opt-in publicWebHosting

if you haven't heard, there's been a change to ssb-viewer so publicWebHosting became opt-in rather than opt-out.

before the change, by default your content is rendered by ssb-viewer, unless you set publicWebHosting to false.

after the change, by default your content is not rendered by ssb-viewer, unless you set publicWebHosting to true.

in practice, this means most links to viewer.scuttlebot.io only show a series of "User has not chosen to be hosted publicly".

for example, the latest post by the @butt_summarizer: %RZJJlUnBimjjlgUJ2tSa2xVA24n4nVcFJRONZk4uUmk=.sha256

or @dominic's free listening manifesto: %V2rZOt+nuTrS/89OquyPSgBBRjkJAf81Stq/sg2Fmtk=.sha256.

i bring this up because it affects our scuttlebutt.nz documentation, which links to a bunch of posts using the viewer, to show the project as a living being. i also tried to share some interesting content to potential butts on the outside and none of them had public content. i'm happy if you don't want your content to be public, but i have a feeling not many people were aware of the change to ssb-viewer

how to change your publicWebHosting

to change you public web hosting, you have to write an about message with a publicWebHosting field.

using sbot (to install sbot, first install node with nvm, then run npm install -g scuttlebot)

sbot publish --type about --about "@your.public.id.here" --publicWebHosting

oops, my "how to change your publicWebHosting" example should be named "how to opt-in to public web hosting"

so then, how to opt-out of public web hosting:

sbot publish --type about --about "@your.public.id.here" --no-publicWebHosting

I have opted in!

yo también

Resurrecting this @dinoƧ𝔸Ⓤᖇ. I'm attempting to get an #ssb-viewer showing just a specific channel. Its working, at feed.cobox.cloud. However the two messages I've posted aren't visible (due to this public hosting issue). I've published a message to my feed, which I thought should do the job, but appears not to have. Am I missing something?

{
  "key": "%S9V3hDa/SQTZQBfetmeEXbOQN4RJWcQTYJw/TS7nojE=.sha256",
  "value": {
    "previous": "%+2mP/CTnD4voYmoXdJQaPo6FkboDbIP5VRkVNYjpfHg=.sha256",
    "sequence": 3396,
    "author": "@MpDd66GPXgN1+eMNrZInHkWq1THMurWwLdMx8BZ1ncw=.ed25519",
    "timestamp": 1562075765672,
    "hash": "sha256",
    "content": {
      "type": "about",
      "about": "@MpDd66GPXgN1+eMNrZInHkWq1THMurWwLdMx8BZ1ncw=.ed25519",
      "publicWebHosting": true
    },
    "signature": "tZ5KJpPUEb0ul+ZfeOVM+KRICZlljft5ex0LqsAhdR/gCRp1/S0+L/yP/TQPhBCFur2z6MVw7r5bk2TqalAACA==.sig.ed25519"
  },
  "timestamp": 1562075765672.001
}

while I'm a programmer and I could do this, this is quite convoluted, and this feature is quite important to be turned on to help popularize SSB. A non technical user (which is the majority of users) would just not bother. This should be an easily accessible checkbox in the clients, and it's quite important to be easy to reach and understand.