@cel

Thanks for the explanation! Reading between the lines, am I correct to assume that the main problem is that we want the same install.sh file to point to different blobs over time?

This problem space feels like it has a big overlap with the #ssb-wiki problem, maybe there's one solution that would work for both? For example:

{
  "type": "wiki",
  "path": "install.sh",
  "link": "&qNy5xZ4bhu61z4k+XenbtDnt1IJp0b/gLJ/vdzd5vxM=.sha256"
}

If you had a button to give my feed a subdomain, maybe that blob would be served at either:

• https://christianbundy.wiki.scuttlebot.io/install.sh, or
• https://<my-feed-id>.wiki.scuttlebot.io/install.sh

How does the network decide what this (sub)domain serves? (Can this be generalized to other domain names?)

The simplest way would to make one subdomain per public key, like how Dat does it. I'd love to have a big distributed wiki where my content is distributed to a bunch of different SSB-related domains.