As much as I like the ‘decentralized’ stuff, the technical part of federation should NEVER be exposed to the end user if you want the platform to be mainstream. I still don’t understand why a lot of federated projects think it’s a good idea to expose that to the end user.
Probably not. Currently it seems on track that you’re always first on their main instance. If you’re technically inclined you could then start hosting a federated part yourself (or joining one), but this does not change that the actual entry experience is exactly the same as on Twitter, hence why transition is so insanely smooth and painless.
As much as I like the ‘decentralized’ stuff, the technical part of federation should NEVER be exposed to the end user if you want the platform to be mainstream. I still don’t understand why a lot of federated projects think it’s a good idea to expose that to the end user.
Whenever Lemmy or Masto gets a flood of new users, a portion of them never make it past the instance selection and totally bail.
The user experience was designed by people who literally respond to user feedback by telling users to commit new code to the project.
It’s clearly designed by engineers who assume other users will be just like them.
This of the core of the problem. Github energy.
Fine for a hobby. Not good enough for a public-facing product.
The project was started as an architectural thought experiment, not with the goals and limitations of the end user.
If bluesky ever becomes actually federated, won’t it have the same problem?
Probably not. Currently it seems on track that you’re always first on their main instance. If you’re technically inclined you could then start hosting a federated part yourself (or joining one), but this does not change that the actual entry experience is exactly the same as on Twitter, hence why transition is so insanely smooth and painless.
The way sign up currently is, probably not. It would still default to bsky.social and your average person isn’t going to think about it.
Dude, do you even email?