/indy/about/index.html

?whyHere

Ever since late November 2025

when IPFS dweb.link started to work much more reliably
- and inbrowser.link also had much improved

The way opened to go local-first and keep much of personal information loclly across devices by using IPFS Desktop and its webui

This opened up the pathway to realize

the vision for Universal Resource Identifier
naming scheme amenable to the PUN to be interpreted as a way to retrieve information, even when it is local first

The key to that was

coming up with names that start with naming the machine where 1 works with its nickname
and ensure that all files created in a day are accessible in a chronolarchic folder tree with paths like
- /💻/asus/🧊/me/📓/2026/04/10
this approach allows for implicate versionning mechanism and practice
when combined iwth rules for sharing an publishing
In line with the overarching design and development methodology
that is integral, omni optional,
recorded working
all work is carried out in a meaningful clonoarchic structure
leveraging the power if IPFS that allows the same resources to appear iunder any number of alternative paths

While still using Peergos and even doing the editing there

publishing takes the form of uplading the documents to
matching folder in IPFS

old version moved from root folder into an about folder as index.html

♖ /indy/

🏁 start - ∀ ♖ Peergos Indy Constellation

@created: 2026-1-7

background

I spent most of 2025 with explorimenting with seeding constellations required for the eventual development of
- integral,
- omni-optional
- permanent
- evergreen
  - future compatible
- autonomous
- co-evolutionary
- generative
  - commons-based
  - peer produced
  - open
    - source
    - sauce
  - end-user extensible
  - meta-designable
    - ifrastructures and meta-morphic-capabilities and affordances and constellations for
mutual-arising webnative
- universal open hyperdodcument system
  - where everything is constited as a named networks of digital resources
  - characterized by all having Universal Resource Identifier
    - that are amenable to be retrieved
    - securely
    - privately
    - with verifyable integrity
    - and full historical audit/version trails and
    - attribution
    - forming named networks of
      - autonomous social netwroks of people
      - information
      - communication/exchange
      - discoverability
      - where individual work to externalized once coevolving intellect
      - merges seamlessly with emergent human interintellect
    - where trailbazing mutual learning and friction-less
    - peer to peer individual conversations can happend
    - that are continuous without needding to be synchronous
    - yet remain contiguous with the participants entire contribtions
    - symultneously scaling sailence, synthesys and reach
    - and communities can find eac other and connect and co-laborate
    - between people becomes
  - the historical information flows that are amenable to be recapitulated,
  - and shared as threads in a virtual diital pensieve
  - leave in their wake verifiably integrous trails that are able to reflect the emergent value of these interactions
info
- structures
- storage
- communication
- co-laboration
constellations
needed
to get just above the threshold that was required to envision and develop the seed for the sweet spot
to get the Indy-Web/Verse off the ground and into the its own
- auto-
  - nomous
  - poietic
- local
- offline
- personal
  - -first
- inter
  - planetary
  - personal
- meta-morphic

Both Peergos and IPFS technologies that are constitutive to the very possibility of envisioning and eventual realizing this emergent vision had improved to the point so that it is now possible to attempt an end ti end first generative spiral cycle that can complete sweet spot dreamed about for nearly a decade
Peergos CK Editor is now much more stable
- this is due to the fact of the eventual replacement of of bit??? with wbesocket communication
IPFS Desktop with the latest version v 047 is now able to share rsources reliably
- and it it also possible to elliminate the need to rely on gateways either paied of publically maintaind ipfs.ip and dweb
- and instead rely on a service worker powered PWA called inbrowser.link
- that runs an IPFS node in the browser
- and the mechanism for DHT management is now working reliably

the most important conceptual advance over the past year was the systematic exploration of the possibility of devising constellations that would combine capabilities of Peergos and IPFS
so that Universal Resource Identifiers become possible
- that is to say these identifiers can provide names that are
  - human Meaningful/readable/writiable
  - yet permanent and verifiable
  - that can be used to actually retrieve the named resource
- All this will happen at the edges
all this is possible because the name of resources include the names of the individual
or community that created the resource
These names can themselves be pseudonames or nicknames, the true identities of the can also b shared within an emergent autonomos soicial network

the envisiaged/explorimented infrasturctural support emerging from the judicious combination of Peergos and IPFS also provides a way of delivering on the original 4 years old ambition of
- zero friction
- cascading organic growth of the Named People/Community networks
Seeding the network does require just one account/identity to be created using Peergos
Peergos can be self hosted so it is also possible not even to require a Peergos account although it is adviable
These networks can be created even without relying on the Domain Name System
- while they can be used to work in combination with domain names
- either via IPNS DNSLinks
- running your own Peergos.net linked to owned domain names
- or imply by signing up with Peergos
- in which case the name you wish to have needs to be created as a Peergos user name
- that has to be globally unique (Per Peergos Service Provider)
  - of the form like <Peergos User Name>.peergos.me
  - as in here indy.peergos.me

$ There are many things that need to be integrated for all this to work

most importantly using IPNS and IPFS names in combination with Peergos resource names
Start with Peergos names and Peergos webhosting capabilities
So we need to configure constellations mapping from
♖Peergos
♖
♖🌐 Peergos Web Hosting
🧊 IPF/NS
🌐 Web

$ sketch the explorimental design

♖📁 Peergos shared folder link
- A peergos pathname can be associated with a secret share link
  - the beauty of this that the link can be created to expire by a given day
  - require passowrd
- when 1 shares an IPFS folder it can contain a document that provides a
  - possibly open
    - secret link, such that when clicked the the named folder would be open in Peergos even if the 1 accessing the folder does not have a Peergos account
    - better still, the secret folder could be designated to be writable
    - best to require a password two and with a time limit to its availability
  - Since it is also the case that all this machinery can be combined with Peert to Peer secure, encrypted communication channetls powered by peersute.space
  - which it self is an Opne Construct, that is to say it is not only Open Source
  - but Open Sauce, and is created as a vanilla PWA App so that it can reqdily be extended and integrated into indy web infrastuctures
start with ♖🌐 Peergos Web Hosting
- Use this to make Peergos Custom Apps to be shared with people without a Peergos Account
- Obviously People who do have a Peergos accounts, people who are thus able to Weave their own Networks of collaboratiors and autonomous owned social networks
- may even support their immediate friends network to collaborate with them
- hence awareness of the implied autonomous social network would expand
- and alll they need to do to be able to weave their own cascading social networks would be to have their own named Peergos Account and run their own IPFS Desktop
- so that they can share and work indeendently of the 1 who invited them to the indyweb in the first place.
- This later