Uh, for something touting e2e encryption and security it would be better if the site did not serve over plain http by default
Scuttlebot: Peer-to-peer database, identity provider, and messaging system
21–30 of 123 posts
Re: Scuttlebot: Peer-to-peer database, identity provider, and messaging system
#22npm install
sigh...
Re: Scuttlebot: Peer-to-peer database, identity provider, and messaging system
#23Earlier quoted context omitted.
I've been on SSB for some 3 years (with some breaks when I had enough of npm). Once you're onboarded it works like a charm: exchange of data between peers works swiftly and efficiently, to the extend that you can even use it for realtime chat the way IRC works. The community is colourful and friendly, and the signal to noise ratio is high. I've learned a lot about fermentation and growing mushrooms and living off-gri…
Thank you! The lack of multi-device support isn't too much cumbersome? Also, do you not fear, due to the gossip protocol, that your private messages may be stored forever by peers and one day, your private key leaks, and all your conversations are publicly exposed?
It would be sweet if we had multi-device support, but it doesn't bother me too much: All my IDs are mutually following each other, and I have my “hops” set to 3, so I see virtually the same timeline on each device. What can be frustrating, though, is that notifications and private messages to a given ID are only visible from the device with that ID.
I am not overly concerned about leaks of my private key, although the risk is certainly there.
One think many people have to get used to, though, is that the log is append-only: once you've published a message and is no way to delete or undo the message — is it there for “all eternity”. The positive side is that you're more conscious about what you post and why, because there is no way of taking it back.
Re: Scuttlebot: Peer-to-peer database, identity provider, and messaging system
#24[deleted]
Re: Scuttlebot: Peer-to-peer database, identity provider, and messaging system
#25Huge fan of Scuttlebutt and think it could (should) be the future of the social internet. I recently quit my job to write about and work on decentralized tech full time with scuttlebutt being my primary focus. I've written about why I think it's so important here: https://adecentralizedworld.com/2020/03/what-is-scuttlebutt/
> Decentralized social networks have been tried before, the two most well known are Diaspora and Mastadon. With these services there [is still moderation]... Scuttlebutt is how I believe the social web should function in the future.
Even the Hackernews community which lean towards decentralization more so than the general public would still argue there is value in moderation.
Re: Scuttlebot: Peer-to-peer database, identity provider, and messaging system
#26npm install sigh...
Yeah, this is where I lost interest too.
Re: Scuttlebot: Peer-to-peer database, identity provider, and messaging system
#27Earlier quoted context omitted.
It's been a while, but I used to be an active SSB user. I hosted SSB pubs and used to post on patchwork semi-regularly. I thought it worked pretty well as a social network. I discovered new and interesting ideas from folks that I don't see much on mainstream social media. I haven't followed the space much recently, and I'm curious about how it has evolved over the last year or so. My favorite memories on SSB: Someone…
Thank you! The lack of multi-device support wasn't too much cumbersome?
The lack of multi-device support was a constraint that gave me a different perspective of interactions on the web.
My ssb keypair was on a work laptop, so when I changed jobs and had to give my laptop back, I lost my keypair. Now, I could have exported the keypair and continued to use my "account" on my new laptop. The network would have synced on my new device, and I'd get all my posts and pictures back. But decided to embrace the constraint instead.
When I rejoin the network, I'll have a new keypair, and no post history. I think this can have an interesting effect on how we view our attachment to data.
Re: Scuttlebot: Peer-to-peer database, identity provider, and messaging system
#28I've used patchwork before, but can someone comment on the other applications of the scuttlebut network and where this scuttlebot fits in?
Scuttlebot is the core server and plugins for Scuttlebutt. The Github repo is now called ssb-server. Patchwork uses it for replication and adds a gui and new plugins on top of it.
Re: Scuttlebot: Peer-to-peer database, identity provider, and messaging system
#29Warning: A bit of a ramble about my experience trying to use SSB for my "application". I really enjoy SSB, conceptually. In reality I've had a fair amount of trouble getting started writing an application in it. Notably, I have difficulty knowing what patterns are good or bad in SSB. As far as I can tell SSB utilizes effectively a commit ledger for user data. This is fine, but some of the specifics of my application…
I've been tinkering with SSB recently as well and I'm also finding it difficult to figure out how to interface with the wider SSB network in the 'correct' way. The communication protocol is well documented and easy to implement if you have libsodium available. Building applications on it should be straight forward considering it's just an eventually consistent event store.
I am having a few issues though. The 'api' that patchwork and other parts of the network use on top of the communication protocol seems to not be documented at all outside of the 'post' message. I'm not sure if it's not documented or if I just haven't discovered it yet. For example, I'm having to dive in to the code to see how a 'vote' message is formatted. I'm not sure how all of the various clients are staying compatible. None of the message formats seem to versioned in anyway either.
I'm also not sure what are the 'correct' ways to introduce my own message types. Should I use a vendor prefix in the type or something? Is it bad form to pollute the network with your own message types that other clients can't understand?
I've just started diving in to all this so maybe I just haven't gotten deep enough yet. I wrote a little toy SSB implementation last weekend to learn the protocol. I've really enjoyed playing around with it so far but I'm still not sure if it's the right fit for the applications I want to build yet.
Re: Scuttlebot: Peer-to-peer database, identity provider, and messaging system
#30Huge fan of Scuttlebutt and think it could (should) be the future of the social internet. I recently quit my job to write about and work on decentralized tech full time with scuttlebutt being my primary focus. I've written about why I think it's so important here: https://adecentralizedworld.com/2020/03/what-is-scuttlebutt/
> Decentralized social networks have been tried before, the two most well known are Diaspora and Mastadon. With these services there [is still moderation]... Scuttlebutt is how I believe the social web should function in the future. Even the Hackernews community which lean towards decentralization more so than the general public would still argue there is value in moderation.
For sure, any network without any moderation is going to quickly fall into chaos. I'm working on a post on decentralized personalized moderation at the moment which should be out in the next day or two :)