♖/hyperpost/🌐/🎭/gyuri/do/web/search/via/search.brave.com/📅/20/25/08/03/index.html
title: ♖.🌌📮/🌐-🎭~☯️gl-▶️-🌐.🔍-🦁/📅/2025-08-03/📇
web
via.hypothes.is
edit
test
https://www.compart.com/en/unicode/block/U+2460
name to icon mappings
♖.🌌📮/🌐-🎭~☯️gl-▶️-🌐.🔍-🦁/📅/2025-08-03
| ||
|---|---|---|
| ♖ | peergos | |
| hyperpost | 🌌📮 | |
| gyuri | ☯️gl | |
| do | ▶️ | |
| web | 🌐 | |
| search | 🔍 | |
| brave.com | 🦁 | |
| 📅 | ||
| 20/25 |
| |
| hyperpost | 🌌📮 |
🌌📮https://www.compart.com/en/unicode/U+1F4EE
Sat-23-Aug
☑️ creating Files/Shots folder for Screen Shots
hyperpost
// originally created with CK Editor
self.links
https://hyperpost.peergos.me/🎭/gyuri/do/web/search/via/search.brave.com/📅/20/25/08/03/index.html
https://hyperpost.peergos.me/🎭/gyuri/do/web/search/via/search.brave.com/📅/20/25/08/03/
goal
The overriding developent principles are
Use HTML as a Universal Morphic information exchange/storage format
which is amenable to be processed by ad hoc functions that one can develop and incorporate and compose readily
The idea is that anything that one does in a browser manually can be automated
So work with instance first exemplars and see to it that at every step of the way
what 1 sees and engages with is appropriate to the envisaged desired work flow
document it
paly with it
use it
to refine it to the point when 1 is content wit it
then figure out ways to name and structure the steps
into named javascript modules
arrange for the contained functins to be called in approriate combinations
and eventuallyarrive at an end to end coplete work flow to e used
the process
Started using SingleFile browser extension to create self contained faithful html version of web pages I want to save, especially searches
I saved the pages in a dedicated folder
uploaded them to my IPFS Desktop and pinned them both locally and on my own Pinata Custom Gateway
Originally what I wanted to do is to save web searches, but wanted to upload them to Peergos
Hence the experiment of creating the folder structure presented here
This one solves a lot of interconnected concerns
just by the naming and the structure
first it is a matter of attribution
As with everything the IndyWeb is
Person-first so the root of the structure should be the name of an Actor
or rather an IndyWeb Player a 1 I and
an nick named individual human being whose intellectual capacities we wish to augment with all of this
All this relies on the PUN that folder names double and correspond to trailmarks or intentmarks
defined in MindGraph dots
why.this
This ♖Peergos folder
♖/hyperpost/🌐/🎭/gyuri/do/web/search/via/search.brave.com/📅/20/25/08/03/index.html
and this document is part of an ongoing experiment
for figuring out how 1 I (one individual, me)
can start to bootstrap/create/curate flip the existing web,
from being centralized, benefitting the providers instead of the participants to one that is People-centric, for the benefit of the participants, who actually are themselves are also providers, and co-creator of the means and services that they create/rely upon to weave the IndyWeb, the Person-first, InterPersonal Web that why completes and plays nicely with the existiing web opens up new possibilities and alternatives as InterPersonal Virtual Cloud computing
Privacy, security , permanence local-first autonomy
There re many (novel concepts involved, new ways of doing things), its an integral vision
with highest premium on permanence, availability yet easy of change
It is a vision of home brew, people-first, interpersonal web of autonomous software in the long tail of the internet, that is not only open sourced, but Open Constructs (easy to emulate extend repurpose, compelling to use) a new world of software where each app is born interpersonal and interplay-able with any other virtual cloud service, and even the with legacy web
The key idea is that by construction information is not separable from its creator, the individual human being. and the very communications/conversations that involved in its formulation.
That changes everything. a New View Point and a New paradigm
shifting focus towards human needs not the need of machine processes,
through autopoietic exploration, experiment creating instance first exemplars of working with and developing ideas, projects that articulate engage in formulative thinking and dreaming in a new way of writing about radical new ideas, projects, ways and means and affordances that allow the realization of the dream of creating software support for personal learning that is contiguous with interpersonal collaborative knowledge work, or rather learning work or mutual learning symmathesy, autopoietic creativity
constellated inside out, bottom up, middle out,
production of new software capabilities by way of prototyping
novel universal ways of working, create by doing exploratory experiment, using
existing and emerging nascent capabilities focusing constellation not so much on development
Integral, omn-optional, one that scales simultaneously to creative learning and synthesis with Reach
aimed at creating documents that themselves go virtual
and infrastructures that are also operate as Virtual Cloud Software as a Service
combining the best of cloud based software delivered as a service with
Personal computing, local-first People-first computing that is home brew
but itself operates at the new frontier of Inter Personal Computing
and idea promoted by Steve Jobs 30 years ago but got forgotten,
The goal of the IndyWeb is to add a new dimension to the Web characterized by
verifiable provenance, recapitulate-able history of contributions and the coevolution of ideas,
personal First Autonomy of participants in the network with Interpersonal connectivity
and collaboration that can be private, secure, permanent evergreen, future compatible for life long mutual learning and beyond.
but most importantly figuring ot ways of creating software that clearly separates concerns about
domains and the supporting infrastructures
so that we can figure out ways and means through experimental exploratory developments aimed at figuring out the ways and means of creating documents formulated fashioned to accomplish specific goals and exhibit desired affordances in a limited application domain
but developed in a way that relies on universal co-evolvable means for
representation and presentation of information with affordances and experiences that are built on a common universal autopoietic means that work as
local-first, personal setting that itself is multiplayer, collaborative
where individual work is considered to be collaboration between 1 self and past selves
Using Open Constructs that are not only Open Source but Open Sauce
Software tools and technologies that are
commons based, Peer produced capabilities, Web Apps,Brower Extensons, Web Apps like
Make use of home brew experimental exploratory technologies/apps like
to put together a Universal Open HyperDocument System, like OHS was
and something like the Engelbart's dynamic Knowledge Repository
doing it so that we can at long last have a viable combination of Structure and Collbaoration
that pioneers like Ted Nelson and Doug Engelbart and many others dreamed off and worked towards establishing
Do mention Topic Maps Topic Quest
Semantic Web
that
figure out how we can create Open Learning Commons that can bootstrap the very infrastructure that enables the creation of
new technological substrate for "Computer Support for Personal Knowledge work that naturally extends into Computer Supported Collaborative Work.
Create an exemplar that would be easy to emulate compelling to do.
Initiate processes that can bootstrap such systems,
This is also a conceptual experiment aimed at creating
through practical experiments
a conceptual construct that can articulate formulate
the intents, purposes and ways, as well as
certain key aspect of weaving the IndyWeb
as the way to progress to the next stage.
This involve many mutually interdependent concepts and intents,
pursuits and long view preoccupations
in this experiment I am focusing on the following aspects simultaneously based on earlier experiments
Questions of
In an emergent a wholistic autopoietic order
that supports bey the way it works, operate and interplay to maintain
baking into the system forward compatibility
permanence
and co-evolvability so that radical refactoring is always possible
For this reason all these concerns has to be reflected in the structures that are to be created
I mean here folder structures hierarchies, rails and pathways
that are themselves designed to be changeable
The simplest way to ensure this is that at a suitable point all structures are created within
timebound structures
Like here we start with structures that help us to identify, intentional structures capabilities/activities
One of the long term directions that I focused on, was to reimeaging the Actor Model on the assumptions that the actors are Human Players
ACTor model where the available actions in any context are named and laid out in self describing
context-revealing folder structure
which are by constructions extendible and themselves are timebound
so are the ways and when the available intentional context are identified an made available through these structures
we have a timebound structure for the information that is to be created /curated etc
This is a kind of fractal structure
The goal is that in any identified time period capabilities and information should be kept aligned
ready for use available permanently in their own intertwingledness modulo time
refactor-timebounding activities/capabilitis too
The pun is to use name trails that convey nature of activities pursued under ‘do’
and make themselves timebound
Since we need mutual arising of capabilities/processes and the information that they create/curate/collaborate with
let's refactor extend
we had started with
relections
/hyperpost/🌐/🎭/gyuri/do/📅/20/25/08/web/search/via/search.brave.com/📅/20/25/08/03/index.html
change it to
This naming convention implies a monthly resolution for designating the start of the time period for which they can be applied
As soon as new future time periods are introduced everything under that folder will be created to work within a time period that start with the new one
Notice the focus is not on the artefact or a named capability to be used
but the capability itself is incorporated in a context of information
but he incorporation of capabilities within 1's players own work!
Reimagine the Web as a Universal Permanent Co-evolvable medium for
People-first, Inter Personal InterPlanetary Interplay weaving
and interest based soical networks of Open Collaboration
where people are able to do it for themselves create/curate/coevolve Open source and Open Sauce
info-communicaiton-infra stuctures and software in the long tail of he internet
what's cooking
Created a folder for named indy actor hyperpost@peergos.me
a subfolder for that 1 as an indy player called wit the nickname gyuri called ‘do’
Playe names are created by holders of named Peergos accounts
The acont holder is responsible for all the information they create/curate/share/ and conversae with others
The number f new players that any such individual account holder is able to create
is limited by the fact that they immply real human engagment to activate, maintain and persists
These players form their own networks of networks
Each individual can be created mutile pseudo names across multiple Peergos Name spaces
and in fact any individual can operate any number of Peeros accounts
again these are limited beause each require individual attention which is the scarcest yet most potential valuable resource
that is an entry point for all info-communication-collaborations that 1 engages with
where all pertientnt resources are owned and stored within an interplay of autonomus decentralied technologies that promote persistence and coevolvability
not only of the information created/curated/shared/conversed upon and collaborated upong
but encompssing the same qualities for all the means of computations capabilities that are being used in its own creation/curation
Actor Model for Hyman Actors called a player referred to as 1
Ready Player 1
to distinguish itfro the original Actor Model
In many respect this is intended to be a much extended Actor model
where we can leverage the fact that in this model Actors are not computations
but computations that are invoked within an intentionally transparent medium a named network of web pages and folders that are owned and created and curated by humans
as universal users of an Open (not just information but source of cod being used communcated to be ready to
be used, emulated extended and compelling to do
as it is self0describing
where people not only own their means of computations
but it is ceated to be an Open constrct ready to be tinkered with
made it home brew, pople are enabled to do it all for themsleves together
as it is also Open Sauce,
all that is needed to understand and make suse o these capabilities are laid out in a plane
easy to explain and comprehend and use
that is to say
universal hyper document system UOHS
Refer to as a Player Model
https://hyperpost.peergos.me/🎭/gyuri/do/web/search/via/search.brave.com/🏛️/20/25/08/03/index.htm
hyperpost.peergos.me/🎭/gyuri/do/web/search/via/search.brave.com/🏛/20/25/08/03/
https://hyperpost.peergos.me/🎭/gyuri/do/web/search/via/search.brave.com/📅/20/25/08/index.html
syllabification-syllable-vs-hyphenation.html
📅/20/25/08/03/
syllabification-syllable-vs-hyphenation.html