📰 IPFS based IndyWeb constellations
completing Peergos & Opidox
converging, confluencing towards transitive generative closure
© gyuri@hyperpost
@card
- 📰 IPFS based IndyWeb constellations
- completing Peergos & Opidox
from - ipfs
@to
@props
- view: /hyperpost/🌐/🧊/
- annotate: https://hyperpost.peergos.me/🧊/
@to
@props
- view: /hyperpost/🌐/🧊/
- sandbox: indy0pad
- annotate: https://hyperpost.peergos.me/🧊/
- ipns: Indy0Pad@IPNS
- file: hyperpost-🌐-🧊
- ipns.dweb.link:
- secret:
achievements
@created: 2025-12-09
about
- // continue with the practice of writing
- contextually named
- = contextual naming
- the path leading to the document encodes
- intent
- purpose
- aspect
- qualia
- provides a situated name for the focal context/plex of attention
- the path leading to the document encodes
- = contextual naming
- single page,
- page-in-a-page
- multi-page-
- universal open hyper-document system (U OHS)
- inspired by
- = OHS
- inspired by
- providing a
- baseline |
- elaborative
- formulative
- clueful
- structuring
- baseline |
- using three levels of headings and outlines as a basis
- in anticipation of turning named elements progressively into Dots
- so that high-resolution, bidirectional links
- can be added later
- as a way of capturing
- not only of the intertiwngularity of ideas
- but indicating inter dependency structures
- so that as attention is shifted
- and wordcloudoutlines are formed
- we can end up with
- HyperMaps that can dynamically
- help us to see salience structures
- as EnScapes for ideas
- this top level major section ind a multi-page document like this is intended
- to provide a named space for jighlighting achievements for ongoing work
- contextually named
- // NB
- everything here assumes that this rich/cluefull intentionally structured multi page document will be amenable to be processed to provide alternative organisational structures with their own specific intentional view
- All that is rendered possible by naming and in/trans/en-clusion mechanisms
update - 2025-12-10 We
goals
- enhance
- continuity of flow
- ensure resume-ability of focus
- track through connections
- envision start to complete first cycle
- leveraging
- IP(F|N)S via Agregore and IPFS Desktop
- leveraging
- >>> // in.notation - conjunctive, discjunctive enumeration
- character sequences like
- ‘| ’ and ‘& ’ at the beginning of
- a nested list of items
- followed by a nested list is introduced as
- an in-line-notation is used to indicate
- that the enumeration in a nested list below it
- is intended to be interpreted as a list of
- conjunctive or
- disjunctive
- list of elements
- an in-line-notation is used to indicate
- ‘| ’ and ‘& ’ at the beginning of
- character sequences like
- <<<
enhance - continuity.of.flow
- initiate a new constellation
- refactor, reimagine, reconstitute layout of
- personal info-morphic-con(s)-plex-structures
- rooted in named Actors as in
- /hyperpost/~/me
- designating the owner of the
- Peergos account or
- the logged in user of the laptop where
- 1 is running the IPFS Desktop
- as I write this this resolves to
- designating the owner of the
- use
- personal pronouns
- object pronouns
- object pronouns
- do.search
- /💻/asus/🧊/♖/hyperpost/~/gyuri/🏛️/2025/12/search/personal.pronoun
- ipfs
- hypothesis-pronoun
- personal pronouns
- refactor, reimagine, reconstitute layout of
personal.pronoun
- as universal pseudonyms like
- me
- us
- we
- they them
- yall
do-setup - Files /💻/asus/🧊/me
- so that the InterPlanetary Personal folder ipns address is created
- as a named IPFS Store for my work on my asus laptop
- in my own IPFS Desktop running there
- done so far
update - 2025-12-09 Tue
resume work
- add achievement section
- next-task - provide IPFS equivalent for this IPNS morphic object
update - 2025-12-07 Sat
continue-experiment - transitioning to Agregore
gotcha - Agregore does not do spell checking
- that's a bit more than a bummer, it is a showstopper, not the way to work
- reverting back to using Brave browser
- After all Brave with its vertical tabs is a great environment
- Indy0Pad@IPNS in Brave provides a more stable environment for working
| action | Indy0Pad@IPNS | Indy0Pad@IPNS | Indy0Pad@Peergos |
|---|---|---|---|
| agregore | brave ipns | sandbox | |
| on save | cursor is lost, need reload | works fine, no error behind the scene | only works if the corresponding Peergos file is open for editing |
| copy paste transfer | need to find other Agregore window | split view works open the file in Peergos window can be closed Even if one fails to do the save to Peergos | if 1 saves while the parent Indy0Pad page is not opened leads to freeze that was a bummer |
improve-ergonomics of write flow
next-task - provide IPFS equivalent for this IPNS morphic object
- @created - 2025-12-09 Tue
- background
- the current setup allows 1 to bring together into a permanent mutable morphc object
- information created using a Rich HTML Editor and a whole tree of related documents
- which themselves are contextually named by the folder structure they enclose
- The info structures so created are mirrored in corresponding Peergos Folders
- This mirroring is currently ensured by a disciplined manual process
- that is used to explore experiment on an exemplar the affordances that needs to be developed
- currently changes to the document being edited is saved in local storage
- so it is bound to the particular machine and a particular Browser Profile
- the next level goal is to save the documents worked on on IPFS
- try to use Agregore Browser
- and instead of working with the ipns
- work with the corresponding ipfs named folder
- try to use Agregore Browser
- proposed approach
achieveBement
- provide a way of creating morphic units of informational units
- that derie huan readable names both for the
- morphic capability
- in this case the indy0Pad Editor named 📝
- and Rich HTML documents in an adjacent folder structure
- as in the name of the path to the document
- path=../♖/hyperpost/🌐/🧊/index.html
- both enclosed in a named folder with its own ipns permanent name
- morphic capability
- that derie huan readable names both for the
- individual documents can then be mirrored and saved within Peergos
- providing immutable human meaningful names for named context and documents
- like in this case
- // practical examplar of how Autopoiesis can be laid out
- Indy0Pad@IPNS gives a good editing experience
- with strong guarantees for always save works always
- todo - make save automatic as in Emacs (whatever worked there was good)
- number of characters typed?
- todo - make save automatic as in Emacs (whatever worked there was good)
- with strong guarantees for always save works always
- It still not what we need eventually but is stable, without the potential snag with sandboxed versions
- better still no need to fiddle with creating the sandbox link
- we can defined a bijection beetween editing urls across infrastructure constellations
- Once the content transferred from the Indy0Pad@IPNS to Indy0Pad@Peergos and saved
- the saved file can be downloaded and added to IPFS
update - 2025-12-06 Sat
experiment - transitioning to Agregore
how.did.I.get here
- uninstalled old Agregore and installed latest Agregore cleanly on ThinkPad
- took a while
- had to turn of Real-time threat protections
- so that anti-malware thread protection does not have to chew through ¼ Gb of code
- good job I an documenting this and can now turn it on
- now it's on
- Used
- view: /hyperpost/🌐/🧊/ from @props to open the document
- in Peergos
- copied stuff from Peergos into this IPNS document
- and started using it and document what I am doing
- the expectation is that I can keep editing here
- and when I want to switch task I just get
- to the corresponding Peergos folder
- open the document and copy paste from Agregore
- there to “commit it” if you like
- to the corresponding Peergos folder
experiments
telegram - comments
Jerry's amazing inro to Open Global Mind
gyuri
(edited) 1 hr ago
on "Introducing Open Global Mind"
(www.youtube.com)
we can't remember what we know and we can't share it with one another very effectively that makes it really hard to cooperate
can't remember (recall) what we know what we know it would be important
Matt's Dream Space taking shape
- At long last I am changing the default font in the indy)Pad editor ro roboto which is aar more readable even withsmaller font sizes
- Share documents in a way that people Can use In-line-trailmarked responses and futher elaborations that would be clearly markd with TrailNMarks in-notation, conversation thread, work on, own their own contributions and can share back
- The Read Write Web is born
- So this is an example of being able to incorpora**te snippets from telegram
- have another great workflow/affordance ready made by the developer of editor.js (I know hi well from the days when I was still active on twitter 6 years ago
- I always knew this will come out in the wash in the long run. I just could not imagine it would 5 years
update - 2025-11-25
change - body font
- body {font-family: Roboto, sans-serif}
auto.inject - hypothes.is embed.js script
<script src="https://hypothes.is/embed.js" async></script>
<style>
body {font-family: Roboto, sans-serif}
☑️ add formatting changes to ck editor presets
do that first on the Peergos side
update - 2025-11-25
accomplished on the IPFS side
- put the editor code at the root of the current IPFS constellation
- have some pending changes from the Peergos side that would add a favicon
- and clearly diverging from the Peergos custom app format
- CK Editor and anything derived from that would not work very satisfactorily
- It is better to make the IPFS setup the master
- and use Peergos as a secure encrypted backup and distribution
- and a source of human readable names
- ant trails
- enjoy the fact that save would not fail on this side
- a good discipline is to open the same page on the Peergos side
- before sqitching context
- like now
- Use the Universal HyperText transfer affor💃dance cross Apps
- Copy Paste x apps
☑ save pages in file system by chronolarchic structures
=============
https://www.compart.com/en/unicode/U+1F483💃
// big.shift-towards - naming focal attention using Trails
how.did.I.get - here
- Yesterday I've noticed a marked improvement in the performance of Peergos
- Later, today, I even managed to confirm, that the frequently occurring
- dreaded failed to save document status message
- in the CK Editor based indy0pad.next
- cease to occur
- With that Peergos became really usable!
- dreaded failed to save document status message
- I am still using the
- vertical tabs
- and the
- splitview of the Brave Browser
- that I developed to mitigate that problem.
- vertical tabs
- It is still worth using, even though the Editor is no stable
- simply because it provides a
- meaningful name for the tab
- that comprised of the last three elements of the path to the document
- that is something that
- simply because it provides a
- ☑️ needs to be added to CK Editor itself
about
- @card
- autopoiesis of the IndyWeb
- Creating a new
- companion constellation of
- open sauce
- autonomous
- infrastructure
- Peerg🔒s
- OpiDox
- based infrastructures
- level synthesis seeding
- minimal workable constellations of infrastructures for the IndyVers/Web/Net
- that is capable of scaling
- reach
- discoverability at global scales
- reach
- flows
- information exchanged as self-value
- along with the morphic means needed to
- create/curate engage and experience them
- autonomy of the participants
- own your data
- own your destiny
- evergreen future compatibility
- Flipping existing characteristics
- own your data
- based infrastructures
- This is the start page of a major new development phase in the autopoiesis of the IndyWeb
- Creating a new
- companion constellation of
- open sauce
- autonomous
- infrastructure
- that plays nicely with the existing open, commons based per produced infrastructures like
- Peerg🔒s
- OpiDox
- based infrastructures
- This one is based on IPFS
- taking the work of Mauve with Agregore as an inspiration
- which is not just a Browser but a Weaver of autonomous networks in its own right
- to this network Indyweb adds a People Cantered Constellation
- weaving an InterPersonal InterPlanetary Network of
- local-cosmo indranet of autonomous work spaces
- and is creating a higher level synthesis that leads to the seeding of the
- minimal workable constellations of infrastructures for the IndyVers/Web/Net
- that is capable of scaling
- reach
- network effect benefitting the participants
- connectivity
- conversations that can be continuus without being synchronous
- instead of feeds maintining self-organizing streams
- with ful provenance and recaptiulable history
- maintinaed for and by the participants for their benefit
- while guaranteeing
- discoverability at global scales
- interactions at omni present evergreen local scales
- flows
- information exchanged as self-value
- along with the morphic means needed to
- create/curate engage and experience them
- experience the web
- not just as an extension of your mind
- but as the medium of structured
- born multiplayer, co-laborative
- info-morphic-capabiity/work-flows
- as self-created value flows
- autonomy of the participants
- own your data
- own your destiny
- with permanence and
- evergreen future compatibility
- the very means 1 uses to create/curate everything on the Web
- privacy
- security
- un-enclosable
- unstoppable
-
- in a word
- Flipping existing characteristics
- of Cloud Services to their dual opposites of what characterizes them, viz flip
- Provider Centric to People Centred
- the value created through ensuing network effects is no longer captured/realized by the providers of the services
- but by the participants
- who themselves are the providers
- but
- Provider Centric to People Centred
- e them
- enclusing
- of Cloud Services to their dual opposites of what characterizes them, viz flip
- Flipping existing characteristics
- in a word
- own your data
- mutual learning
- synthesis
- salience
- and significance
- reach
- in a way that results in intelligence augmenation
- improving the intellectuall capacity not only of individual human beings whio make use of it
- but entire networks of co-laborators forming
- interest based autbonomos social networks of their own
- that leads to the emergence of
- autnonomous
- self-hosting
- autopoietic
- coevolution of
- Virtual Cloud Info-morphic Universal Hyperdocument system
- taking the work of Mauve with Agregore as an inspiration
practical.steps - indy0pad & indy0wiki.pad interplay
- setup.using-brave browser profile: ♖indyweb@tp
// experiment - indy0pad & indy0wiki.pad interplay
- ?.why.here
- Now that both indy0pad and indy0wiki.pad are setup on IPFS
- ready to use indy0wiki.pad to start creating
- explicitly intentionally named/qualified,
- bi-directionally linked
- in/out-transclue-ded associative complexes
- gloss - in-transCLUE-ded
- is a proposed neologism
- it is a reimagining of Ted Nelson Idea of transclusion
- but instead of including content from a source
- so that the transcluded content remains in sync with a designated source
- pages are composed of inline Clues
- and the Clues themselves
- are composed of outlines of clues
- and every clue has its independent existence
- and while it may have been created in the context of a page
- it is automatically created as a clue
- and in the pages flow these clues are out-transCLUE-ded
- that is to say there is a link out to that clue from the page
- and that clue is shows as a page in 1's indy0.wiki in context
- and can be edited in there
- on save a message is sent to open editors
- to effect an update to the page
- to refresh the content of the
- out-CLUE-ded segment
- This opens up the way to collaborative editing
- TODO
- and in the pages flow these clues are out-transCLUE-ded
- ~~~ where one click's into the text of a clue appearing on a page
- and the latest version of the clue is shown via indy0wiki.pad
- and if they are not identical
- the user can merge the changes in the ind0wiki.pad
- and signal the re-inclusion of the changed/merge version of the clue in the original document
- The solution to concurrent editing of clues
- relies on the idea that when one references a Clue
- created by others a local attributed copy of the clue is created
- in 1's own ClueSpace and when any other changes the clue they get notified of the changes and can accept thise changes or create a linked conversation/comment about the changes
- This is possible because asynchronous communication channels
- are always available between collaborators
- to send notification about pending changes
- with proposed deltas
- and can initiate real time merging sessions
- This one is a nice example of integral design and
- integral operations
- That clue will in turn
- will have a backlinks to all the pages that it is included via an out-transCLUE-ded is anmed broken up/mirrored into clues
- it is a reimagining of Ted Nelson Idea of transclusion
- is a proposed neologism
- weaving trans-hyperdocument netowrks
- while indy.0.pad focuses on providing a new writing experience
- that makes use of the rich capabilities of CK Editor
- fluent proper way of handling nested outline structure
- ability to introduce three level heading
- insert page breaks
- that makes use of the rich capabilities of CK Editor
- Now that both indy0pad and indy0wiki.pad are setup on IPFS
- further.background information
- Up until now I had to choose between using CK Editor based Peergos Custom App
- which was for a long time perilous
- always running the danger of data loss with a careless use of saving
- which would fail if any other update happened within the folder tree that it was part of Gotcha
- which is now fixed with the development of the Peergos Custom App
- indy0pad has a viable workaround
- but now usable but totally lacks the necessary connection across documents
- which was for a long time perilous
- indyWiki0pad
- which is not a Page-in-a-Page oriented full featured editor
- but a minimal vanilla HTML Rich Text Editor
- with the ability to introduce Wki like organization nee (WikiNizeR)
- Wiki Like Organizer of yOur Personal Research
- Personal Research Assitant
- https://web.archive.org/web/20151018053101/http://linkedup-project.eu/files/2014/12/WNR-Blog-Picture_2.png
- WikiNize Research 7 years before Roam Research
- a tool for Personal Knowledge Management
- not the best designation for sure
- Person-first Mutual Learning Space
- but without the great name Networked Thinking Tool
- Presented in 2014 in the Linked Up Challenge
- Decided against launching, because it was clear that
- The Semantic Web with its tessalation of the graph
- in terms tripples, Subject Predicate Object
- was woefully inadevate
- and our approach focusing on named associative complexes required a better way of conceptualizing
- what we called MindGraph
- and indeed it did require another 4 years
- to discover the right way forward
- And since 2018 we were developing concepts of an infrastructure
- that would allow MindGraph to become
- an Interplanetary Interpersonal Open Global Mind
- https://hyp.is/j2W0UsFGEfCD8xvZolPHCw/www.youtube.com/watch?v=PbFg0B8uN0A
- Graph
- a tool for Personal Knowledge Management
- of named Dots
- and ensuring bidirectional eranent linking between Dot Pages
- with the ability to introduce Wki like organization nee (WikiNizeR)
- It allows dragging and dropping urls onto a page which in turn are turned into
- propery presented links
- It is this ability and implcit nnterdot linking
- that makes it ideal to capture the intertwingularity of
- multi page in a page documents
- and sections/dots within documents created by indy0pad
- The main benefit of doing so is that it gives the author/creator /curatorof such documents the ability to
- interlink them in a way that can provide a HyperMap of the territory comprising info-morphic hyperdocuments and all other web accessible pages which IS the territory that is created by individuals co-laboratively
- high resolution self-organizing indranet workspaces
- Up until now I had to choose between using CK Editor based Peergos Custom App
IPNS Publishing Keys
much of the work involves extensive use of IPNS Publishing Keys
These are documented here
IPNS provides mapping from human readable names, the names of the keys used
to mutable information resources
🧊ipfs http://k51qzi5uqu5div1auuxm59ygav4p7gdg9z4e9iggtu6m43rmc3xw75mczx2b7x.ipns.localhost:8080/
k51qzi5uqu5div1auuxm59ygav4p7gdg9z4e9iggtu6m43rmc3xw75mczx2b7x
purpose
- provide a Web Hosted entry point to ongoing
- meta-reflective documentation
- of all work related to developing an IPFS based
- inter-Local/Personal/Planetary Virtual Cloud
- infrastructural constellations
- that are
- commons based, peer co-produced/evolving
- self-hosted, browser native
- Open-
- Sauce
- Source
- Constructs
- Open-
- charactised by being
- autonomous
- local-first
- self-hosted
- private
- secure
- unenclosable
- unstopable
- surveilance resistant
- resistant to harvesting by centralized aggregators
- while maintaining full discoverability
- verifiable attribution and full historic provenance
- of all information exchanges and conversation flows
- permanent
- evergreen
- co-evolvable
- born Multiplayer
- Commons based,
- Peer Produced
- local-first
- Self-Hosted
- omni-optional
- integral
- holonic
- co-evolvable
- Infrastrucures
- bootrapping the IndyWeb
- Infrastrucures
- autonomous
- inter-Local/Personal/Planetary Virtual Cloud
- including information about how it interplays with and mutually arising with self-hosted Peergos based such infrastructure
- in fact the IPFS based and the Peergos based infrastructures need to be combined
- into one that is required
- where
- IPFS gives a natural peer-hosted, interplanetary evergreen permanence
- and global reach relying on Content-addressability
- cryptographic names for interconnected context
- Peergos gives human readable naming system anchored in
- globally unique human-meaningful names
- anchored in global names rooted in Peergos account names
- that People are able to create themselves
- either by creating such account with existing services like peergos.net
- or can choose to run Peergos themselves on their owned machines
- while
- IPFS gives a natural peer-hosted, interplanetary evergreen permanence
- in fact the IPFS based and the Peergos based infrastructures need to be combined
- It is possible to create constellations that rely mainly on IPFS
- and uses minimal, though crucial exteent on Peergos
- The idea is that everything will be done on IPFS
- and only the human-meaningful self-hosted autonomous permanent names are provide through the interaction of Peergos and IPFS
- in the limiting case Peergos will be used to provide
- the means of creating secret links to mutable content
- where the meaningful name is provided by an alternative eco system
- and vice versa
> Peergos News Snippets
2025-11-14
/hyperpost/🌐/🧊/snarf-peergos.chat/
https://app.element.io/#/room/#peergos-chat:matrix.org
@saved.in:/hyperpost/🌐/🧊/snarf-peergos.chat/