Choose your SSB-Viewer URL

I just decided I was bored with editing the default viewer url (viewer.scuttlebot.io, not my side of the globe I guess, and frequently overloaded?) whenever I want to share some external link. Turns out patchwork reads the ~/.ssb/config file to set that url! ❤️
So I just added this line to my config:

"gateway": "https://ssb.muchmuch.coffee",

and now it generates the "right" urls! :)

@daan

Oh that's really cool! Do you know if the message ID gets URL-encoded? If so, I think Oasis might be compatible with this too. It'd just be example.com/thread/<messageKey>

@Christian Bundy your message is
https://ssb.muchmuch.coffee/%25a9kXcow0uyV2K8ZvgxMEpXqhWUK8bi0mMffNpAM7i1M%3D.sha256

so I guess that should work...

Yep, confirmed! 💓 This worked for me:

"gateway": "https://oasis-demo.fraction.io/thread",

🔥 🔥 🔥 🔥 🔥

Good to know.

But how do I decide whether my messages should be visible on public SSB viewers?

Using patchwork, I don't have any ~/.ssb/config file.

• Should I write that one line in it?

#ssb and #ipfs are really close. Except no encryption is activated by default in ipfs. But using ipfs-senc with ssb json messages is close to the same. ssb have Pub, ipfs have textile.io cafe. ssb-viewer is a application "gateway" service (anyone tryed to add and run ssb-viewer code in ipfs? Any Web2.0 app should work... )

Implementing ssb protocol into ipfs would brings the best from one to the other. If both community comes closer... https://discuss.ipfs.io/t/ipfs-scuttlebutt-protocol-similarities-and-complementarity/7228

@Fred ~/.ssb/config is actually a json file. So if you just want that one line, make it this:

{
    "gateway": "https://oasis-demo.fraction.io/thread"  // note the absence of a comma here!
}

I must have misundestood my publications rights?
https://viewer.scuttlebot.io/%252g4FtRpm5GFTT%2Bu2Ppw3M0Ywl40A06j27jVAv91iEVg%3D.sha256

I thought I publish that message in Public...