You are reading content from Scuttlebutt
@cel %Lr8mzqWjDBf4AqY2ZNMShJpRJzeoy7QUhyXvDU+9gM4=.sha256

@dominic re: https://github.com/ssbc/ssb-ws/pull/8
I'd like to use ssb-ws's /msg route in ssb-npm. WebBoot and the /thread route I have not needed to use.

@Dominic %i0rs0EjiB+PmjsD25p2k1mRML95T9pbG/8QoWKR5ItE=.sha256

did you mean you were using it, or that you want to use it? I didn't see any code using it in ssb-npm

@cel %1IVUqJe1CjgbD1L+E51qlCKu2h3uWymhGwo14b4Yn64=.sha256

@dominic
that I want to use it.

@Dominic %5R2H8UlbsiCbVsVRFu+wRydyysc0xlWqRJpGv1A25WU=.sha256

you can still install that via sbot.ws.use(handler) from ssb-npm-registry... can you tell me more about how you'd use it?

@cel %9cxT3BnTcRJNo/xJiqsOMQ2wKMd+qZIzu4JOL23zmMI=.sha256

@dominic

i want to be able to get ssb messages without needing to make a shs/muxrpc connection. this would be for bootstrapping ssb-npm installations of scuttlebot and ssb apps. i am concerned with cases where the user wants to install scuttlebot or ssb apps via ssb-npm, but doesn't have scuttlebot installed yet, or only has patchwork installed. i want to make a bootstrap installation script that would take a message id and an address of a http server that serves ssb blobs and messages (i.e. ssb-ws or ssb-viewer on a pub) and serve a local npm registry server for installing ssb-npm packages reachable from that message id.

@Dominic %fEGU2bsgUuSUkrjySU3z43TY+EBAd3zyAMa3DyCDf3U=.sha256

hmm, right... okay, I'll remove /thread but not /msg. requesting messages is different because you have to know the exact hash, it isn't revealing anything about the database (such as private indexes) other than having the message or not.

Join Scuttlebutt now