/hyperpost/π/π§/
@to
@props
π° IPFS based IndyWeb constellations
completing Peergos & Opidox
converging, confluencing towards closure
Β© gyuri@hyperpost
// 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!
- I am still using the
- vertical tabs
- splitview of the Brave Browser
- that I developed to mitigate that problem.
- 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
- βοΈ needs to be added to CK Editor itself
about
- 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
- 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
- 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
- e them
- mutual learning
- synthesis
- salience
- and significance
- 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
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
- ~~~ 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
- 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
- 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
- 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
- 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
- of named Dots
- and ensuring bidirectional eranent linking between Dot Pages
- It allows dragging and dropping urls onto a page which in turn are turned into
- 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
-
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
- 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
- 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
- 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/