/09/5/index.html

♖🌐 .🌌💬.🎭.📓
Univ3rsal Virtual Resource Name
UVRN: ♖/hyperpost/🌐/🎭/gyuri/📓/2025/09/5/index.html

Gyuri's Daily Notes - 2025 Sept Week 5

: props

drive: ♖
player/actor; hyperpost
host: /hyperpost/🌐/🎭/gyuri/
folder: 📓/2025/09/5/
view.file: index.html
sandbox: /hyperpost/🌐/🎭/gyuri/📓/2025/09/4/
sandbox@indy0: /hyperpost/🌐/🎭/gyuri/📓/2025/09/5/
web: ♖🌌💬🌐/🎭/gyuri/📓/2025/09/5/
annote: ♖🌌💬🌐/🎭/guri/📓/2025/09/5/

= Universal Virtual Inter Planetary Inter Personal Hyper Morphic Document System

Inter Playeable Massive Online Open Multiplayer Conversations
- Weaving the Indy Learning Commons
Following the trail blazed and explored by Engelbart named as
- Universal Hyperdocument System (OHS)
- and reviving the eekim.com: OHS Launch Community eekim.com
- gyuri (edited 4/28/2025 3:43 PM) 6/27/2023 9:16 PM
- https://via.hypothes.is/https://eekim.com/ohs/lc/
- https://hypothes.is/users/gyuri?q=ohs+launch
Approaching it from a Wholistic, Integrl, Experimental, Exploratory, omnioptional
- ViewPoint Perspective
- can arrive at a broader practical concept of Hyperdocuments/Media
- characterized by being constructed as a
  - autopoieticbootstrppable
  - extensible
  - lively, morphic concept of a document
  - that is created by using a notation so that each document is
  - amenable to be presented in a universal way
    - much like workflowy
      - but instead of interacting with an app
      - going to the website for that service
      - the document and the capabilites needed
      - are available on the User's machine as
      - web apps that once accessed
      - aare alway available in thebrowser
      - can even work offline
      - can use just any Rich Text Html Editor
      - that is customized/plugout to oepn capabilities
      - that log out to appropriate
      - oen commns based peer produced infrastructure constellations
        like the one we are deeloing
        called indyWeb
        but as it is not just open source
        but Open Sauce, and Open Constcuts eerywhere
        unenclosabl, unstoppabple constellations
        permanent
        yet evrrgreen
        becase the documents are always shipped with the ability to work with them
        and sicne the way they are structured are universal
        amenable for
        reuse, repurpose, refactor, extend tinker modified
        to suit users own needs
        and in fact it is built with the idea
        of Softwae being a Symmathetic multiplayer conversation
        through time
        and in fact individual work itself is consstructed
        as a ,utliplayer collabroration
        between multiple identities associated with the slef
        through time
      - and all affordances, interactions and transformation
      - are designated using the markin notation and naming
      - and a provision of associed interpreatative
      - morphic capbilities
      - that are cnstcuted using
      - a common Open Source, Open Sauce
      - Open Cosntructs
      - like Peergos Cusom Apps
      - or a nice exampe integrated into the sytem wold e
      - https://peersuite.space
  - utilizing a homoiconic mark in notations
  - that has a univorm universal canonical Presentation
  - that is to say all document ae constructed
  - structured
  - presented in a same way
  - yet are amenable to be turned into a MEMplEX
  - associated complexes of Dots
  - that are
    - attributed to their creator
    - with guaranted permanent availability
    - full provenance
    - autdit trail
    - versions
    - in al workeable universal storage/retrieval characteristics
    - that can be imlemented using a variety of prorocols and platforms
    - that are all by construction interoperable, nay interplayeable
    - borm multiplayer
    - where the players hav permanen pseudo ids
    - whee personal learning work and collaborative work
    - are interplayeable and able to form acoherent interplanetary
    - indranet or work playces
  - ,
- This document is an instance first eemplar of such a document
.contrast with MrkDown may be helpful
- Markdown uses palin text input
- witj notational convention that impart
- presentational aspects
- It lets 1 focus on tent and structuring
- and use the mark in notation that allows the arkd down txt to be presented in
  - customary visual form
- This way the content is decoupled from the means or presntation
- provides a n interpretable format that is amenable to the pub of being interpreted to produce
- the intended Presentation
- - It is kind of Whay You See is What You the author
  - explicitly mark down and intended to see
- . Mark In Intentionak in line innotations in contust
  - are based on a limited subset of WYSIWYG Rich Text Editing Capabilities
  - It workes directly with HTML
  - uses Open Source Web Based Editors like CK Editor
  - made available by the System
  - and uses a Mark In Notation
  - or writing conventions that are
  - exensibale,maleable tinkerable
  - It is all possible because this format itself is
  - Lively and Morphic
  - that is to say is delivered in a lively morphic self-hosting bootstrpable
  - infrastructure that is based on a concept of document
  - that considered the Content (RePresented using HTML Javascript and CSS, that is open technology
  - such that all 1 needs is a browser
  - and the document content th HTML is always shipped along with
  - the very capabiuities needed to present and interact with it
  - provide morphic transformation and presentationa capabilities
  - in a coherent complete permanent yet future compatible unit of sharing
  - And proivdes all the means necessary for
    - collaboration
    - version controls
    - attribution
    - audit trail
    - recapitulable fulll verifiable history
    - of the co-evolution multiplayer collaboration of its becomming
- Start with a name that capture your focus of attention
  - the name has two parts
    - intent
    - subject-object
      - of yor focal attention
    - create outline structure
    - where every list item can itsel be a dot
      - e.g. name your intent
      - and the subject of your focus
      - and spell it out in nested outline
  - Eventually all these nedted dots will be torned into a node in a
  - Global giant kind of HyperGraph
    - carrying audit trail link as verifiable links to the author and the itme context
    - versions
    - and all conversations anchored in annotations
      - bot within hypothesis
      - or in shared private indranet.work spaces
  - As in here, one can just create a document like this
    - can enter new Dots at the top level
      - and trust that the system will turn them into dots
      - and replace the content for the dot with a klink to a dot
      - and leave a HyperMap of the immediate associated neighbourhoold
      - of that dot
      - thant neihbourhoold includes
      - salient summaries
      - and two level down outline of all connected dots
      - both going out or
      - indeed all trails taht lead to that Dot
      - from anywhere!
      - That is to say
        The creator of a dot
        will have a verifiable list of all
        thoese dots in theentire IndyWeb
        that links to that Dot
      - That accomplishes by consrcution
      - of all backlinks pointing to any resource
  - Note all rsource have a
  - = Universal Resource Name
> search-result - univesal hyperdocument

refine/update document properties
- so that they reflect the copying of Week for 4 document
- into Week 5 folder
  - use hypothesis annotation to point to specific part of the document
- with a linkoriginally

// do.how
- started using checklist
  - right after the block it refers to as a comment
- If the first character on a line following an empty line
  - if fiollowedby a space
- or actually a double forward slash followed by a space
  - that significes in line comment
- has special interpretation

^.🎯 purpose

A single page as an entry point to daily work
- Keep track of everything need keeping track and a record
- Especially ideas that come to mind in context
- Be on the same page with your vision
- combine it with task
- fervent active hope to success in 1's endeavour
- on the journey of exploration and hope
practically it involves curating everything that needs to be brought in mind to succeed
- not loosing any adjacent ideas that comes to mind
- pursue IT as attention flows
- to persist in that flow
.🗺️>
- .☑️<🔝>☑️📂 prioritize > tasks
  - ☐ create own version for CK Post Editor for indy0
- .☑️<⏳> ☑️📂 in.progress - ☑️tasks
  - .☑️>create 🔤 alphabetic listing of 😀 emojies
  - .☑️>refactor root web hosting folder

Anything before this page break is a copy of Previous Week's notes

Need to change it to make it work for the current week

Trying to figure out how conservative extensions/continuation/resumption later should work

♖🌐 .🌌💬.🎭.📓

Gyuri's Daily Notes - 2025 Sept Week 4

folder: /hyperpost/🌐/🎭/gyuri/📓/2025/09/4/
sandbox: /hyperpost/🌐/🎭/gyuri/📓/2025/09/4/
sandbox@indy0: /hyperpost/🌐/🎭/gyuri/📓/2025/09/4/ https://bciqd3usbvlc3m25hkqgxalnc4l7dyztxwcbglttuo73rxkm76vkc4wy.peergos.net/index.html?path=/hyperpost/%F0%9F%8C%90/%F0%9F%8E%AD/gyuri/%F0%9F%93%93/2025/09/4/index.html&theme=&username=indy0&isPathWritable=true

web: ♖🌌💬🌐/🎭/gyuri/📓/2025/09/4/
annote: ♖🌌💬🌐/🎭/guru/📓/2025/09/4/

^.🎯 purpose

A single page as an entry point to daily work
- Keep track of everything need keeping track and a record
- Especially ideas that come to mind in context
- Be on the same page with your vision
- combine it with task
- fervent active hope to success in 1's endeavour
- on the journey of exploration and hope
practically it involves curating everything that needs to be brought in mind to succeed
- not loosing any adjacent ideas that comes to mind
- pursue IT as attention flows
- to persist in that flow
.🗺️>
- .☑️<🔝>☑️📂 prioritize > tasks
  - ☐ create own version for CK Post Editor for indy0
- .☑️<⏳> ☑️📂 in.progress - ☑️tasks
  - .☑️>create 🔤 alphabetic listing of 😀 emojies
  - .☑️>refactor root web hosting folder

. ⏳✍️write.to.do<

attempt to re-
- factor
- imagine
- from top to bottom
- focusing on facilitating
  - URN for on the IndyWeb
describe what I am trying to do/achieve and
- articulate, write to think as I do IT
'cause Ideas through Work Must Flow

☑️.🔝 prioritize > 📂. ☑️ tasks

.☑️>create 🔤 alphabetic listing of 😀 emojies
.☑️ > 🔄 - 🗂️.✳️-🗺️ biject- folder-plex-trails
.☑️> use emojis in folder name

.☑️<⏳- ☑️📂 in.progress - ☑️tasks

.☑️>create 🔤 alphabetic listing of 😀 emojies

.use.of ~ qualifiers< > trail terms ~ subject | object

// this one is a bit hazy, unformed
for composition of terms forming ground atomic clue formulas
- I used to use the hyphen character ' - ; surrounded by spaces in clues.
- This is still the baelinepractice where the writer is allowed to be sloppy
  - nd epect to povide a sharper formulation at a letr stage if
  - warranted and wish to make te ==he discourse more specific
  - and better though ot
- the ‘verb’ part of what used to be called rhemes
- which is a pair or verb prases and object designation
Going beyond triples we an have subject in the sense
- of the semantic webs subject there,
  - what the predicate is about
  - that can be marked with the use of a tilde ~
    - to indicate that the verb/intent/qualifier phrase refers to
    - in that case
    - this concept of subject is really identifying the subject mattr of the discourse
  - experimented using = to broaden that concept of subject
  - to a topic and in fact aim to be capturing, formulating the notation
  - soo that it can be thought of as taking inspiration from the topic map practice
  - and attempt to provide a metaricuar elaboration of Topic Map
    - that is to say take the route that was not followed
      - .see - TAO of topic map metacircular
        .NB whenever
  - and expanding the the topic maprtraditio
    - This is particularlyb-
  - .
- .
.

.do.web.snarf>emoji-🍿-popcorn.html

.do.essay
- // try in writing
  - use the > operator to name the result of an action/indy.sevice call
  - formulate a fully worked out exemplar
  - possibly in stages
  - document the process possibility
  - including morphic interaction/processes/workflow with results
  - so it can be emulated, repeated
  - and eventually implemented
- < goal
  - save the web page on IPFS so it can be annotated
  - https://via.hypothes.is like
- < steps
  1. propose an eventually “true name” for it as given in the name for this clue
    - or use one in the process of trials and development
    - // as in this case
  2. Use SingleFile chrome extension
  3. Save the page, name the file appropriately
  4. Upload to IPFS Desktop in the right folder
  5. Pin it locally and via Pinata Custom Gateway that is configured
    - Searching takes considerable time
      - perhaps because I am not running IPFS Companion
        turn it on to see next
        ☑️ repeat the process to see if turning on IPFS companion makes a difference
  6. replace name of custom gateway here ipfs.indy0.net with ipfs.io
  7. add parameter for the filename
provid

☑️.🆕 create~🔤 alphabetic listing of 😀 emojies and trail-terms

alphabetic.list 🔤 - input_latin_letters
associated adjacent thought - 💡💭
- adjacent associated -💡 light_bulb
- 💭 - thought_balloon
create new 🆕 - NEW_button
cycle 🔄 - counterclockwise_arrows_button
dig/do/hack ⛏️ - pick
drive ♻️ - recycling_symbol
- drive
  - Peergos
write ✍️ - writing_hand
- write.to.do - ⏳✍️ - writing_hand
folders 🗂️ - card_index_dividers
- ☑️📂 in.progress - ☑️tasks
  - // use 🗂️ < indicate collection
in.progress -⏳ - hourglass_not_done
prioritize 🔝 - TOP_arrow
map 🗺️ - world_map
- 🗺️-
peergos ♖ - white-chess-rook
- - is.a - drive - ♻️
- - one.of
  - IPFS 🧊 - ice
  - MEMplEX ✳️ - eight-spoked_asterisk
  - peergos ♖
plex ✳️ - eight-spoked_asterisk
- 🔄 - 🗂️.✳️-🗺️ biject- folder-plex-trails
🔄 - counterclockwise_arrows_button
- 🔄 - 🗂️.✳️-🗺️ biject- folder-plex-trails
search 🔍 - magnifying_glass_tilted_left
research 🔎 - magnifying_glass_tilted_right
think 🤔 - thinking_face
horizontal zig zag 𜺰

⛏️.search.for-zigzag

https://www.compart.com/en/unicode/block/U+2980

hyperpost.peergos.me/🎭/gyuri/📓/2025/09/4/

XXX

. 📆.day>2025-09-4-Su

Save previous day's daily notes in Dot folder structure

explore the shape of things by manual operations
/hyperpost/🌐/🎭/gyuri/📓/2025/09/4
/Dots/📆/day/>/2025/-/09/04/Sa/index.html
. 📆.day>2025-09-4-Sa
secret.view: link
from.folder : link
dot.folder: link
sandbox: 📆.day>2025-09-4-Sa

Save today's daily note in Dots folder structure

.result.
- 📋.props
  - path: /hyperpost/🌐/🎭/gyuri/📓/2025/09/4/Dots/📆/day/>/2025/-/09/04/Su/index.html
  - in.trail: /hyperpost/🌐/🎭/gyuri/📓/2025/09/4/Dots/
  - dot: 📆/day/>/2025/-/09/04/Su/index.html
  - file: link
  - sandbox: 📆.day>2025-09-09-Su/
- .
.

save image manually in current folder

. 📆.day>2025-09-4-Sa

!>saved.in
- secret.view: link
- dot.folder: link
- sandbox: 📆.day>2025-09-4-Sa

. day>2025-09-4-Fr

keep track, in reverse chronological order
- of what I am doing on my other laptop
- via rustDesk with the ability to copy paste accross devices

.☑️>refactor root web hosting folder

so that I can start a new
- the index.html in the webhosting directory back in January was created using
  - dyWiki an extended version of FeatherWiki now renamed as index
  - view
  - that experiment was abandoned for it was really hard to work with
  - you really had to be somewhat of a developer to cope with its complexity
  - Still it was a good learning experience
  - One good thing about feather wiki was that it could just be downloaded
  - and when it was opened it became a live web app
taking into consideration recent learning and achievement
- use CK Post Editor
  - on anther machine so it can take screenshot into l
  - locaStorage
  - as the original
  - hyperpost browser profile
  - pretty much reaches it 5 Mb limit
  - and the next major development task will be
- ☑️ to.do - save documents saved by CK Post Editor
  - in localStorage keyed by path into plex structures on
    - HyperPost PeergosDrive
      - mirroring Mind/
      - HyperPlex Maps
      - in folder structures
      - using and extending existing MindGraph Library
    - .
  - .
- .
- ☑️ to.do - document

. day-2025-09-4-Th

☑️ setup for instant/continuous development

now that I figured out how
- I can use Peergos CK Editor with my own customizations
- that allows me to use it without the danger of loosing what I am writing
I am ready to setup for
continuous documentation & development and real time collaboration, call and screen sharing
On one machine I can do development, research and anything else
On another I can do writing and make calls and screen share

. demo - IndyWebScratchPad

I've developed IndyPad ( the Rich HTML Editor for WikiNizer over a decade ago
- designed to allow WYSIWYG editing of HTML content as Dots that are wowen into a MindGraph
- It allowd pasting in HTML content from the web
- and also supported switching to source view for allowing HTML o be written edited directly
combine this with Agregor's own Dweb ScratchPad
- and host both on IPFS in a same namespace
- and we have a Web Development environment design for
- use by anyone without any setup of tools
.
.

. demo - Agregor's DWeb Scratchpad

. do.how

As this document is dedicated to creating running notes
- I am adding new Clues at the top
I am using Plex/TrailMarks'
- intentional
  - Universal Resource Naming Methodology
    - conventions such
    - that they are amenable to the PUN
    - that resources named using appropriate
    - infomorhic infrastructure of the IndyWeb
    - can actually be used to
    - Create Curate and share those uniquely named resources
      - with their own permanent names,
      - in the creators own(ed) Indy/Indra/Net Work Spaces
      - that are exlusievely under the creator's control
      - with life-long, or even beyond permanence
      - with full provenace and audit trail of all changes
      - that are private to the particpants who created/contributed to them
    - and for conversations
      - that are continupous, recorded, with full attribution
      - provenance, privately by and for the participants
    - that translates into Universal Resource Names
    - that not only identifies resources on the IndyWeb
    - that in turn can be resolved to real Web URLs dynamically
  - in-notations and
    - that is being designed and developed for the purpose
      - of bootstrapping the IndyWeb as an
        Open Universal HyperDocument System

.⛏️ .❓ do.how - using two laptops

setting up on two laptop mode of operation
I have
- Thinkpad in front of me, using its keyboard
- Asus stack up on boxes using its screen hinge so it is lifted up above the line of the Thinkpad
That means I have the ability to write/document what I am doing
- while I am doing it on the ThinkPad laptop in front of me
I've been using at least two machines two keyboards and mouse parallel
- for the best part of the past 4 decades
This time, thanks to
- RustDesk
- I can have one small window opened on my Thinkpad
- remotely operating the other one
- Best of all,
  - I can take a screenshot on any screen
  - and paste the image in to the document I am writing
  - where I document the work I do
  - - This is the Asus screen with resolution set to 1366x768
That means I have just one keyboard
- can fully control the other machine all I need to do is to move the mouse over the window where I see the other machine in a window
- Once I have done that I can use the other machine's mouse that gives a more precise control
- while using the one keyboard
This setup is needed also for
- calls.
- The call window is opened on the machine with the raise screen
- while at the same time I can take notes on the other machine
- or indeed share my screen
- Using
  - https://p2p.mirotalk.com/
  - https://chitchatter.im/
  - https://peersuite.space/
  - or any of the others like zoom or calls that I do not initiate
- .
.

https://hyperpost.peergos.me/%F0%9F%8E%AD/gyuri/%F0%9F%93%93/2025/09/4/

prompter

work around Peergo's limitations
- cannot work simultaneously on multiple documents
- Save can fail, need a way of working that is reliable
Peergos provides a an infrastructure shell that combines the benefit
- of Personal Computing and Cloud Computing
- Yet supports primitives that can be leveraged to develop infrastructure of
  - Personal first
  - Local first
  - deliver of Open Commons Based Peer produced capabilities
    - in the form of Peergos Custom Apps
  - which can be exapted to realize the vision of the IndyWeb.
- InterPersonal Virtual Cloud based multiplayer collaborative learning work
Peergos, as it designed and constituted, would not allow multiple documents to be worked on parallel.
- But we must be able to do that
- There will be a workaround
But since our approach is exploratory, experimental in the sense of doing much of the work
- on Perrgos as is and intending to extend and exapt it
- and shape it to be one of the possible infrastructures that can get the
- IndyWeb off the ground and into the Virtual InterPersonal Cloud
Here I wish to demonstrate the current workaround
- Which is workable but no for the faint heared
The work around involved the etension and customization of the existing Peergo Custom App
called CK Editor
.
I costumied it to make the first necessary step to develop a full work around
.
Agenda
- showing how to setup work with multiple documents
- Demonstrate the efect of two important modifications
- .
- First is to ensure that the most important part of the path to the document we work with
- NB documents are but index.html information aout what the edocument is about can be gleanded from the document oath
This is a critical feature because it can be exapted to reflect the intertwingularity of MindPlexes in appropriately devices folder structures that are DirectedAcyclic Graphs Trees really