/indy/🌐/0/via/hypothes.is/about/

🔗links - 👀view, 🌐indy.peergos.me/0/via/hypothes.is/about/

 

---

reflection on ongoing process

 

Flip the old Web where people flock to sites to access informaion and engage in interaction

on the IndyWeb, all the information, means of creation/curation of owned information and the very means of working with the information and communication come to the user's browsers

work local first, even offline first, *except when engaged in live interplay with online servies

but the result of all such past interaction is available offline and permanently

 

All infomration is tored on IPFS

as files have permanent cryptographically verifiable identities

it is possible to include the same file in multiple plaes in one file system without duplicating use of underlying storage

the folder names can this be reied on as meaningful permanent designation and

a way to capture the intented use of files thus enclosed

 

folders can also contain web apps and services, which are also stored with permanence, and verifiability, that enhances security

 

1 can think of the eveolving folder structure as a vehicle of meaningful organization contextualization

 

---

About the IndyWeb.inbrowser.web.service endpoint to interplay with hypothes.is

• Hypothesis itself provides a via.hyp.is endpoint that provides access to
• hypothesis annotation without users needing to install the hypothesis browser extension
• For the IndyWeb this concept of via is generalized and is used to 
• name all domains for that provides servies that has
  •  indyweb 
  • inbrowser
  • overweb
  • companion services
    • that play nicesly with each other
  • In this instance
    • the first service inbrowser service is used to replicate the capabilities
    • of the via.hypothes.is endpoint that provides access to 
    • annotated pages even in browser without the hypothes.is browser needed to be involved
  • Hypothesis operates a proxy server, but it only works for sites that approved for such an access
  • the virst indy.web.inbrowser.service via hypothes.is is built to 
  • enable web pages archived by any individual indyweb user to be shared
    • with hypothesis/embed.js preloaded
    • so annotations made on athe shared page can be seen
    • and new one's added as long as the user signs up with the hypothes.is service
  •  
    • overweb access to hypothes.is web site/service
    • indy interplay 
      • with existing centralzed services accessible via hypothesi.is 

 

nexus

• /indy/🌐/Web/via/hypothes.is/about/
  • Sharing entry points to
    • self-Documenting 
    • IndyWeb 
    • Inbrowser 
      • interplay service entrypoint 
    • supporting indy interplay via hypothes.is web service