secure-scuttlebutt@18.0.0, scuttlebot@11.3.0

ssb now has decrypted-indexes
see also the PR. This does not mean that messages are stored decrypted, but that they are passed to indexes decrypted. To access a decrypted message, most sbot messages now support a private: true option, that is not allowed on methods exposed to peers.

This clears the way for private-groups, which I intend to start on once user-invites is ready.

This also means that things like likes, follows, and blocks, can now be optionally private! and that support for this will require minimal changes to UIs!

/cc @matt

Awesome! Hopefully next week I'll spend some time fixing up ssb-about, ssb-private and ssb-backlinks to take advantage of this! And maybe look at adding the option to do a few things in Patchwork privately (such as nicknames).

Patchwork privately (such as nicknames)

Reckon private should be the default unless someone manually elects to have open nickname tagging (i.e. public disclosure of their assigned tags)

Great!

I'm having a look at how the unboxing was done to learn some more about flume indexes and hopefully gain some more performance. Hopefully that will make it easier for you @matt so you can focus more on the UI side.

well done !

I'd like to have a go at upgrading scuttlebot in Patchbay + Ticktack. There was some horrid problem in muxrpc 7, which was pulled in by scuttlebot... any updates on that.
cc @matt

@mix

Everything seems fine now. I'm running the (almost) latest version of sbot with no pinned deps and no problems (just make sure you find the pinned deps in your package.json and remove them)

Created PRs for ssb-private and ssb-backlinks

@mix we downgraded muxrpc back to 6.4.0

I was gonna say - Patchworks mucrpc is at 6.4 in the package-lock.
Keen to see ebt running

I pushed a new version of ssb-backlinks and ssb-private to github, but can't publish them to npm as I don't have permission. Please note these depend on scuttlebot 11.3.

@arj

Hmm, if these depend on scuttlebot 11.3, shouldn't these be breaking (major) bumps?

I was thinking that as well, but then again the plugins are very loosly coupled to main sbot. The thing is that the changes aren't really a major change in the module per se as it should do exactly the same thing just simpler. But please feel free to bump the versions when they are pushed to npm.

@arj

It would break older versions of patchwork and patchbay if installed via git tags (if we weren't using package-lock) since these bundle their own sbot. But otherwise not a huge deal.

I would strongly recommend bumping minor at least (since most of these are 0.x.x, this will stop them from being pulled in).

Right, fixed. Thanks!

@arj

I pushed a new version of ssb-backlinks and ssb-private to github, but can't publish them to npm as I don't have permissio

Oh, you should probably be added to https://github.com/ssbc/ssbc-owners

Or is there a better solution now @Mikey? I seem to recall something about an npm org.

Or is there a better solution now @Mikey? I seem to recall something about an npm org.

@matt yes! ssbc npm org. if you have any packages, add them here.

@Mikey @arj

Cool, I added:

• ssb-backlinks
• ssb-about
• ssb-private
• patchcore

Thanks!