player: /hyperpost/🌐/🎭/gyuri/

trail:/♒

doc: /index.html

web: hyperpost.peergos.me/🎭/gyuri/♒/

title: ♖🌌💬/🌐/🎭/gyuri/

♖: Peergos Account

🌌 hyper

💬 post

🌌💬

.purpose

☑️ Setting up (Info/Communication/Collaboration/Work Flow) Streams
- for the IndyVerse/Web's envisioneer Gyuri the seed engineer for the Indy/Verse/Web
- https://hypothes.is/a/2nUZlL3aEe-010_zuWArMQ
.
☑️ Provide an entry point to the resumption of work on
- https://opencollective.com/open-learning-commons/projects/indy-learning-commons
All this is work in progress,
- with the twist that all the work here is instantly available and hosted
- by the Peergos Account hyperpost
- and is amenable to be annotated using hypothesis
- Thereby facilitating conversations that are
  - Open
  - Continuous
  - without being Synchronous
- and eventually contiguous with each participants
- Personal Indy Learning Commons Spaces!
This document is in fact a portal to a
- Virtual Instant Autonomous emergent Community
  - formed from all the individuals who engage with
  - this shared document
  - by annotating any part of it.
- By doing so, if that engagement is genuine, they would be granted their own
- IndyWeb pseudo identity, so they can build trust and engage in deeper collaboration
- and weave their own bit of the IndyWeb.
- All this without signing up or signing in
- Building a network of Trust scaling mutual Trust and Reach and growth of
- Autonomous mutual learning and understanding and collaboration
.

.caveat.venditor-IndyWeb

Years of learning and exploration and long term collaboration over 2-6 years, convinced Us
- Gyuri, Gien, Alen, Parmjit Yarrow, Wendy, Charles, Flan, Paul, Michael, Grace
that the Web We Need can be readily characterized by saying that everything we have needs to be FLIPed
The IndyWeb is the Flipped Web.
An alternative to the existing Web
- that plays nicely with the one that exists,
- as it does provide tremendous value,
- even if it is created for the benefit of the providers not the participants.
Right there the IndyWeb seeks to empower the participants in the networks
- to empower individuals to be their own
- “providers” and Vendors themselves,
- of all of the virtual services and apps they use,
- not only of the information that hey share and collaborate with others,
- but the very capabilities they make use of, and by implication they own, as in the OC days
- and share it with others in their owned networks, limited to fair share principles
The above is a clear example.
- On the IndyWeb, that makes software available that is created curated by individuals
  - in the long tail through personal connections
- Some of the software like Peergos, Pinata and other essential infrastructure services
  - People do need to sign up with and even pay for those services
  - but only if they wish to operate their own collaborative-cooperative services for their own communities
  - or want to have their owned Peergos Names
- But everything they create with those services remain under individual's own control
  - or at least can be mirrored in infrastructure like Peergos that provides strong guaranties
- for people to Control their data, to control their destiny
So as the title of this Dot suggest it is the opposite of caveat emptor
- meaning - Buyer be aware
and emphasizes Users Responsibility (as providers of information and virtual services themselves) to exercise cavet.venditor: “Provider Be Aware”
- all that software is not only
  - Open Source (LGPL) but
  - Open Constructs and
  - Open Sauce
    - Instead of providing services built with secret sauce
    - share the very ideas and technologies that empowers the networks
    - as a fulfillment of DigLife Collective's by line
    - A tech we can trust for a world we want

gyuri

Jan 19, 2020

Public

on "About the Collective – Digital…"

(diglife.com)

Tech We Trust technologies that prioritize our autonomy, privacy and dignity. Our tech, not their tech.

autonomy, privacy and dignity

the right watchwords in the right order, wow

The reason that it is possible, because at the heart of it the IndyWeb connects Inividuals
directly
some of these individuals may form their own named dedicated communities of practice
- that is to provide for their own communities first
- and ineviatable will be scaling reach beyond what is possible for individuals
- so probale wome kind of share alike and sharing in the commons will need to be
- adhered to
- But again it is not “Buyer Be aware”
Even there it will never be a provider customer relationship
but a provider of virtual autonomous participants owned co-laboration-operation as a service
so there will be no customers only participants
but participants in a dedicated network

.conPlex

🥇🧩-🎭📰 winning.constellation-Indy.Wiki

.IT'Story

.the.point
- the story so far. How, and why and for whatever for did I ever get here to create this document?
for the past two years I've been seeking a
- workable
- autonomous
- autopoietic
- commons based
- Open
  - source
  - constructs
  - sauce
- constellations of technologies and methodologies
- to seed the IndyWeb
that is to say to create a Universal Open Hyper Document system
- inspired by the example of the OHS Launch Community
  - .gotcha - need to click the button HTML to see the search result!
  - // We are making it all as we go along
    - The guiding design/implementation strategy is
    - to be able to do everything needed by hand
    - in a way that would allow us to document what's is being done
    - with a view to creating on the fly the very capabilities that needed to be constellated to automate/improve those steps eventually
    - eliminating those very manual steps
    - We are in the business of describing personal/Interpersonal
    - information-workflows in a way that leads directly to the creationg
    - of morphic processes that makes those steps availabe as self-revealing/documenting affordances that are introduced into the flow
    - as the work context demands
    - .true.meaning.of-Open.Sauce
      - Instead of focusing on defensible novelty
      - we are aiming to make the know.how do,how required
      - explicitly formulated so that those formulations are
      - instantly available for collaboraive feedback threaded named conversations
      - the outcome of which would be Open Sonstructs
      - delivered within a Trust Networks and networks of trust based
      - Software in the long tail of the IndyWeb
    - .principle-Open.Autonomous.Use
      - Anything capability that people access on the indyweb would be made available to them as Progressive Web Apps or equivalents
        as the Peergos Motto put it
        Control yOur Data, control yOur destiny
so they should work in a way as to create all the data to be available on their own devices
backed up by Virtual Cloud Software as a Service
that respect their ownerhhsip, privacy and autonomy of the proeucts
of all their engagements
that would enable the practical realization of an extended version of the original intent
in the form of a
- Universal Hyper Document System
  - that is powered by an
  - Autonomous
  - Autopoietic
  - Self-conveying
  - constellation of means and autoscaling infrastructure for
  - Info-Storage-Communication-Collaboration Spaces
  - that are
  - unenclosable, unstopable spaces
    - that are
      - controlled by its creators,
      - for the benefit of the participants, and that are also
      - a self-scaling, permanent, evergreen, future compatible, People-first, Local first, safe, secure, co-evolvable,
      - born multiplayer collaborative conversational
  - capable of weaving the Indy Learning Commons
  - where everything is fully attributed, with full verifiable, recapitulate-able history and provenance
‘Cause It’s ain't what u do but the way that u do IT, that's what get results
So at long last we are getting close to get the IT, the envisioning, right, at long last, so it can actually be REALised, together

.acknowledgements

I, Gyuri Lajos the lead envisioneer of this system over two decades have been working closely with a number of people for the past 4 years, people who understood the goals of the effort and helped me through deep conversations, much of it in writing on Telegram
who are brave enough to be joining and collaborating on weaving the launch community for this whole vision
all under the name of the Minimal Workable Constellation hosted at
hyperpost.peergos.me
Will be posting entry points to this work on
https://opencollective.com/open-learning-commons
- https://opencollective.com/open-learning-commons/projects/indy-learning-commons

.name

// Peergos account name for owner
/hyperpost
- // web site directory designated in account profile
- /🌐 web
  - // folder for indyweb actor/player.s
  - /🎭 player
    - // name of an indy player
    - /gyuri account@hypothes.is
      - // in this case the name of a hypothesis account
        for the owner of the the hyperpost Peergos account
        the indy envisioneer pio-engineer of the IndyWeb itself
      - what kind of an account it is it will be reflected in the
      - associated meta-info-folder 0 within the folder for gyuri
        will have a folder named is
        that in turn will be trail part of the clue
        is-via-hypothes.is
      - // folder tree for information arising/related to on going
        activities by the named individual above is engaged with
        organized as a timebound chronological tree that the
      - /♒ stream
        .folder.tree-👨‍💻development-♒stream
        // new-innotation-move
        started bold font at the beginning of a line with an initial dot
        for clue names
        Just realized I can jus use that as an inline crossreference mechanims
        that should work both on page and when the clue is transcluded
        in a transparent interaction flow

.purpose

folder trie for storage and organizing and interacting with information related to named activity streams

.occasioned.by

keeping track of development work
create a timebound trie auto archiving conPlex structure

.meta-narrative_subject.object.distinction

// making it UP as I go along
- for-innotational.conventions
- .background
  - for a long time I've been experimenting with notational conventions
    - exploring and discovering the proble/solution space through practice and experiments
    - clue names are composed as ground atomic formulas
    - utilizing a mixture of prefix notations and in subparts infix notation
    - the baseic unit of formulation is a rheme
      - verb phrase and a
      - noun phrase
      - .contrast_this
        with triples formed of
        subject
        predicate
        object
    - an ordered pair of
      - one.of
        intentional
        conplex
        trail
        clue
        marks
        acting as Verb Phrases or qualifiers
      - and a
        subject or
        gloss-subject
        subject are marked with the prefix character ~
        simple-object.designation
        gloss-simple-object
        simple object designations are marked with the prefix character-
        composite-object.designations
        the beginning of a complex object designation are marked with the prefix character _
        the end is not maked because in cluenames as ground atomic formulas always come in pairs
        cluemarks and subject or object designations
        Can form clue trails such that after an subject object designation
        can introduce a new clue name with a hyphen which in turns can form trails of cluemarks sequnces separated by hyphens eventually ending with a subject ~ or an obect designation if it is the last -
        or again a composite object designation starting with a _
    - where

.folder.tree-👨‍💻development-♒stream

// named networked info-tree for development work streams
- in-/hyperpost/🌐/🎭/gyuri/♒/
/👨‍💻 development
- // folder-tree for information organized along time dimension
- /📆 timebound
  - /2025 year
    - // month ordinal number
    - /09 month
      - //ordinal number for the week within the month
        starting at 0 if the day is not Monday
        otherwise 1
      - 1 week
    - .
  - .
- .
.