/indy/0/💬/
indy.0.💬.html
@created: 2026.03.31
1
create this page as an entry point to formulating the intent in terms that documents the thinking and imaginings in a way that it becomes the very software that embodies the affordance iMagined intended to be created
Intentional InterPersonal Permanent Evergreen Software As A conversation
as a intentionally transparent named networks of
- InterPlanetary
- InterPersonal
- Holonic
- Intentional
- Browser native
- all you need is a browser and
- IPFS Desktop installed on your Laptop and a
- Hypothesis Account
- to join the conversation as a First Class Netizen Human Actor
- Software as a Co-evolutionary Autopoietic Symmathetic Conversation
- Weaving the Open Learning Commons
- via the Indy Learning Commons
All starting with this link just formulated
join this 💬conversation
A critical goal is when on clicks on a page (or on the margins) a link like above a link back to the originating context must be provided prominently at the top of the spawned conversation
Most importantly any one following such links should become automagically a participant in the indyweb and as long as they have account within the enclosing service they should be given a linked IndyWeb identity
and become first class actors in the network
If they install any one of the seed infrastructures
like install IPFS Desktop on at least one of their laptops they could also be able to ceate join this conversations anywhere they choose!
URLs can be used to name dynamic content and morphic processes
server_path designates the (inter)action
search parameters marked with ? can be usd to provide parameters
On the IndyWeb there is a single sever running on each participant's machine
This is equivalent to function calls
What matter is the flow of control and work flow
All this can be described in structured interlinked documents
So it is reasonable to use WYSWYG editor as key tools
Later on introduce WYSIWYN editor where
the conversations about intent can radully refined reformulated in terms that realizes the desired interaction work/info/communication flow
Having the browser as the platform
and provide infrastructure that can deliver both the software and the information data that it works with over IPFS makes it possible to create Browser Native Infrastructures that transcend the centralized web both conceptually and technically
Better still, since the Browser had recently developed into a Structured Interaction Shell,
The kind of things that were popular 30 years ago
Structured Editor as Shells
as the browser now provides three key capabilities
Obviously structued editing and in fact any page based interaction
split =view for Pages so that one can see and interact with two screens paralles
while each view can be navigate with back and for
Combine that with vertical Tabs
and the ability to search for opened tabs across all opened browser windows
Plus
Even when the all open browser crashes
on attempting to open a browser would allow restoring alll the windows that there before
Working on realizing this one affordance
the ability to add a link anywhere that can be used to
engage in conversations linked ot the context whre the link appears
is the fundamental end to end seed slice that is needd
to get the process of weaving the autopoietic indyweb itself!
from manual steps to services
This is the generative idea behind this approach.
The methidology of using existing browser based capabilities to accomplish tasks and workflows manually they way I've been workig for years allos me not only to document
documenting what I do but the processes themselves that I work through manually combining existing capabilities and developing critical new ones on demand
and incrementally automate workflow steps while working on capabiities as needed
has reached a level of real flow, that is about 80% workable, and have a number of seed capabilities that work on their own and much of the rmainning task is
combining them in the large
This harks back to the long fogotten totally abandoned idea of programming in the large
at total oxumorong
in te 80s 8
90s Interactive User interface based structures shel environments were built with the goal of seamless extensible integration but they kind of fallen by the way side
Eventually we got this onster of a monolith the browser, that eventually encompassed many core capabilities, but by architecture they wer alll isoaated
interoperability interplayability was hard and discouraged by the ethos
Now we are at a point whre this fat kernel can be used to
create commons based per produced infrastructure constellation that over come all these limitations
instead of platforms use protocols and build a new autopoietic world where user are at the center of their own world and work connect with each other directly etc
This goes behond Exit to comunity of Holon
which was a laudable approach
bt Enter existing communities and provide them with the means to engage in inter personal intercommunity conversations on their own term from within their owned spaces
work through instance first exemplars
start-exemplar
.doHow
- note that required documentation workflow is working niceli
- I can use Awesome Screenshot to document the process with screenshots and descriptions of what's going on
- Peergos rich Text Editor is working much more reliably than for years before
https://hypothes.is/a/nMXIlizTEfGHRcdG-56CDQ
use-hypothesis.search-to.find.exemplars
https://hypothes.is/users/indyweb
like
exemplar-brave.search-software is a conversation
brave-search-"software is a conversation"
💻/thinkpad/🧊/♖/hyperpost/1/I/📓/2026/03/31/
filename=＂software%20is%20a%20conversation＂%20-%20Brave%20Search%20(3_31_2026%2010：01：42%20AM).html
exemplar
toDo