/hyperpost/~/indyweb/now/2025-12/=/IPFS/

---

created-2025-12-08 Monday

@props

• view.by
  • hyperpost
  • indy0
• sandbox.by: 
  • hyperpost 
    • indy0pad
  • indy0
    • indy0pad

---

 

update - 2025-12-08

note within a daily update use chronological order

---

setup on asus

I am using indy indy0 Peergos account

• 
• to edit files in folder  in hyperpost peergos account
• but shared for writing with another Peergos account
• Later on hyperpost (or any Peergos account) could create folders to be named for participant in an interpersonal indyweb space and create a secret writable link to pass on to new participants in the emergent network

This is the way it looks

• on my Asus Laptop
• 
• the associated brave profile there is
  • 
  • contrast that with the one below for ThinkPad
•  

---

setup on asus for IPFS

steps

• create a folder on IPFS @ asus
  • in here
  • 
  • new folder with path: 
    • now/2025-12/=/IPFS/
    • 
• download this document with the name
  • matching on the left vertical bar
  •  
  • the last two elements of the folder path
    • ipfs.dweb.link =-IPFS.html
  • .
• upload it to IPFS
• provide both ipfs and ipns links for it
• then setup editors for both
•  

 

 

 

 

 

 

 

how.did.i.get.here

• yesterday started using Indy0Pad@IPNS
  • giving a much improved editing experience
• Wish to use it to
  • create networked records of what I know and find most salient about IPFS
• Created a topic under /hyperpost/~/indyweb user
  • the Peergos counterpart of indyweb @ hypothesis
  • at  /hyperpost/~/indyweb/now/2025-12/=/IPFS/
  • the Peergos Folder, the enclosing folder for this document
• Arranged for sharing the /hyperpost/~indyweb folder
  • to be writable by my other Peergos account Indy0
  • 
  •  
  • 
  • 
• This is necessary as I wish to annotate these key resources now 
  • using my hyperpost account called indyweb
• Since this is my first attempt at using Indy0Pad to 
  • create/gather/curate information for a named Topic 
  • in its own named folder
  • by a user whose identity is anchored in the trusted service hypothes.is
    • but 1 that does not have a Peergos Account
    • whose work is actually accessible with write permission by two distinct Peergos account one of which shares a folder with right permission with another named one
    • This is an essential move to weave trust networks
    •  
•  
• https://bciqddcwkbfiklle6w6igsophhuyhwfv6ek52yy67pdxxkzdgzuohn4i.peergos.net/index.html?path=/hyperpost/~/indyweb/now/2025-12/=/IPFS/index.html&theme=&username=hyperpost&isPathWritable=true

---