Learned yesterday about . Absolutely loved it at first (I still find it very interesting). But found many problems in its design that need to be fixed before taking it seriously. My main problem is that if you have two devices you have two identities with different feeds and activities, that's because of how it works (every thing is stored locally on a folder on your device)
And for people using it, what problems in the federation model made you decide to go full distribution ?

· · Web · 3 · 3 · 5

The fact that I cannot share my identity across devices is what made me stop using #scuttlebutt. Other than that problem it is interesting.

@saadnpq scuttlebutt’s best point is its public key trust anchors. If you know someone’s public key, it doesn’t matter who’s in between, or what server they’re on. Mastodon fails at that b/c we mere consumers can’t be expected to comprehend or install anything, so they tie us to a server like [email protected] That server dies, or bans me, it’s an opportunity for swindlers to sneak in between, when all I can say is “just trust me this is totally my account now.”

@cy can't argue with that 👍, great point

@saadnpq Sorry for the toot flood. Doing this sort of thing right is kind of a life goal for me. If I could only figure out how to distribute and combine estimates…

@cy Have you heard of Tim Berners-Lee's SoLID? What do you think?

SoLID looks like their “WebID” is just a URL to a centralized server, so exactly the same as the Fediverse and Mastodon: a federated trust anchor. With the servers deciding whether or not you get to encrypt your data. And more of that awful “app” paradigm. Color me unenthusiastic as fuck.

but… federation technically isn’t the problem. Federated trust anchors are the problem. With public key trust anchors, even if we have federated servers, we can switch them easily, securely and transparently. Servers hate that because they can only be passive participants, not active moderators, rulers, or rock stars. But if you can get people with servers to help with the network, it’s perfectly safe to federate as long as you have public key identities.

…and the other reasons scuttlebutt does suck is first off (for the most part) it depends on electron, which is so hard to compile I hesitate to call it open source. Second off block chains are singly linked lists, with no random access. Binary search? Ha! Incremental is all you’re gonna get! They should use hash trees, not block chains. And thirdly, the tying of a public key to a computer. The argument is if have a message for a public key, which computer do I send it to? Uh oh!

The answer is all of them, of course. But Scuttlebutt just picks one at random then forgets about it. That would also work, if there was code to redistribute posts you receive to all your other computers, but… scuttlebutt doesn’t do that either.

Sign in to participate in the conversation

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!