/indy/🌐/0📁/^/about/
/💻/asus/y concept 🧊/♖/indy/0/indy.0.html
Pubically shared top slice summary version
There is a private non web accessible matching folder tree under the given Peergos network participant's root folder
There is an origo folder in the root folder of a Peergos name
In fact every folder coud have top level folders name digits from 0 - 9
It depends on the intended role of th enclosing folder what these numbers mean
0 zero is good for Origo folder start here for every such folder
there is a maching Origo Folder under the web hosted folder for the named Peergos user
This allows for public sharing of the top slice information
for every 0 origo folder we can have one called 0📁 which int4ends to capture meta infomration for the Origo folder itself
It is important that that meta-reflectinve information is not part of the folder that the meta folder reflects upon
This is alos a way of associating with any named folder its matching independent adjacent folder that is intended to be reflecting on the entire slient neighbourhood
that links to It a way of talking about slaient trails with the designated end point
to describe an anlaitc account of the synthetic enclosing structures
This is all very hazy but is important
Since I am already committed to sharing everything on line
and annotating and working in the open
The main benefit of this is that searching annotations can help me to find relevant information in my own curated space indranet workspace
and ready to comment annotate and provide entry points to associated conversation
2026-04-16
thinking about a folder structure for autonomous network participants, that are
In this case consider a
Use this origo folder as a space for
The occasion is to explore the possibility of using peergos shared foders matching persona's
I should have done this from the outset?
Try to articulate and formulate what needs to be envisioned/imagined first
in that spirit consider this structure
2026-04-03
.doHow - use TOASTUI Image editor to rotate image
and save it to Peergos, then drag and drop it to document being edited
After years of experimentation with promising info-storage infrastrutures like
As the vision the practice gets evolving
2026.03.25 Wed
The very cconcept or orrigo folder needs to be revised
2026-03-08 Sun
2026-02-19 Thu
This is part of the process of
This is aimed at a next level re-constitution
a fresh
indy/0 is the origo folder for the
That was the one that focused on a vertical slice, the ability to weave autonomous interest based social networks of individuals and communities where they can Share Post
While this objective remains central, just getting the supportive infrastructureal constellations working as seed for the Indy Everything, recent work focused on the seed technology
(NB bot Kernel) but a living system capable of autopoietic autononos growth
@props:
the goal here is to develop and instan(t|ce) first exemplar of the interplayeability of MindPlexes and
Deeply intertwingled Structured HyperDocuments where the foler file structure can reflect the compsitional intentional structure of a focal attention
Start with everything related to a focal attentinon and intent to be captured as mutliple complex structured paes in a sinle page
and as they eveolve enable working on the focal content in way that allows one to switch focus seamlessly
realizing the WikiNizer vision
earlier experiments demonstrated the ability to save structured document
having done so many epxirments
leveraging the complementar nature of IPFS and Peergos
where IPFS can be used to hide synthetic enclosing sturctures
where Peergos gives permanent verifyable full synthetic paths rooted in the name of the actor responsible to creating them
Peergos can provide the same hiding of eyntheitic/enclosing context relying on secrekt links
and even make them writable with full control
Ditto with IPNS
One missing storage capability is needed the ability to save HTML info structures on IPFS automatically
for this will use Helia and add it to the existing IPFS hosted Indy0Pad
2026-01-19
Today is the first working day of the new year. Time for a new high level, generative commons based peer produced synthesys of past learnings and current envisioning of the IndyWeb
A new attempt at getting the articulation of the IT right, the
Been engaged of this kind explorimental ways of creating such synthesis over the past four years
relying on working prototypes and norphic affordances that embodied many of the salient, defining characteristics in a working system of the
co-evolving emergent vision for the past 4 years, explicitly focused on IPFS file system managmanet
drive IPFS Drive capabiities, once it became clear that OrbitDB (the previous focus of efforts) proved to be not sufficient,
In fact I've seen the potential for combining/extending OrbitDb based MindPlexes (nee MindGrphs) with IPFS bsaed MindDrive (first used Fission, then IPFS Desktop but none of them work sufficiently. It all required the use fo IPFS Gateway services. This in itself may not have been the problem, but what we really need is to get at least a minimal viable constellations working without
ever needing to sin up or sing in with any one service
This is critical for the network to groew, and be spreading in a way that is unstopable, enunclosable by deisgn
In tis context the original promis of IPFS is crucial. is to have information and info-morphic permanent storage and communication infrastructures emerging that are auto-poietic, unstopable, permanent, evergreen coevoutionary with verifyable provenance with the abiity to be act in the open commons based peer produced trust network without exposing the real identity of the participnts
before the holiday break.
I was very close to closure. Working towards a new salient generative synthesis under the IndyLab Name indy which was intended to be the one for launch
Over the past 4 years I created half a dozen of paid Peergos accounts to do experiments in creating the open commons based peer producible constellations for the indyweb.
Envisioned originally to be built on top of of IPFS.
Explored using OrbitDb, Fission, Both of them lost out as IPFS was not really up to the task on delivering on its original promise.
I've been searching for technologies that would allow a full constellation of the vision,.
One that would complete IPFS.
I found Peergos, which itslef is leveraging the magic of IPFS but is built around a nemd network of Human Actors (people with a Peergos account or self-hosting Peergos on their own devices.