/indy/🌐/Web/via/hypothes.is/about
🔗links - 👀view, 🌐/indy/🌐/Web/via/hypothes.is/about
self-Documenting IndyWeb Inbrowser entry points are shared publicly here
nexus
public access point
https://indy.peergos.me/Web/via.hypothes.is
indyweb (edited Just now) 45 secs ago
on "InfiniteZero Network"
(artizen.fund)
work-in.progress-👀view
2026-04-18
dynamically loading embed.js
approach
on the peergos side
- in indy 🌐 0 via hypothes.is
- in the daily folder folder create
- a via.hypothes.is/index.html file for experimentation
- on peergos side
- create in the right folder main.js file that would be loaded from
- indy.peergos.me and the index.html file
- save that in current day under via.ypothes.is
- edit it with
telegram conversation w
[18/04/2026 07:11] Gyuri Lajos: Thank your for the heads up. I nice page shared as an instance first exemplar for weaving symmathetic permanent conversations on the margins of the personally archived web
[18/04/2026 07:12] Gyuri Lajos: see my response on the annotation margins https://hyp.is/4z7DjjrgEfGTpb8y4D3pTw/artizen.fund/index/p/infinitezero-network?season=6&scroll=no
Resource shared on telegram is archived personally on IPFS
that lead to the idea of providing a web function as part of the IndyWeb Autonomous InBrowser, micro Software As A Service constellation
for injecting/embedding hypothesis.js dynamically on any personally archived page
This would 1 gurantee visiility of annotations on resources shared via IPFS
also provide an instance first exemplar for supporting conversations on the annotated permanent personally archived web, andprovide the context by which shared resources can be linked to adjacent conplexes and indeed initiate threaded conversation
💻/asus/🧊/me/📓/2026/04/18
<< telegram-Artizen.fund@Michael Lennon
❓here
trigger
- I just realized as I was
story so far
- Personal Web Archiving via IPFS and annotating those archived pages so that a permanent Universal Resource name is assigned along with the permanent link to the saved resource
- The basic assumption is that these resouces will be retrievable vai requests to the creator of the resource if they are not available on the IPFS network
- In any case all retrieval of resources will be recorded
- that is to say the sharer of the resource has a a verifiable record of the sharing to specific indy.net participants
- requestors of such resources are assigned a unique locally unique pseudo id
- which is linked ot the identity of the resource owner
- this is ensured by the resource shared assigning a visually distinct utf8 icon
- plus the current month and day
as long as personally archived resources are shared vi IPFS and link to these resources are shared on hypothesis annotation pages
- later on other sites and social networks like Telegram, Are.na memex etc
It is possible to write a function that would take the following paramaeters
?
- CID of the resource
- pseudo id of the resource sharer
- pseudo id for the requester by which the resource owner can identify the requester