/indy/🌐/0/

 

@.link

• self:  https://indy.peergos.me/0
  • ^^ link to this document it self
    • containing links and information to a specific document in 1's indranet workspace
    • The links here allow direct retrieval of resources
    • publicly , in the old ways of the internet, 
    • with the intent to be available for public unrestricted/unrecoded access
    • thus making these resource available without attribution
    • or connecting directly with the readers
    • This is the norm as we are still in the bootstraping phase
    • and rely heavily on being able to annotate all these shared documents
    • usinga private annotation tool that is a first class IndyWeb app 
      • is in active developmeent
    • considr this as a repository of meta information about the resource being shared
      • a place to document how things work currently
      •  
• canonical.web: https://indy.peergos.me/0
  • ^^ Web Hosting by Peergos Account holder named: indy
    • a page that contains links to IndyWeb content created/curated in Peergos and IPFS Infrastructure
    • This document provides those linkls
    •  
• view: /indy/0/ 
  • ^^ view page referenced here on Peergos
• @diary.link: 
  • ^^ pages are created and worked on in daily active document folders
    • these are then shared via Peergos, IPFS,  IPNS or via Peersuite.Space
      • either as Rich Text HTML created by WYSYWIG editors like
        • Indy0/NotePad Peergos Custom App
        • or equivalent hosted via IPNS
  • ipfs: inbrowser.link/?urn=💻.thinkpad.🧊.♖.indy.📓.2026.02.19/♖.indy.0
    • ^^ using inbrowser.link to run an IPFS node on demand in the browser 
      • sharing resources by Content ID
      • add to that link as a location.search string introduced by ‘?’ 
        • a parameter named urn
          • that stands for Universal Resource Name
          • which gives a  symbolic name for the machine used
          • by the creator of the resource
          • and a folder path
          • so the resource is identified by the machine and the folder
        • This name is not used for retrieval, the IPFS CID ensures retrievability
          • but i used to name the resource in terms that are idicative of
          • the nature of the information being retrieved
        • This name also reminds its creator which machine was used in the creation of the reource
        • and whrere it will be in their loal file system IPFS or OS or both
        • This information can be used to nodify existing version republish
        • using 1's own IPFS Desktop App
  • ipns:https://k51qzi5uqu5div1auuxm59ygav4p7gdg9z4e9iggtu6m43rmc3xw75mczx2b7x.ipns.dweb.link/♖/indy/0/index.htm?ippn=0🧊ipfs-2b7x
    • ^^
• 💻.thinkpad.🧊.♖.indy.📓.2026.02.19/♖.indy.0

purpose

This is an explorimental document intended to provid a web accessible canonical reference to indyweb content

Its primary purpose is to contain meta/conpexual information about pages shared on the indyweb

a brief summary card image etc

Use the Peergos hosted link to this page as a canonical url for the putpose that all variants of this page both chronolarchic references, specific verions as hosted via IPFS and

permanent names to mutable content in one

 

development notes

This document is available via Peergos site Hosting under the Peergos acount indy