start.page-IndyWeb
.props
folder: link
web: โ/hyperpost//๐ญ/, edit,"โ/hyperpost/๐/๐ญ", via.hypothes.is,hypothes.is
Two Joined Squares[1] Unicode Character โโงโ (U+29C9) use that for annotations
.retrieve-silver.twine
.extend-the.idea.of-single.page
following the logic of maximizing focus, by writing eerything that coms to mind on a single page leads to considering writing even daily notes into the start page, trusting that soon these will get to be
There's a lot of work need doing.
I suppose I will have to relegage some of that into MindPlex using the existing PlexEditor
>update-2025-10-06
.props
folder: link
web: โ/hyperpost//๐ญ/, edit,"โ/hyperpost/๐/๐ญ", via.hypothes.is,hypothes.is
Two Joined Squares[1] Unicode Character โโงโ (U+29C9) use that for annotations
>restore-Single Source Overview
goal
.transition.to-IPFS powered infrastructure constellation
steps
foci
>update-2025-10-05
Next Level end to end first cycle in a spiral of autopoeisis
Can document work on the annotation margins of documents edited and made available on the web using hyperpost IndyWeb Player hyperpost powered by Peergos
Gyuri Lajos, [05/10/2025 01:17]
revisiting earlier experiments with setting up IndyWeb InfraStructure using IPFS
This constellation ships documents with specific versions of the tools that were used to create them
created: 2025-8-22 09:50:53
.daily.notes-2025=09=21
.// review-2025-09-21
- stub : This is the Origo document for all my Essays wrtiting to try,
Explore Experience and Experiment
$ getting close to complete interplay-ability between MindPlex editor and Peergos CK Editor
this is really needed to demonstrate that multiple implementations can provide
Not fake it as we make it,
but Make it as we write annotate and have symmathetic conversations as symmatheticists in the medium of software
So anything one does need to be done in at least two or better three drastically different scales and ways of operating
self-sufficient, embeddable and interplayable from the start
$ hypothesis as catalist
-background
4~notation=Paragraphs are nameless Dots
โ๏ธdev-revert.to~CK.Post.Editor
- exploring the use of Peergos as the basis of developing a kernel for the IndyWeb
- As a first step want to take the existing CK-Editor Custom App
- change it so that it would work outside Peergos as most users of Hyperpost will be
4=omnioptionality-tinkerability
flipped.Web specifications as the end product of constructive explorations
The primary value of Web is that its focus is on interoperability and standards
so that many players can provide their own alternative implmentations
flip that. Just as Jason did
Start with constructions that work across multiple platforms and programming languages
Prove the proposed de-facto standard through experiments
One way to give permanence to a capability is to eschew reliance on version numbers
An alternative to that is to build systems that are bootstrapped and autopoietic
with strong guarantees of future compatibility
Another key aspect here is that avoid lock in at every level and single points of failure
the price of ronustness is redundancy
If something is worth doing it is worth doing in all conceivable constellations of infrastructural consideration
As long as there is a single seed from which everything can be grown that should be possible
testing fonts with CK Post Editor
indy.web.link: โ/hyperpost/๐/๐ญ/
// can generate by Peergos Search an overview of folder contents
anything that can be produced via manual interaction is ipso facto amenable to be automated and can be turned into a virtual indy web service call
Sharing links to top level folders enclosing current work focus is a good way to keep track of work
even making sense just to post links like that in dedicated Telegram channels like IndyWiki
โฆฟ current.focus~Indy.Wiki
after a lot of toing and throwing, running up and down on the ambition stack
I concluded to focus on just delivering IndyWiki at long last
envisage it as the simplest possible people-first autonomous autipoietic interpersonal info-communication-collaboration autopoieti morphic intentional infrastructure for software as virtual Cloud Services in the long tail of the (Indy)Web
$ indy.web.link: โ/hyperpost/๐/๐ญ/
$ do.how
My focus is on delivery at last so that people interested have some minimal workable ways of empowering people to form autonomous emergent communities of practice dedicated to share pursuances and interest
small dedicated circles of autonomous sharing and collaboration
a process started by developing a Launch Community for IndyWiki itself
which is the seed from which the IndyWeb can grow over time
// This one is already an example how given the right inrastructure
when wiki pages that individuals compose can be shared by their creators in their own trust networks and in fact on the indy web weaving their own autonomous permanent evergreen networks of interest based social networks the Wiki itself goes virtual and the Network becomes the Global interpersonal Interplanetary Wiki
with the ability to Wikify the existing Web itself
But this time people can do it for themselves
do not go to some central place
but share and just connect!
One can associate with any page on the web a wiki page of their own personal or community wiki
over he web so in that sense Wikify The Web itself!
The esence of the Wiki has been the move that allow it to expand the networks mutual learning by its ability to invite one to name and create a new page whenever in a narrtive associated idreas come to mind that are relevant
The difference between the original wiki and the IndyWiki lies in
the way links and pages are named
and the associated reinterpretation of a link they entail
IndyWiki is inspired by Federal Wiki in two threads
It is author centric and allows interpersonal/wiki sharing and collaboration
reuse and creating non linear networks of pages
and its focus on extensibility and as a vehicle of actions and personal digital work
Federated wiki also made the move of eschewing relyance of data bases and in fact using HTML files as storage format, that was by construction amenabe to be tinkereed with at scale
content and the way one interacts with the content
On both accounts by removing the bottlenecks created by relying on an infrastructure that is srver based, localtion based
Search: /hyperpost/๐/๐ญ created after 17/08
Name | Directory | Size | Created |
---|---|---|---|
index.html | /hyperpost/๐/๐ญ | 3.3 KB | 2025-8-19 11:03:10 |
index.html | /hyperpost/๐/๐ญ/gyuri/โญ | 3.44 KB | 2025-8-19 10:53:54 |
index.html | /hyperpost/๐/๐ญ/gyuri/do/๐ | 0 Bytes | 2025-8-19 10:50:27 |
index.html | /hyperpost/๐/๐ญ/gyuri/do/web/search/via/search.brave.com/๐ /20/25/08/03 | 24.7 KB | 2025-8-17 12:13:34 |
โญ | /hyperpost/๐/๐ญ/gyuri | 0 Bytes | 2025-8-19 10:53:35 |
7.53 GB / 200 GB
Upgrade
hyperpost ๐ ๐ญ
hyperpost
$ indy.web players Human Actor Model