♖ hyperpost

root folder for peergos name hyperpost

about ♖ - hyperpost

peergos.path: 


stub

This is the wikinized about page for the root folder for the ♖ Peergos Name: hyperpost

hyperpost is an Indy.Name for a capability on the indyweb

The indyweb is an autnonomous named spaces for 


human actors as players/participants ideas and capabilities all supported by a 

Great Progenitor Infrastructure


actors names three  types of named participants/players 🃏

  1. players 🃏 individual human beings using nicknames that in du course can be turned into
    •  full fledged inyweb players with their owned peergos account names
    • granted the capability of creating their own circles of
      • frineds
      • contacts
      • whatever they wish to create
        • all instances of huddles
  2. indy labs network of people groups coming together to pursue some named mission, vision or collaborate on named topic of shared interest

  3. sites corresponding to domains on the legacy web



old.stub

this is the about page for your new wiki. Change its name and add a description to it by clicking on the link Wiki Settings on the left panel or on this page


#

dev.note - customize empty wiki page

Now that we have Feather Wiki installed as our own named Peergos Custom App

carefully setup in a web accessible folder so that anyone can access and edit the wiki and save it to their own file system

and later should be able to save it by sending back the modified wiki to the original author of the wike using

asynchronous peer to peer channels



gotchas #

Peergos has a time limit on the editor being active.

In the very likely event that you exceed this limit and you get a message unable to save


the workaround is

  1. before you do any editing
  2. right click on the link on the left of the page that you wish to edit and open it in a new tab
  3. This will open the page for editing in a new tab with the editor occupiying the whole window tab and show the title of the page being edited
  4. You can have several pages like that open
  5. If you fail to save it
  6. then close the Peergos.net link to the wiki
  7. and reopen the wiki you've been editing
  8. Switch back to the tab that shows the page you failed to Save to Server
  9. Press save again and it will save

Clue Marks

This part of the IndyWiki provides the space to write about the Clue Marks that are used in IndyWiki


Clue Marks /

dev.note


designates topic for a development note





Taliho



Move Fast and Break Things


Move Slow and Make Things

about ♖ - hyperpost /

Great Progenitor Infrastructure




stub


I started referring to a concept I've made up called Universal Infrastruture

modelled on the concept of Universal Machine. I am eploring an alternative name for it

omni-emulative infrastructure or whatever will emerge from this attempt at articulation


intial formulation

an infrastructure capable of emulating any conceivable infrastructure in principle

with different non-functional requirements, constellations and architecture


The bet here is that if you develop an infrastructure that is people centred relying on asynchronous communcation infrastructure it could be used to support any capabilities realized in any other infrastructure in its own ways

It may not be what you want, It may be that a centralized model is what you want to have

but looking from the point of view of individual human beings, who may value autonomy privace, they can indeed have the same apps and networks of affordances and capabilities recreated in this one omni-emulative infrastructure


The immediate goal is to prove this for the web and demonstrate that any capability that exists in the centralized legacy web can have a new version of it that respects human's need for autonomy and privacy.


At a later stage it may well be the case that if you have that kind of infrastructure to start with one can create "emulate" and satisfy non-functional requirements of centralized system


The bet is that that itself could actually radically better then what exists as long as low latency is not essential to the operation of the system.





there for decoupling the application domain concepts and affordances from the infrastructural concerns




reonceptualize


let's face it I am groping for a new concept here, something needed to be named


consider the concept of "Universal Machine" as our initial name for the Elephant in the Room 

(the focus of our intent laden attention)


Public
(www.ratioscientiae.com)
“The Blind Men and the Elephant” written by the poet John Godfrey Saxe.

blind men and the elephant

acknowledge that the concept of "Universal Machine" arose from a specific context as people were touching the first part of the "Elephant in the Room" perhaps its's tail


I want to explore another part of the Elephant let's assume that it may be its trunk


in many ways this metaphor captures the many similar features that are shared


first step is to shift the focus to an eisting feature of what we call Universal Machines which brings in the concept of emulation


in thse terms one can say that a Universal Mahine is one that can emulate any other machine given its description


If we focus our attention on how these description can be obtained and aiming from the start to discover a better way of creating drscription that are available. this aim implies what we may call augmenting articulation with the restriction that articulation should be systematic, within a suitable computer support that helps us manage the complexity of the task, and in fact is designed around the concept of the Universsl Hyper document idea, which we may subsequently rename with the new name we are groping for


the current proposal is omni-progenative descriptions that is to say decription that are amenable to be interpreted to ehibit desired system behavious affordances Human Computer Interactions that are capable of supporting ertain tasks or the creation of digital artifacts that can act as effective models for a given domain


Let call that "domain" the "application domain" it is a misnomer or even a miscocneption to itself, one of the root causes behind what is referred to since 1969? as The Software Crisis





a self-contained autopoietic infrastructure that satisfies a constellations of values serving human autonomy as a moral commitment embodied in the systems we create


In the discussion the use of the word universal lead to misunderstanding

echoing my own unease regarding the concept of Universal Machine or Universal Function itself


it really should be called "omni-emulative machine" in view of the fact that given a suitable description any machine using this omni-emulative machine it is capable of emulating the behaviour of the machine we have a description of


This is really the great PUN of Symbolic Progenitation that Sussman referred to in the context of explicating the Universal Function the evel/apply of LISP, the Great progenitor of all LISP functions/programs as John Allen calls it in The Anatomy of LISP

the eval/apply mutually recursive definition of LISP ite

as a self referential, homo-iconic  meta-circular description of an "universal" (omni-emulative) machine/function when that is implemented in a computer it can interpret/exectue any function/program described by it




alternative account - emulation


I've seen alternative trails curated by others that explores this very same on the face of it totally different formulation using the concept of emulation in digital systems to articulate these ides





Now this is a really deep and take a long time to appreciate concept


one that Sussman 30 years later referred to it as the greatest most impactful idea that got formulated in the 20th century




see snarf.telegram - Great Progenitor

about ♖ - hyperpost / Great Progenitor Infrastructure /

Snarf-telegram - Great Progenitor

stub

gathering manually snippets from Telegram channel 

https://web.telegram.org/a/#-4532427129

starting with


search.telegram = progenitor


comment.trail = recursive

stub

leading to the "great progenitor"

> indyweb dev - innotation
- Moonshine : Mü oonshine : Mü  I'm working with Gyuri now on
    - innotation on
        - Feather wiki within
            - Peergos.

> adjacency
- between
    - intonation in Feather Wiki in Peergos
   - your story of etymology of glossary
- adjacency relationship
    - This is reminding me of your 'gloss' story of monks leaving space between written lines of text
        - so that in the future,
            - when others or they themselves are reading the text,
        - could also be writing emergent ideas inspired by the reading between the lines.

    - I've discussed with Gyuri that one thing artificial I've noticed about annotation is that
        - it creates two different levels,
            - the content and
            - the annotation that is sitting outside the original document.

    - With innotation, it reflects how timebinding itself works. Namely,
        - the new idea is written and embedded within the text itself at the point where the inspiration occurred.
        - hence you have captured the cause-effect relationship of your new inspiration
    - this structurally captures the recursive nature of timebinding,
        - older existing ideas interacting with a new consciousness that stumbles upon it and
        - resonating with it due to interacting with ideas in the reader's salience landscape
    - Since the innotation is inline, it can now be read as a nonlinear continuation of the original discourse,
        - a jumping-off point of you will
    - This is using hyperlinks in a timebinding manner
    - If it results in a new page of information, then it has given birth to a new subtopic of inquiry
    - I'm going to try innotation on the latest article I annotated referred by Kim,
        - the David Hinton article on Emergence magazine.
    - I haven't written a summary for that yet.
    - If I innotate this, we can compare annotation with innotation


Where there is "Recursive" there is inter-being


> Gyuri Lajos: The Great Progenitor the recursive functions Eval and Apply on symbolic expressions and their computations by machine is Mutual Recursive the strange loop the chicken and the egg > Gyuri Lajos: Add people into the mix you have a trefoil a Celtic knot