@Christian Bundy thank you for the feedback.

the main problem is that we want the same install.sh file to point to different blobs over time?

Not necessarily. The URL contents could be immutable. Or could be non-editable but deletable (like npm package releases). The example in %9c2tLY9... includes a version number in the URL. But we might want mutability anyway, since it makes the system more useful and in some models would not add any complexity.

Yes, it could be similar to a wiki. But I think of a wiki as having pages that multiple people can edit. A feed per domain means each page (URL) can be edited by only one author. Also, I expect wiki to be published in a markup format and rendered on the server before serving as HTML. Shell scripts would not need that.

The simplest way would to make one subdomain per public key, like how Dat does it.

Noted. This wouldn't work for the http://installers.scuttlebot.io/… idea if just one feed has access to publish to it. Unless that feed can grant access to others. That gets to what I am wondering about how to make work and what is needed for it.

I'd love to have a big distributed wiki where my content is distributed to a bunch of different SSB-related domains.

What would the different domains be? The same system hosted on different pubs? Or different applications/variations/structures?

maybe this would be a better task for git-ssb?

That is an option.