Avatar
MK Fain
932614571afcbad4d17a191ee281e39eebbb41b93fac8fd87829622aeb112f4d
Team Soapbox. Freedom advocate. Plant and animal lover. Reader and writer. #Ditto #Bookstr #MKStack #Vegan #Shakespeare #divine
Replying to Avatar Garbage nsec

"AtProto allows users to theoretically move between different services. However, user keys are controlled by the server admin, and users' ability to move servers is dependent on the server's willingness to cooperate."

Some nuance here. If you start by having your PDS hosted by bsky and then pull it away to self-host, from the point you've taken charge none of your rotation keys will remain controlled by Bluesky. (You control the server, server controls the keys, thus you control the keys, no permission needed from anyone.) What's also relevant for your self-hosted PDS is that everything is content-addressed.

The question of pulling away from bsky (as host) in adversarial sense versus an allowed sense is a different question, but point is once you're out you're out, you've got the keys

You can also start off self-hosted and thus half self-hosted control from day one, though pretty much everyone starts off in bsky.

"Bluesky uses DIDs (Decentralized Identifiers) for accounts, but accounts are still managed centrally."

They use DID:WEB and DID:PLC. You can setup your own DID:WEB, which you control, and that DID:WEB plus a download of your repo can potentially be enough for a future adversarial migration. What's centrally managed is the directory (i.e. they are their own ICANN), but that's another tangent.

"Self-hosting is highly restricted: servers are limited to 100 users, and Bluesky can refuse to federate with them."

The idea there is you self host your own PDS (one by one). There is no real federation per say, no real sense of being in charge of others. If there existed two relays then one relay could refuse to index your individually self-hosted PDS (or hosted via some cloud service) while the other relay could agree. (A second independently-run ATProto relay is going up later this year in Europe, or so they say.) Or a relay could index your PDS but a given appview(client) could refuse it. For example bsky-dot-app could refuse while pinksky-dot-app could accept. Importantly though any AppView can pull directly from any PDS (or group of) without a relay in the middle, so at the moment bsky has zero power to stop anyone from from creating an app view that pulls directly from self hosted PDSs.

"Although AtProto is a decentralized protocol, in practice, Bluesky is highly centralized because the vast majority of users rely on bsky.social, which can block entire self-hosted servers."

This is defo the key point, i.e. the flagship demo has eaten the future. That said the term "Bluesky" can mean different things to different people:

- Bluesky the AppView (as in Primal or Damus)

- Bluesky PBLLC the company and team (which is driving ATproto)

- ATproto the protocol itself driven by Bluesky

- The current (and only) ATproto relay (graph service)

The issue is that Bluesky the AppView has all the client usage and the current relay under the PBLLC is doing all the indexing. And that won't change anytime soon, even though there are some neat ATProto versions of Olas, and Comingle and a lot of other clients on Nostr.

Sure but keep in mind this is a 101 level post for non-technical users moving from something like Twitter, who are likely just discovering decentralization. :)

Alex has been sitting on a way more detailed breakdown of Bluesky & AtProto that gets in the weeds like this that I really want him to finish when he's not so busy 😁

That doesn't matter. Nostr accounts have no loyalty to their client of origin. Your keys are your keys no matter what client you use, a Ditto username is just like any other NIP05 :)

What do you mean? In that screenshot you are on Ditto.pub, no?

Oh then its a reminder to request your username I think? πŸ˜…

Replying to DEAD ACCOUNT

Hey nostr:nprofile1qy2hwumn8ghj7erfw36x7tnsw43z7un9d3shjqpqjvnpg4c6ljadf5t6ry0w9q0rnm4mksde87kglkrc993z46c39axsus667r when I'm logged into #Ditto, how come I see a notification on my username under ditto.pub where I can add a username?

I'm currently on damus.io

Maybe you have a Ditto username granted you haven't added?

As someone who worked on the Fediverse for many years before being convinced to switch my focus to #Nostr, I'm often asked what the difference is between various decentralized protocols.

I made this post as a 101 answer to this common question so I don't have to keep typing the same thing :)

https://soapbox.pub/blog/comparing-protocols/

Flip it over and drill holes πŸ˜…

Don't worry, I love hearing feedback from people who are using/running Ditto! Sometimes it's hard for us to know what to do next when there is a near infinite amount to do, so getting community feedback actually helps us choose what issues to prioritize.

I'm surprised to hear about the issues with admin edits, like customizing the theme. I haven't seen that issue, so I'm glad you let me know! I wonder if your json config file has got messed up?

I agree with you about onboarding - this is the big question for Nostr. How much do we try to "obscure" the technical details for the ease of joining, vs how much do we empower users to learn and take their freedom into their own hands. It's a fine line.

What sign up flow would you rather see, do you think?

Henhouse is my own Ditto server, but we're hosted on the Ditto home servers. 😁

Replying to Avatar TKay

nostr:npub1jvnpg4c6ljadf5t6ry0w9q0rnm4mksde87kglkrc993z46c39axsgq89sc

How is ditto working for you? what is your hardware setup?

I get a lot of errors when making soapbox edits or accepting new members. Not sure what im doing wrong.

can you speak to your experience with this?

I love it! But of course I'm biased, lol.

Henhouse uses the same servers as Ditto.pub. I know it's a lot more advanced than the setup we recommend for a standard self hoster, but that's because we want to be able to spin Dittos up at whim.

I do get a lot of those pop up errors sometimes, but almost always they seem to be referencing nothing of importance bc my stuff is still working? I know we need to figure out why though.

And I have the benefit of in-house tech support (literally) which is lovely ☺️

I know that Ditto probably isn't really, truly ready for mainstream self-hosting yet. There's so much to fix, improve, add... The list is never ending, but it's a high priority for us to improve this experience and make it more self-hosted friendly!

How's it going for you?

It's okay, I was just curious about the zapping mostly. Thanks for experimenting with me!