Scuttlebot peer-to-peer log store(scuttlebot.io)
scuttlebot.io
Scuttlebot peer-to-peer log store
https://scuttlebot.io/
12 comments
I think the more relevant link is https://www.scuttlebutt.nz/ which is more about the use of it and thinking behind it than just dumping you in the core docs... I find it good to know if i should care before i start dissecting the guts of an API.
What's the difference between scuttlebutt and scuttlebot?
From the repo…
> There are already several applications built on scuttlebot, one of the best ways to learn about secure-scuttlebutt is to poke around in these applications.
I'm very confused.
From the repo…
> There are already several applications built on scuttlebot, one of the best ways to learn about secure-scuttlebutt is to poke around in these applications.
I'm very confused.
Scuttlebutt is the protocol. Scuttlebot is a nodejs library that has implemented the protocol.
You can use the scuttlebot library to build peer to peer apps.
I looked into it a while back, it seems like a cool technology. Happy to try and answer any questions.
You can use the scuttlebot library to build peer to peer apps.
I looked into it a while back, it seems like a cool technology. Happy to try and answer any questions.
hey @atestu, i agree it's confusing.
this page on scuttlebutt.nz should help: https://www.scuttlebutt.nz/modules.html#secure-scuttlebutt-v...
feel free to ask if you have more questions. :3
this page on scuttlebutt.nz should help: https://www.scuttlebutt.nz/modules.html#secure-scuttlebutt-v...
feel free to ask if you have more questions. :3
I would say that is somewhat outdated as well.
Take a look at https://ssbc.github.io it's much more detailed as to how it all works.
Take a look at https://ssbc.github.io it's much more detailed as to how it all works.
hey @brad0, as far as i know, ssbc.github.io is the most out-of-date, at the time of being written by @pfraze it was superseded by scuttlebot.io which has all the same detail and more.
scuttlebutt.nz is a more recent effort by me to write documentation not only about the technical details of _how_ but also more stories and quotes to capture the spirit of _why_.
but having documentation scattered around is confusing, our intention is to consolidate these many sources into scuttlebutt.nz: https://www.scuttlebutt.nz/contributing.html#contributing-do....
scuttlebutt.nz is a more recent effort by me to write documentation not only about the technical details of _how_ but also more stories and quotes to capture the spirit of _why_.
but having documentation scattered around is confusing, our intention is to consolidate these many sources into scuttlebutt.nz: https://www.scuttlebutt.nz/contributing.html#contributing-do....
Oh sorry! I didn't realise.
Scuttlebutt is definitely in need of a consolidation of information. Keep up the good work!
Scuttlebutt is definitely in need of a consolidation of information. Keep up the good work!
[deleted]
I ended up here: https://ipfs.io/blog/25-pubsub/ after reading up on scuttlebutt (again). They've implemented a pubsub mechanism on IPFS, which would (neatly) handle the data distribution challenge of SSB, and largely be compatible with SSB's ethos. They don't have a way to make it so only certain people can publish, but that's a technically surmountable challenge (either filter out invalidly signed publications now, or wait for them to have their solution in place).
Pairing these two approaches, SSB could make a neat application on top of the IPFS pubsub infrastructure (with some work)
Pairing these two approaches, SSB could make a neat application on top of the IPFS pubsub infrastructure (with some work)
[deleted]
nice. Kappa Architecture mentioned ! :) -> https://github.com/ssbc/scuttlebot
I long for the day where we no longer need a server at all.