share.link: https://cryptpad.fr/pad/#/2/pad/edit/sYl7w4OBYJ6pm3Qn8jOJrFeL/

~ stub

• dumping ground for screenshots

FeatherWiki @ Peergos

~ stub

• I wanted to document the work I've done over a year ago with FeatherWiki
  • but as I write it brings in a lot of adjacent topics
  • before I could continue with this
  • I'll move some of the discussions into adjacent IndyWiki Pages
  • and create linked CryptPad Page where I can share some of it in form
  • that would be amenable to be shared and commented upon relying on CryptPad's won
  • collaborative capabilities

? why.here

• The time has come to review and 
• synthesize years of work carried out 
• across three Peergos Named Spaces:
  • hyperpost
  • indy0 and
  • indy
  • 
    
• They constitute chronological records of expanding understanding and intention
• all represent more than 1 year of work
• and as the understanding of what's ie emerging
• occasioned the creation of one's with better names

• • 
    
• hyperpost
• ~ was
  • the first account I created 
  • with the intent of delivering
  • on the value proposition as it was set out a decade ago
    • HyperPost @  https://hyperpost.co/
    • 
      
  • A decade ago 
    • together with Christophr P. Goodman,
    • we created TrailMarks Ltd
    • as the commercial vehicle
    • for delivering HyperPost.
  • HyperPost, as the name suggest,
    
    • was was envisaged to inter connect Posts of interest and 
    • Weave them into emergent self-saliencing adjacent
      • threaded 
      • named, 
      • deeply intertwingled, 
      • meaningfully, high resolution addresable,
      • mutually connected,
      • emergent
      • networks of threaded
        • conversations
        • collaboratively co-created co-evolving
        • mutually discoverable and engageable
        • shared digital pen-sieves
          • 
            
        • from which adjacent thougt of the participants could be explored and engaged with
      • It was envisaged to be an born multiplayer
      • networked mutual leaning tool
        • where each node in the network would act as a portal
        • for the entire scaffolding with which participants
        • would record/externalize, formulate their thinking,
        • act as a Networked Thinking Tools, just like the
        • Networked Thinking Tools of roam years later,
        • but by construction it was envisaged as co-thinking tool,
        • as a companion to Google_, 
        • the original Interest Based Social Networkd,
        • augmenting it to enable parts of 1's own
        • thinking to be shared between individuals.
        • A sweet spot where providing web access to once work
        • doe not longer imply benefitting the network providers
        • but enable ones to link their own contributions to be made available within adjacent emergent networks of trust privately if desired.
        • But most importantly HyperPost was intendd to grant users full autonomy of their own contributons not only those that they shared inside their own mutual trust networks
        • but everything they contributed to the Google.
        • This would have provided users of HyperPost with
        • strong gurantees tht they would not loose all when the service is discontinued
      • .​​​​​
        •   within the trust 
        •  and personal learning trails  and share for mutual benefit.
        • hat establish deep associative trails
          • contiguous with the entire available di
      • a social MEMEX,
      • a social network for trailblazers
    • HyperPost thus would have successfully combine
      •  global reach and discover-ability
      • with interpersonal trust based networked threaded deep conversations that would have been continuous without being synchronous
      • and contiguous with the participants entire writing to think and mutual learning spaces.
      •  
        • through operating as a companion app/service,
        • anchored in and mirroring existing Google+ Posts that 1 made
        • and providing access and expansion ports to the entire scaffolding, captured in 1's additcontributions to Google+ as a social network
        • through open inerplayN 
        • but acting as a portal for deeper, private conversations that are related to what is eing shared on the social network itself
        • Giving rise to the emergence of interpersonal inter interest based communities, that would be autonomous and survive even if Google+ was sunset-ed.
        • and allow for parts of the conversations to be private between emergent trust networks
        • t​​​​​​​
    • 
      
    • Posts on Google+
    • into an aoutinomous in autonomous 
    • using TrailMarks InLine MarkIn Notation and the lessons learned
      • over nearly  a decade of WiniNizeR development
  • A workable prototype was getting ready by December 2017 when Google announced its shutdown justifying the decision with reference to security issues scheduled by August the following year
  • By January 2018 the shutdown was initiated and it was all gone by February
• I always intended to rely on Google Infrastructure just to get off the ground
  • and scaling reach
  • while pivoting to create a brand new infrastructure using IPFS protocol
• In 2018 I found OrbitDb which seemed to be able to offer everything that was just above the threshold that was required, in order to deliver a sweetspot
• It worked perfectly for a time in a personal setting, where any work conducted on any of my machine got synchronised automagically, as OrbitDb was built as a combination of CRDT and IPFS
  
  • to develop a 
• recreated using indyWeb Scaling Infrastructures
  • at some point
• ...
• indy0
  • At some point I pivoted to name my adjacent next maximal ambition as Indyweb
  • Registered the domain name indy0.net
    • as a reflection of the fact that it was intended to be a
      • born multiplayer scaling infrastructure
    • with IndyWiki as its Maker App
    • and it was envisaged as a threefold
    • or should I say Trefoil of mutual arising infrastructures for
      • Permanent Web Scale Storage powered by IPFS
      • Multiplayer omni-sync, omni optional Human Actor Model,, as in real time and asynchronous eventual consistency, local first personal fist interpersonal browser native networks of trust of networks
        • where each individul was to be empowered to operate their own(ed) autonomous evergreen Hub tow waeve their own People's networks around named colaboratories dedicated to some named pursuance
    • At that time IPFS still had lots of issues, so i spent a lot of time
      • technology scouting to find adjacent efforts with the intent of finding existing capabilities tha could assist bootstrapping the vision
    • I found Peergos and CryptPad
      • both delivering in different ways capabilities that could be incorporated into the development of te origin networks for the IndyWeb
    • indy0 @ 
      • Peergos
        • CK Editor was a very cpable Rich Text Editor
          • but due to technoloical gotchas
          • it way too frequently resulted in unable to save messages
            • The real cause of this was found years later in the unreliability of bitswap
          • It took a major refactoring to swith to relying on Wesockets
          • It was a major improvment
          • but did not completely elliminated te proble
        • Explored TiddlyWiki. 
          • The peergos custom app clled ...
            • was rally nice, the I and the workflos and affordance were quite capabapble, but holding everything in a single file was a real limitation, so I did not use it
        • FeatherWiki was much nice. First of all
          • because it allowed multiple "orkspaces" so promising better scaling
          • it could be used as local file so save operations were reliable
          • 1 really had to be a programmer to be able to create the organization of the information in nested folders
        • This section is dedicated documentin existing work using Feather wiki
        • and make it available for te curent development Sprint and beyond
      • CryptPad
        • just like Peergos CryptPad is very muc value alligned
          • both deliver capabilities
          • that can contribute to te mutual arising co-creationg
            • of IndyWeb as an autonomous BrowserNative constellation capable of delivering te goals of
            • https://indieweb.org/
              
        • CryptPad is te only one I know that delivers in a usable clear way
          • on the vision of no sign up, or sign in and provides by construction guarantees of User Autonomy
        • Ayear ago it still had limitations of not really able to incorporate images into documents and did not generate clean self contained HTML that was required
        • It does Now. That was a show stopper
        • It still does not support inter document wiki like links
          • but that is exactly what IndyWikiDelivers and in fact brings that capability to any page on the web
          • along with the ability to link threaded converstions enayhwere over the web itself
        • IndyWiki becomes the Maker App for the Autninomous IneterPersonal Web
          • that is designed to InterPlayN nicely with the existing centralized Web
          • It can complete IT, not designed to compete with it but to
          • complete IT resulting in a mutual arising new space
          • 
            
        • 
          
• indy
  • Eventually I registered and paid for a tird Peergos Account called Indy
    • as a way to develop all the applications
      • envisaging it as a future entry point to have a single central named space
      • for all the IndyWeb apps created in the future
  • These three names correspond to the three main Three partatie components
  • HyperPost as User Facing SeetSpot
  • that connects simultanously
    • People
    • Affordances
    • Information
  • Indy0 responsible for the People's Networks
  • indy for the evergreen everpresent Affordances (Apps) if you like
• 
  
• 
  

Track work in Bookmarks