You are reading content from Scuttlebutt
User has not chosen to be hosted publicly
@cryPhone📱 %5xVJ244s6+ggY4qK24iS5LRUd+xoW2aCwn67wbnNGsE=.sha256

I agree. Backlog control is a thing that keeps a lot of people from SSB. Some times you want to exchange thoughts and ideas without a unforgable record.

Even if you can control who gets in a network fairly well (network key + mutual auth with friend graph dist) in case of failure the attacker gets everything instantly.. but I’m not sure how to effectively protect against that if the medium should also work as an historic archive.

My personal opinion here is that ssb is not the tool for everything but maybe that’s a copout as well...

@cryPhone📱 %yQff4sdGguAVqoWC1dBGliPm/aT6tWsGCdd2JpIKiqU=.sha256

Where the job is mostly decent twitter, git and media for me. I think ssb is a strong stepping stone to iterate further.

Privacy wise, I also think that there aren’t many platforms that offer reader privacy (no one ones what threads or profiles I spent hours on) and no recipient info on PMs.

@agentofuser %i8xWC1NYchEFUctQ4DzLiszs+hxp0ltxo9/4CCwTo8Y=.sha256

That resonates a lot with me. The least we can do is protect network information by not using bare TCP/IP.

I've recently written about this as well:

I think metadata should be front and center in the design of peer-to-peer systems, because as people start connecting directly to one another, they end up leaking a lot more to a lot more untrusted actors than when previously "laundering" their connection graph through something like a (trusted) Signal server. And I think #onion-services provide unmatched security to build on top of.

%6rXPJT2...

The good news is that SSB already supports p2p-over-tor with #onion-services thanks to @arj. We just need to move towards this becoming the default or at least the path of least resistance.

User has not chosen to be hosted publicly
@agentofuser %pJ9LQ8KmF0CHrwKPvI2T3mS6+bhGw9IcUMWXPD2kt1k=.sha256

I didn't know #retroshare also used #onion-services. I was glad to see they borrowed code from #ricochet to implement that :) https://retroshareteam.wordpress.com/2018/03/13/release-notes-for-v0-6-4/

It's very nice that they made a separate "TorOnly" binary. This way you don't have to fiddle with configurations and don't need to be afraid to have messed up something and leak data.

Downloading now! I'll DM you my "RetroShare certificate" in case you want to connect :) If anyone else wants to try it out just DM me.

Join Scuttlebutt now