/11/5/index.html

/hyperpost/🌐/🎭/gyuri/📓/2025/11/5/

@props

prev: indy0.peergos.me/1/gyuri/⭕/0
view: /hyperpost/🌐/🎭/gyuri/📓/2025/11/5/
sandbox: indy0pad.next
web: https://hyperpost.peergos.me//🎭/gyuri/📓/2025/11/5/index.html

daily notes - 5th week of November 2025

@nexus - /hyperpost/🌐/🎭/gyuri/📓/2025/11/5/

// savelinks here for adjacencies
/hyperpost/🌐/🧊/
- 📰 IPFS based IndyWeb constellations
  - https://bafybeicjq5b6pl3jvijbo2mirispldkheg6dfpac3bsxofjshvxn7svvyi.ipfs.dweb.link/
  - ?isPathWritable=true&path=/♖/hyperpost/🌐/🧊/
/hyperpost/🌐/🧊/0/
- Origo Folder - hyperpost web directory on IPFS
/hyperpost/🌐/🎭/indyweb/scratch/

Sun 30 November 2025

checking open browser windows

gatehering all actively worked documents into this browser window
sorting out this which is a mess
- - the but around pinning ice is now added to the active document
the other one is the I about
- 📰 IPFS based IndyWeb constellations
  - completing Peergos & Opidox
  - converging, confluencing towards closure
  - © gyuri@hyperpost
- http://k51qzi5uqu5div1auuxm59ygav4p7gdg9z4e9iggtu6m43rmc3xw75mczx2b7x.ipns.localhost:8080/📝/?isPathWritable=true&path=../♖/hyperpost/🌐/🧊/index.html
- - on IPNS

interplay - IndyWeb-Peergos-IP(F|N)S-PeerSuite

the latest exploriment established that
- Agregore's extension of the Fetch API in a wat that it works for IPFS
- instead of directly working with legacy web servers
  - supports the publishing resouces on the Inter Planetary File system
really opening the way to
- treat/develop/customize
  - Agregore Apps into Peergos Custom Apps and vice versa

Sat 29 November 2025

restore daily notes 5th week of November

the document was created by an earlier version so it did not have the new improvements of the latest version of indy0pad
- need to up the version number
like font settings and hypothesis embedded
In any case the Peergos hosted one would require the use of via.hypothes.is
which is a deal breakwer as far as relying on
♖ Peergos for web hosting
- OTH - on the other hand
  - it is also a new deal maker between
  - Agregore and Peergos
    - in the sense that Peergos can solve the problem of securely saving/sharing
    - IPNS Keys so that people can share them with trusted parties
    - and even create one's for them
    - thereby providing a way of sharing privaely
    - such keys relying on Peergos Secret Links
    - This can also act as theoposite of Zero Knowledge Proof
    - but proof of mutually established autonomous identities and connections
    - we could add to this a third element that would be
    - peerspace.suite channels
    - which could also be mirrored via IPFS Pub Subs ephemeral, rotating channel names
- All this to deliver the wholly grail, secure, private/public/friends networks
  - where anyone in the nextwork can secure verifiable pseudo identities for their
  - own connections invitees with zero friction
    - So with one person who is signed up with Peergos
    - or run their own Peergos Servers
    - Or their own IPFS desktop and capable of managing IPNS Keys
    - and pub-sub/p2p keys for Peersuite.space or equivaleng
Much better to use🧊 IPFS for that
and keep Peergos as an
- named archive,
- search
- secret links and
- key management
- pubs-sub channel names
- named trails
- versions
If you want reliability robustness you need redundant systems

setup - agregore ipns

trying to open document being edited in Brave with localhost ipns and path /peergos/hyperpost/web/ipfs/0

http://k51qzi5uqu5dgbxv41hai7p8b9ogr56dmv25aauie1vk41deezn0h7qf8o9ppy.ipns.localhost:8080/indy0pad/?isPathWritable=true&path=/peergos/hyperpost/web/ipfs/0
Now copy the stuff form the verion that was saved by Agregore
- http://k51qzi5uqu5dgbxv41hai7p8b9ogr56dmv25aauie1vk41deezn0h7qf8o9ppy.ipns.localhost:8080/indy0pad/?isPathWritable=true&path=/peergos/hyperpost/web/ipfs/0
- saving looks good
  - - Now try to reload
    - took a liitle while but not too long

checking with IPFS Desktop

republish under key

The capstone for this cathedral is provided by Agregore which is not just a

Web Browser but is a Web Weaver
ipns://k51qzi5uqu5dgbxv41hai7p8b9ogr56dmv25aauie1vk41deezn0h7qf8o9ppy/indy0pad/?isPathWritable=true&path=/peergos/hyperpost/web/ipfs/0/

Major breakthrough

setup for editing in agregore is working

Fri 28 November 2025

had a bit of a mostly over nighter

focusing on finding a way to create
- IPNS powered permalinks to HyperText
  - would be HyperPlex pages
- pages

Thu 27 November 2025

how.did.I.get.here

Trying to close a few windows on ThinkPad
- transfer some of the work to Asus
Latest I had developed a few changes to the Indy 0 Pad
- changing font and embedding hypothes.is see

☑️ add formatting changes to ck editor presets

do that first on the Peergos side

just add this to the CK editor template
<script src="https://hypothes.is/embed.js" async></script>
<style>
body {font-family: Roboto, sans-serif}
Change the name for the app
I think I have already done that
added this to
- let css = 'body {font-family: Roboto, sans-serif}'+

IPFS Desktop updated

IPFS is Running

Initializing daemon...
Kubo version: 0.38.2
Repo version: 18
System version: amd64/windows
Golang version: go1.25.3
Kubo repository at C:\Users\indy0\.ipfs has version 16 and needs to be migrated to version 18.
Looking for embedded migrations.
Running embedded migration fs-repo-16-to-17...
applying 16-to-17 repo migration
> Upgrading config to use AutoConf system
updated version file
Migration 16-to-17 succeeded
Embedded migration fs-repo-16-to-17 completed successfully
Running embedded migration fs-repo-17-to-18...
applying 17-to-18 repo migration
> Migrating Provider and Reprovider configuration to unified Provide configuration
updated version file
Migration 17-to-18 succeeded
Embedded migration fs-repo-17-to-18 completed successfully
Success: fs-repo migrated to version 18 using embedded migrations.
PeerID: 12D3KooWBtA9yLero8KRM6Gmnj7UZz8odBr38FtjtR1kopC4HGwd
Swarm listening on 127.0.0.1:4001 (TCP+UDP)
Swarm listening on 169.254.131.86:4001 (TCP+UDP)
Swarm listening on 169.254.150.118:4001 (TCP+UDP)
Swarm listening on 169.254.247.147:4001 (TCP+UDP)
Swarm listening on 169.254.47.220:4001 (TCP+UDP)
Swarm listening on 169.254.49.29:4001 (TCP+UDP)
Swarm listening on 192.168.0.17:4001 (TCP+UDP)
Swarm listening on [2001:4c4c:151f:5600:3c69:38e5:db64:1db7]:4001 (TCP+UDP)
Swarm listening on [2001:4c4c:151f:5600:4c91:259a:7fe8:7bf8]:4001 (TCP+UDP)
Swarm listening on [2001:4c4c:151f:5600:6047:3a3a:9aef:25ec]:4001 (TCP+UDP)
Swarm listening on [2001:4c4c:151f:5600:62b4:a86c:306:3eac]:4001 (TCP+UDP)
Swarm listening on [2001:4c4c:151f:5600:9514:c857:fd08:f64a]:4001 (TCP+UDP)
Swarm listening on [::1]:4001 (TCP+UDP)
Swarm listening on [fdaa:bbcc:ddee:0:3c69:38e5:db64:1db7]:4001 (TCP+UDP)
Swarm listening on [fdaa:bbcc:ddee:0:6047:3a3a:9aef:25ec]:4001 (TCP+UDP)
Swarm listening on [fdaa:bbcc:ddee:0:7b38:5c17:256b:12e5]:4001 (TCP+UDP)
Swarm listening on [fdaa:bbcc:ddee:0:9514:c857:fd08:f64a]:4001 (TCP+UDP)
Run 'ipfs id' to inspect announced and discovered multiaddrs of this node.


ℹ️  Anonymous telemetry will be enabled in 15m0s

Kubo will collect anonymous usage data to help improve the software:
• What:  Feature usage and configuration (no personal data)
         Use GOLOG_LOG_LEVEL="telemetry=debug" to inspect collected data
• When:  First collection in 15m0s, then every 24h
• How:   HTTP POST to https://telemetry.ipshipyard.dev
         Anonymous ID: da0a630e-7e67-410b-ae21-5a3cca22c9dc

No data sent yet. To opt-out before collection starts:
• Set environment: IPFS_TELEMETRY=off
• Or run: ipfs config Plugins.Plugins.telemetry.Config.Mode off
• Then restart daemon

This message is shown only once.
Learn more: https://github.com/ipfs/kubo/blob/master/docs/telemetry.md


RPC API server listening on /ip4/127.0.0.1/tcp/5001
WebUI: http://127.0.0.1:5001/webui
Gateway server listening on /ip4/127.0.0.1/tcp/8080
Daemon is ready
Close

xxx