/next/0.0.2/index.html

/hyperpost/♖/indy/0/pad/next/0.0.2/

// master ♖ document

Created this document under ♖ Peergos Constellation
so that it can
merge snippets/pages in a multipage document
- created originally using the 🧊 InterPlanetary Constellation as part of its
- instance first experimental setup for such work.
Much of that 🧊 InterPlanetary Constellation was documented there as it was developed using a version of the inyd0pad
- https://ipfs.io/ipns/k51qzi5uqu5div1auuxm59ygav4p7gdg9z4e9iggtu6m43rmc3xw75mczx2b7x/♖/indy/0/pad/📝
- but now it is critical document the work in one constellation
- using the other
- thereby ensuring that what is used for documentation
- is on that is meta-stable
created in the InteroPlanetary constellations
- and this is an attempt to
- consolidate and connect that to one creatd using
- ♖ Peergos Constellation

rely on ipfs in favour of ipns dweb links

on Asus side 🌐☯🦁indy@zen

create folder for the asset folder of a Peergos Custom App
- created a folder named 📝 in the pad folder for the asset folder of the next version of the peergos custom app: next/0.0.0.2/assets
  - This in fact is a good way to extend a Peergos Custom App stup such that it could be used on the IPC (interplanetary constellation)
This can thus be use to have a shorter name for the app to be used
- so we can have
- https://bafybeihkeomfd7tdaqzsdowons6ywybfl3xafxguuzx5qdytydfwgwphoe.ipfs.dweb.link
- this as the link to the editor
- https://bafybeihkeomfd7tdaqzsdowons6ywybfl3xafxguuzx5qdytydfwgwphoe.ipfs.dweb.link/indy/0/pad/📝/
and for the document say at

Files/🧊/♖/indy/0/pad

working on the IPFS side

https://ipfs.io/ipns/k51qzi5uqu5div1auuxm59ygav4p7gdg9z4e9iggtu6m43rmc3xw75mczx2b7x/♖/indy/0/pad/📝/?path=../next/0.0.2/♖.indy.0.pad.next.0.0.2.html&isPathWritable=true

working on the peergos side

add some stuff from Telegram

/hyperpost/♖/indy/0/pad/next/0.0.2/ChatExport_2025-11-22/messages.html

https://k51qzi5uqu5div1auuxm59ygav4p7gdg9z4e9iggtu6m43rmc3xw75mczx2b7x.ipns.dweb.link/📁/ChatExport_2025-11-22/messages.html

save to peergos and republish

steps are

copy new page from ipfs version to Peergos equivalent
save it

use-ipfs.io

publish to IPNS

used local gateway to walk the folder tree the ipns link
tried dwb.link
tried it with ipfs.io

got links

https://ipfs.io/ipns/k51qzi5uqu5div1auuxm59ygav4p7gdg9z4e9iggtu6m43rmc3xw75mczx2b7x/♖/indy/0/pad/📝/?path=../next/0.0.2/♖.indy.0.pad.next.0.0.2.html&isPathWritable=true

Storage {../next/0.0.2/♖.indy.0.pad.next.0.0.2.html: '<h2><strong>/hyperpost/♖/indy/0/pad/next/0.0.2/</s…y through the medium of hyperPlex documents s</p>', toOrbit: '[]', title: '/next/0.0.2/♖.indy.0.pad.next.0.0.2.html', filePath: '../next/0.0.2/♖.indy.0.pad.next.0.0.2.html', S3c533f1: '{"t":"start-all","s":"stub - start-all","i":"edit/…,"ct":1763040648,"le":1763040648,"lu":1763040648}', …}
1. ../next/0.0.2/♖.indy.0.pad.next.0.0.2.html: "<h2><strong>/hyperpost/♖/indy/0/pad/next/0.0.2/</
2. S3c533f1: "{\"t\":\"start-all\",\"s\":\"stub - start-all\",\"i\":\"edit/icons/dot.png\",\"a\":\"S3c533f1\",\"d\":\"dot\",\"ct\":1763040648,\"le\":1763040648,\"lu\":1763040648}"
3. filePath: "../next/0.0.2/♖.indy.0.pad.next.0.0.2.html"
4. title: "/next/0.0.2/♖.indy.0.pad.next.0.0.2.html"
5. toOrbit: "[]"
6. length: 5

do remember to copy this new page into the peergos hosted version

@props

@view: /hyperpost/♖/indy/0/pad/next/0.0.2/
@sandbox indy0pad.next // hyperpost@tp
@filename: ♖.indy.0.pad.next.0.0.2.html
indy0pad@ipfs: https://ipfs.io/ipns/k51qzi5uqu5div1auuxm59ygav4p7gdg9z4e9iggtu6m43rmc3xw75mczx2b7x/♖/indy/0/pad/📝/
@dweb.link:
- https://bafybeifxgigrodkxqywpu7o7ytdynk5ysmkq7vc4cdvxhahx6oppicua24.ipfs.dweb.link/?path=https://bafybeihoj5ig5aqugp2rpiz7x6wpes6w6rryfsyoha26aumtr3mvrpk5fi.ipfs.dweb.link/&isPathWritable=true
- - If the above works,
    - dweb.link to indy0pad on IPFS
    - with path on IPFS Desktop on Asus Zen to
      - 💻/🧘‍♂️/🧊/♖/indy/0/pad/next/0.0.2/assets
      - the current indy0pad
    - with parameter path
      - ?path=https://bafybeihoj5ig5aqugp2rpiz7x6wpes6w6rryfsyoha26aumtr3mvrpk5fi.ipfs.dweb.link/
      - &isPathWritable=true
        the dweb link of an earlier version of this document
  - hen the path towards developing the autopoietic plumbing for the first cycle of the evolutionary spiral of the Permanent interpersonal interplanetry autonomous Indy Web would have proved to be open. Ready to be used to document itself.

/hyperpost/♖/indy/0/pad/next/0.0.2/index.hpmi

secret.link

> renamed from : /hyperpost/♖/indy/0/pad/change.log/0.0.2/

@links: sandbox next an0tate

experiment - indy@zen - setup.via - IPFS

milestone - mirroring constellations across devices

For a long time I realized that I need
- to use two laptops interchangeable
- one dedicated to writing the other
- to experiments
- interchangeably
- so that I can document new stuff
- in a previously establsehed meta-stble constellation
- on another device
And at last the setup is working
- .
I can use
- IPFS to mirror any folder across devices
  - under new named folder paths
    - naming focal context for work
  - on another device
  - so meta-stable and devlopment constellations
    - are clearly deparated
- Yet rely on the Universal Information Exchange mehanism
  - that is secure, private and available cross devices
  - called Copy Paste
  - rely on Rust Desk
    - to allow me to control two devices from one lptop
    - and copy content from one to another!
  - This means that I can record/document work on one laptop
  - in another!

$ purpose

experiment in mirroring IPFS Desktop running on ThinkPad to be mirrored in part on Asus Zenbook identified as 💻/🧘‍♂️
launch indy0pad@IPFS
- @💻/🧘‍♂️/
  - Created by mirroring the CID for the
  - entire IPFS infrastructure constellation 🧊
  - partially mirroring indy Peergos account
  - ♖/indy
  - setup for 0/pad indy0pad on my ThinkPad IPFS
  - 🧊/♖/indy/0/pad/next/0.0.2/assets
- once it is mirorred on my ZenBook laptop using IPFS Desktop there
  - managed to setup using indy/0/pad there
    - as 💻/🧘‍♂️/🧊/♖/indy/0/pad/next/0.0.2/
    - I was able to edit the index.hpmi file thre
    - like so
    - - and document that work on the Peergos side right here at the equivalent path
      - but the index.hpmi file has been renamed back to index.html
    - as shown below copied from the working setup on zen
  - 💻/🧘‍♂️/🧊/♖/indy/0/pad/next/0.0.2/assets
    - at http://bafybeifxgigrodkxqywpu7o7ytdynk5ysmkq7vc4cdvxhahx6oppicua24.ipfs.localhost:8080/?path=http://bafybeiggjarhhehi4advrlthl3skujat3uyw4ltwueabyviiwafaefxlve.ipfs.localhost:8080/&isPathWritable=true
    - 💻/🧘‍♂️/🧊/♖/indy/0/pad/next/0.0.2/assets?path=index.hpmi&isPathWritable=true
    - 💻/🧘‍♂️/🧊/♖/indy/0/pad/next/0.0.2/index.hpmi

/hyperpost/♖/indy/0/pad/next/0.0.2/index.hpmi

do.how - share documents ready to be annnotated via IPFS

.Would like to have this document to show up in my own annotation stream
That is easy
- download the file
- upload to corresponding IPFS folder
- set the canonical name
- as https://hyperpost/.co/♖/indy/0/pad/next/0.0.2/index.hpmi

experiment - creating new document and copy across

just created a new index.html file in

💻/🧘‍♂️/🧊/♖/indy/0/pad/next/0.0.2/

duplicate this split window

get share link popup

from there copy its cid as bafybeiczsscdsbs7ffqz55asqdf3smv6klcw3gofszvwlyarci47bgf35

save the documentcopied across document space on Peergos

copy the new CID and change the path for the open editor

bafybeiczsscdsbs7ffqz55asqdf3smv6klcw3gofszvwlyarci47bgf35

http://bafybeifxgigrodkxqywpu7o7ytdynk5ysmkq7vc4cdvxhahx6oppicua24.ipfs.localhost:8080/?path=http://bafybeiggjarhhehi4advrlthl3skujat3uyw4ltwueabyviiwafaefxlve.ipfs.localhost:8080/&isPathWritable=true

http://bafybeifxgigrodkxqywpu7o7ytdynk5ysmkq7vc4cdvxhahx6oppicua24.ipfs.localhost:8080/?path=http://bafybeiczsscdsbs7ffqz55asqdf3smv6klcw3gofszvwlyarci47bgf35.ipfs.localhost:8080/&isPathWritable=true

.next

= self-hosting
= topic map
- next
  - /hyperpost/🌐/🎭/gyuri/=/t/m/=/topic/map/
- - autopoietic
  - autopoietic topic map
  - history
  - From the moment I learned more about Topic Maps from
    - Jack Park and Marc-Antoine Parent
      - especially being pointed towards the
      - TAO of Topic Maps
- Jumping context can be handled by creating new named topic quest context and use them as catch and dispatch modes for
  - facilitating conPlex switching
  - the variance of named context (topics identified by a carefully chosen combination of words 2 - 4 typically
  - Using word combinations as topic designations
    - can also double as search terms!
  - I wish I have started using them earlier

// new element add next link

which is the sandbox link to dit current document with the next version of the Peergos Custom App
.test - ^

add file extension ‘hpmi’ short for
Hyper Plex Mark In document which is
a conservative extension of
- a document created as Hyper Text MarkUp Language using an Rich Text HTML Editor like CK Editor
- in the sense that it can be edited with vanilla Rich Text HTML Editors
- As it contains TrailMarks MarkIn Notation which is valid HTML
This is in contrast with document created using Mark Down
- that generates HTML from plain text
- Mark Down relies on Humans as Users Universal Capacity
  - for Learning
  - so that people capable to learn and carry the cognitive load
  - of using plain text mark down notation
  - using a plain text notation that is
  - amenable to the PUN,
  - to be interpreted by suitable markdown processors
  - to generate HTML with the desired formatting
  - automatically
  - to obtain visually Rich in clues to hints to intent/role/affordance HTML documents with WYSIWIG formatting
  - that common for documents with appropriately styled elements on the web like
    - Headers, emphasis italic bold, images even tables
- Althoug HyperText can be written as plain text
  - but it uses Mark Up to indicate formatting document element presentational intent and other visual effects
- However it results results in a text that is
  - much harder to read and write
  - then the Mark Down equivalent
HyperPlex MarkIn notation and the interactive mrphic editing envirooment, in contrst,
- proposes a new approach
- It proposes a mark In Notation for Rich Text HTML documents
  - that is added in line to the prose taht one would otherwise write
  - Makes use of bolding, italics and other typographic conventions
  - and adds a disciplined use of nested lists
  - or outlines
- At any point, using this inline notation remains to be a
  - visually appealing rich Text HTML
- The pervasive use of nested list structures would be familiar for people who used Writely or Roam Inspired Networked Thinking Tools
It also relies on the universal user's capacity to take on extra cognitive load to overcome the limitations of existing machine(ry)
The learning curve may be deeper, not steeper.
- That is to say, to learn MarkDown may be more of a challenging in use then in learning
- Learning to use TrailMarks may be a greater conceptual challenge
- But in every day use it is much less distrcting and
- easier to practice
- and it is way more powerful
Not so much when working with a single documents
but because it can completely dissolve document boundaries
so that 1s entire written work is created/curated/developed as a unified
space of articulation/formulations with a host of readily available capabilities which are not only userful/critical in themselves
but they are all integrap part of a holonic whole
.
The workflow is uniform repeatable and infact personalizable etendible, exaptable, designed to be personalized
Most importantly it is self-hosting self-extendible, personalizable
tinkerable in depth and in scope and reach

that is easy to read AND write then either Mark Up or Mark Down
it relies on vanilla WYSIWYG editor capabilities
so we have all the benefits of easy of writing nd reading associated with suitable ayed out and formatted HTML pages
Plex format has two parts
One is a systematic naming conventions that provides for structuring of information within named folder structures which are implied by the naming conventions used on a Plex Page
.
fomr Mind Dumps to MindGraphs to MindPlexes to HyperMaps that
ARE the territory

The naming convention is grounded in the notion of what we call Clues

while at the same time invites 1s to capturae the and reflect the nested nature of ideas

with implicate salient high resolutions cross referencing trans/in/clusion and reue of named blocaks

HyperPlex

.purpose

There are many HTML editors
But Indy 0 Pad is based on CK Editor and is an WYSIWIG HTMKL editor
but it also been extended to add TrailMarks ark In notation and automorhic capabilities
that

in HTML

It uses TrailMarks Hyper Text Mark In Notation so that these documents

are to be created by Open Commons Baed Peer Produced

info-morphic-multiplayer communcation infrastructures

that ensure that every document is

created in an infrastructure that guarantes full control by their creators'
- ownershi, have their all the documents/spaces that they engaged with avsilabile
- local-first and on the IndyWeb vietual cloud
fully attributed verifieably to their authors
- the authors themselves hve stable veifieable pseudo identities
- that are created/attested by individual huan beings who are already part of the IndyWeb People's networks that itself is autonomous,etc
full history that is replayable and recapitulable
- If a is granted access to view the document, that implies access to its full history

and amenable to support the following processes

weave their own web of bidirectionally and meaningfully

Gyuri Lajos, [02/11/2025 08:26]
Thanks

Gyuri Lajos, [02/11/2025 08:32]
Created indy 0 pad as a Peergos Custim App based on CK Editor Peergos Custom App

Gyuri Lajos, [02/11/2025 08:33]
It is a conservative extension in the sense of whatever it produces remains a Valid HTML dicument

Gyuri Lajos, [02/11/2025 08:47]
And a generative exaption through class-free inheritance through mix-in additional JavaScript modules that add new capabilities while preserving the full HTML comparibility

Gyuri Lajos, [02/11/2025 08:50]
Producing named info-morphic autopoietic mutual arising explicitly intertwingled bidirectionally high-resolutionally linked (where the links themselves are explicitly intentionally named weaving their own meta plex space) verifiably attributed versioned HyperPlex documents with recapitulable history of co-laboration weaving a space of associative complexes hyperPlex documents that themselves constitute an interplanetary permanent mutable field of documents as externalyzarion of individual and co-laborative mutual human learning symmwthesy through the medium of hyperPlex documents s