/hyperpost/🌐/🎭/gyuri/index.html

self

• prn: ♖-🌌💬/🎭/gyuri/ 
• prin: ♖-🌌💬
  • .0 : permanent resource iconic name
    • which in turn is a Trail Mark Term
    • that can be mapped to folder structures
    • and back
    • when a a Clue Named Resource is shared 
      • in a Website directory associated with a Peergos account 
      • the hyphens in the name are mapped to nested folders
    • hyperpost.peergos.me
• web.link: ♖-🌌💬/🎭/gyuri/
• edit: link
• hypothes.is: link

edited

.purpose

• This folder is the portal to my virtual networked virtual personal spaces
• It is created under the Peergos Name hyperpost
• in its
• under the
• 🌌💬

 

provide-listing

motivation

• index.html files especially in folders that are web accessible are ideal to
• provide an over view of what's contained and all related work
• Rely on this while integration of Peergos and IndyWiki is The IT is developed
•  

wiki > reinterpreting links

• This is an idea I've picked yp recently as I wacthed a video by Ward Cunningham

indywiki >  reinterpreting links 

• as intent bearing links along with 
• reinterpreting folder structures as intentional structures
  • where folder names play a role analogous to terms names in abstract syntax trees
  • and are combined with user defined operators 
  • forming analogues to ground atomic formulas
  • concrete intentionally explicit construct rules
  • that are amenable to interpretations and transformation for alternative interpretations and functions

experiment-web.search&web.snarf

background

• started using SingleFile
  • see? https://hypothes.is/users/gyuri?q=singlefile
  • Browser extension for saving web pages with images
  • and in a way that pages that rely heavily on JavaScript would render faithfully
  • That is in itself a break through
• Experimented with saving these SingleFiles in IPFS Desktop
  • but it would be nice to do likewise using Peergos
  • and based on that develop complex workflows
  • that enable 1 to do the job of web search and web snarf
  • in a way that are born integrateable and interplayeable with any other
  • capability, software as a virtual autonomous service in the long tail of the Internet
• .

 

 

 

integration.with-hypothes.is

problem

• hypothesis Browser extension is not available on Android 
•  

Fortunately Michael requested a page hosted at hyperpost.peergo.me

• to be available via.hypothes.is gateway
• /hyperpost/🌐/🎭/gyuri/index.html

outcome

• The outcome of all this is that
• it is possible to conduct 
• exploratory experiential experiments 
  • trials formulative thinking in the medium of exploratory essays 
    • (trying to say)
  • that orchestrate existing capabilities and sketch out future extensions and
  • design of future conversational,
    • intentionally explicit , 
    • work/information 
      • flows
  • relying on Peergos's extensive range of
• built in capabilities 
  • Rich Text/HTML Editing via CK Editor
  • Drive that gives you control yOur data, control yOur destiny
  • basic searches including full text
  • an alternative to Google Drive and Workspace
    • even without realtime collaboration it offers tremendous value
    • especially as it offers users to control their data, control their destiny
  • It is designed to be extensible, timkerable, midfiable with user provided
  • Open Source and even Open Sauce,
  • Open Constructs, such as peersuite.space
  •  that are easy to integrate, interoperate and even interplay
  • nicely with each other
• producing automagically web hosted HTML documents
  • which themselves are amenable to be annotated
  • even without the need for installing a Browser Extension that in fact is not possible
  • and cosmo-local autonomous infrastructure that is capable of supporting
  • much of the values that the IndyWeb is about
• but most importantly all that work can be carried out in a way 
  • that cn be shared via the web and even ANNOTATED/Commented on people who
  • are interested in its development
• One of the early goals of current development is to pave the way for
  • creating and sharing named collaborative spaces that themselves are
  • deeply intertwingled forming emergent complex associative complexes
  • that are themsleves in a deep sense self-organizing and self-revealing
  • integrating sharing ideas with the very means of conducting
  • symmathetic conversations about and related to it
• All this makes develoment of sotware in the long tail to be created
• as a Conversation about
• orchestrating interconnecting interplaying across emergent capabilities
• Make IT by doing/engaging with ideas and means and with each other

 

dedicated launch communities

By interweawing

• conversation about 
• desired capabilities
  • all associated research, formulative thinking, conversations
• trigerred by and facilitated thorugh practical instance first eploratory experiments
• creating neccessary documents
• doucumentin gthe work process
• taken togehter allow developers instigators to obtain feedback, contributing viewpoints and ideas
• early and often

Put in another word

• all development work enables the emergence of “Launch Communities”
• bringing together
  • People
  • ideas
  • Intents
  • for the co-creation and co-evolution of the means of achieving common shared goals
  • and capabilties
• resulting in an ever expanding cretive feedback loops

 

notes.on-do.how-bootstrapping

with all the technical pieces in place

• we are on a path to getting workflows and interplay 
• that supports wholistic, integral intentional 
• info-communication-capabilty flows
• tat allow us to factor out infrastructural concerns at ascending levels of scaling

while at the same time be ssured that if something works for an individual

even if most or all steps are done manually

are ipso facto amenable to be incorporated with minor controlled extensions at any future scale of working together, so that we an actually realize separation of

working out solitions to a particular domain

from the supporting infrastucture that is needed o deliver it atdesired scales

This is no idle imaginings and dreamings

we have most if not all the technologies at hand to do so.

Better still, we are following a design principles like

 

integration of concerns

that is to say figure out ways to intemingle concerns that in previous approaches driven effort to solve them as self-contained components that are to be composed and integrated into larger wholes and in fac tthe design of the applcaitons/capabilities/and affordances are shaped and rendered monolithic and unresusable in any other constellation of component choices for

• storage
• communicaiton
• scaling
• version control
• dev ops

In fact the approach can be charadteried by dithcing the very idea of dev ops

develop open universal infrastructures of cascading scale

on te assumption that all capabilties will be created and delivered

on the basis of a Open Universal Document Model

a uniersal intentional contextual resource naming scheme

 

that is independent of scale

 

or rather it is built with assumption of having available

 

global, interplanetary scale which relies on a global networked universal naming schme

very much a way of facilitating Universal Resource Names

that are open to be interpreted to actually deliver the named resource

 

bringing people, ideas and capabilties and autonomous emergent interest base social networks together onto the SamePage

 

The current model of using capabilities on the web is that all capabilities are in their own silos

that people flock to them do their own bit

in the process they loose all control of their own data,  loose control of their own destiny.

obtain digital artefacts that are enclosed in many sense of the work

more often than not they ale locked up by the very services they make use of to create them

Typically they an only shared resource and even comment and engage with content only with people who signed up and signed in to these services

Simultaneously drastically limiting reach and attainable social synthesis

 

Contrast this with a vision that at every point Flips everything there is

 

Start with the most fundamental:

The core value proposition of Peergos:

Control and own your own data, control your destiny.

see: https://hypothes.is/users/gyuri?q=lock+the+web+open

 

 

This implies some starting choices regarding  infrastructural choices we make

very much in line with "

hard to integrate, interoperate let alone interplay with

Here we take an approac that Fils this.

 

 

 

about

• This folder gives a short, permanent. human readable/writeable  name 
  • for the Indy Actor/Player called: gyuri
    • that is linked to gyuri-lajos
    • and is the owner of the Peergos account called hyperpost
  • It is  a public web accessible entry point to all information
    • that is made available on the Web
    • This is a temporary arrangement
      • eventually most of the content will be accessible only through the indyweb
      • won't be crawlable, indexable by search engines
      • and all access, even read access will have full audit/provenance trail
      • and even verifiable record of all information exchanges
      • associated conversations, hypothes.is annotations
      • and a full, attributed history of development of each resource
  • Originally I used the tilde character as a folder name to indicate that the
    • folder provides entry points to named user spaces
    • so the link bellow no longer works
  • https://hyperpost.peergos.me/~/gyuri
    • hyperpost.peergos.me/🎭/gyuri/index.html
    • assumption is that each Peergos account is created/curated and maintained
    • by designated group of individuals trusted to be the stewards and administrators
    • of a named community of purpose
    • or by real individual human beings
    • In either case the number of connections they are able to make
    • over time is limited
    • especially when considering time dimension
    •  
  • .
• .