♖/hyperpost/🌐/🎭/index.html
web: ♖/hyperpost//🎭/, edit,"♖/hyperpost/🌐/🎭", via.hypothes.is,hypothes.is
- stub : This is the Origo document for all Exploratory Experiential Experiments as Essays
$ 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 only
- interchangeable
- interoperable results
- but InterPlayable
- IP3 Inter-Personal-Planetary-Playable
- Not just Scaling Reach and Synthesis but
- Weaving Ihe IndyWeb of Open Structures, Constructs and Collaboration
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
- for the last three days I've been using CK Editor heavily as I was doing experiments
- creating new structures in hyperpost's webhosting directory
- experimenting with creating index.html files as a way to get started
- then within that folder relegate named paragraphs as proto.dots
- all assuming that from named paragraphs dots can be generated via suitable functions
- in any context.
- This means, that need to extend CK Editor with that ability
- ad in fact map documents to dots
- and rely in MindGraph as the Univrsal Intentional Document Constructs
- which is not juest a matter of data encoding and representation but coupled with on the one hand Universal Presentational and morphic interations and transofrmational capabilties
- Just as HTML rich Text Editors provide such unification
- HTML as universal information representation with built in ability for vanilla presentation
- and in fact a whole infor-norphic infrastructure with the abiulity
- to change Presenation
- orhestrate interactions
- functional transfomation
- and indeed associated storage mechanism that are coupled with communication
- sharing publication infrastructure that is the Web!
4~notation=Paragraphs are nameless Dots
☑️dev-revert.to~CK.Post.Editor
- long time ago, in October 2024, in a long forgotten,
- Peergos Website directory called ASite
- replaced later with the current one using the utf8code as its name 🌐
- acting as hyperpost's own Peergos Web Hosting folder
- I have done some experiments
- 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
- I am revisiting it as I wanted to change the use of fonts for
- HTML Rich Text documents created by CK Editor Peergos Custom App
- so that it uses a different front, not monospace, but arial
- which I find much more readable
4=omnioptiopnality-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
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 |
- LauncherLauncher
- DriveDrive
- SharedShared
- NewsfeedNewsfeed
- SocialSocial
- CalendarCalendar
7.53 GB / 200 GB
Upgrade
hyperpost 🌐 🎭
hyperpost
$ indy.web players Human Actor Model