♖ Peergos
ipns
- dweb.link.2.doc: 🧊.♖.indy.html
- key
- name: 💻/asus/ 🧊/♖/indy
- value: k51qzi5uqu5dm9g6q2l275rmato8ce47dz8cn4di3nglvgpjqd93p2rubxv5t3
- shared.parent.folder
issue-index.html in ipns links
if we have index.html in a folder than in the IPFS Desktop will not list the files in that folder
That means we need ot use index.htm instead
TODO - modify editor to work with HTM files too
🏁 start - ∀-♟️🤝.➿📰Indy.Web
Open Sauce, Commons based, peer produced constellations for
webnative, permanent, evergreen, morphic, multi-player, omni-scale info-communication infra structures for scaling reach, salience externalizing augmented human interpersonal inter intellect
powered by Peergos ♖, IPFS 🧊 and Trystero 🤝
active.docs
- /indy/index.html
- /indy/:/do/dev/~/indy/0/peersuite/
- indy/:/do/dev/~/indy/0/wiki/Pad/
- /indy/📓/2026/01/27/scratch.pad/
dweb.links
folder.trees - private view links
- indy
- :
- do
- onboard
- friends
- dev
- onboard
- do
- :
folder.trees - IPF/NS links
create these links by
- uploading Documents to local IPFS Desktop
- create local IPNS keys
- and Indy Resource Names as links to the actual IPFS resources
- These will be replaced in the future by mechanisms
- that powered interpersonal sharing with full mutual provenance
- as worked on in /indy/:/do/onboard/friends/~/Parmjit/
- # how.did.I.get.here
2026-01-22 14:30
Took the plunge.
Started the process of constructive practical synthesis
realize the dream in code
started to create
- the integral
- forward-compatible
- mutual adjustments to existing expolirmental infrasturctures
- as the pathway for developing
- seamless generative learning/woking/autoipoietic flows,
- frictionless, zero config, auto install, mivmicro
- virtual holonic,born multiplayer and future compaibly interplayable
- universal micro saas
- (software as a services( that are themselves
- bave.search?micro+saas
- "Building Your First Micro SaaS
- creating high value niches that are born inteplayeable interworkflowable
- evergreen
- autonomous
- people centered
- verifiably attributed to the creator
- open interplayeable integrateable inot individuals owned workflows
- turning the Curse of Lisp
- into a blessing
- have the power of LISP
- without the
- Lots Irritating Single Parentheses
- If you can describe what you want to do
- provide fully working instnace first exenmplars
- there will be a way to REALise it in running holonic apps
- arise through interplay between such services
- that help people to capture all informatin they care about
- as universal hyper plexed HyperDocuments using HTML as a lively active information exchange format
- that are shared along with the very means of inteacting
- and creating them in a global named network of
- autononous human participants
- for their own benefit
- (software as a services( that are themselves
- interplay across key application domains
- supported by
- commons based,
- open constructs
- but are created as open constructs
- not just the source but the way they are created, the secrets that make them work, the souce itself is open
- facilitaing omni-optional organic scaling
- autonomous people-centered info-morphic-
- communication infrastructure constellations
- that can provide an alternative, a polar opposite of the prevailing paradigm
- that actually plays nicely with them for mutual benefit
Levarage the ability to work on two laptop simultaneousl
Setup on thinkPad for documenting the process
on Asus do actual development
leveraging/instrumenting my ability to engage with all personal work simultanously on any of my devices while ensuring automatic synchronization
This synchrnization works seamlessly and completely when working with Peergos.
This is because Peergos is real cloud app
whereas all the others I am developing are available via IPNS
both the apps and the documents that I am working on
main tasks
- CKEditor based Wysywig HyperDocument Editor based on CKEddoitor whic in turn is based on editor.js are working both under Peergos and IPFS
- Te peergos version is able to reflect Indy 0WikiPlex Pages is apporiate folder structures in the Apps Data folder
- On the IPFS side we do have a variant of the Indy 0Pad editor which saves the documents in localStorage
- ready to be incorporated in corresponding 0Wiki Plex Pages
learned.about=Google.Chat insert emoji
🐒
let's see ⏮️⏭️type a : to trigger popup choices not just emojis but any action
🎬 clapper use that for do
also avoid using emojis in folder names
work around to make inbrowser.link paths work
instead add the icon as part of a file
so in this case add a folder do for experimental activitites like
- // new folder layout
- using special characters
- :/do/about/🎬.html
- onboard/~/parmjit
- // exploriment onboarding personal contacts
- onboard/~/parmjit
2026-01-22
.about = Indy Web
IndyWeb delivers on the aspirations of the IdieWeb community
dedicate to providing a people-focused alternative to the “corporate web”
- owning your content.
- without being tied to any domain
- you can establish Personal Presence on the web and share and collaborate in your owned circle of People
- share you content in a way that gives view full control over it through time
- with permanence, evergreen future profo availablility with full historical verifiable provenance and autorship and recapitulable history of all interactions
- who read/acessed your stuff
- and all your collaborations contributions
- .
.snarf-from-Telegram
Gyuri Lajos, [21/01/2026 10:36]
climbing the mountain
- Rely on inbrowser.link, IPNS for the app Indy 0Pad and
- IPFS for the CID of the hyper document to be shared
- trying this to share a document using its
- content identifier CID and inbrowser.link that is
- able to retrieve the document from IPFS for editing with Indy 0Pad.
- One can make changes and eventually share back the modified document
- via persuite.space or saving it to IPFS and create link with that new CID
- linked to the user's trully self-created, self-sovereign Indy ID
Gyuri Lajos, [21/01/2026 10:58]
https://k51qzi5uqu5dihxsxkei250vtafny61hql20k52q6541viq5da5vl3wfazx7i7.ipns.inbrowser.link/🧊/♖/indy/0/Pad/📝/?title=🏁start-∀~♟🤝➿📰Indy.Web&path=https://inbrowser.link/ipfs/QmZWiisy1De5uVUd7AtiPfTL1SYrmKK1VnYcVi43V1q5FR&isPathWritable=true
z
Gyuri Lajos, [21/01/2026 11:00]
When 1 saves the changes to the document a popup wold inform 1 about the size of the document saved
Gyuri Lajos, [21/01/2026 11:00]
reload the browser page to see tha inded the changes you made had been saved indeed
Gyuri Lajos, [21/01/2026 11:16]
🧊/♖/indy/0/Pad/📝/?🏁start-∀~♟🤝➿📰 ()
.testing
z
edited
.props
- @created: 2026-1-7
- canonical 🧊/♖/indy/♖-indy.html
- an0tated: 🧊/♖/indy/♖-indy.html
- ipfs: 💻/asus/ 🧊/♖/
- ipns:
- local.ipns:💻/asus/ 🧊/♖/l
- 💻/asus/ 🧊/♖/
- 💻/asus/ 🧊/♖/indy
- k51qzi5uqu5dm9g6q2l275rmato8ce47dz8cn4di3nglvgpjqd93p2rubxv5t3
- Copy the link below and share it with others. The IPNS address will resolve as long as your node remains available on the network once a day to refresh the IPNS record.
2026-01-18
development
setting title by hand
function setTitle(s) {
document.
getElementsByTagName('title')[0].textContent=s;
}
setTitle('♖/indy/index.html')
indyweb
(edited 38 mins ago) Jan 7
on "/indy/index.html"
(bafybeig3hpaa7l7clax4rau3temikwbzixvnx4qkqjspsgszfxnmhcr3jm.ipfs.dweb.link)
Note this page is now ships with hypothes.is embedded
so no longer relies on via hypothes.is
background
$
- I spent most of 2025 with explorimentcing 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
- universal open hyperdodcument system
- 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
- auto-
$
- 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
- that is to say these identifiers can provide names that are
- 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
- possibly open
- A peergos pathname can be associated with a secret share link
- 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