385
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 09 Jun 2023
385 points (100.0% liked)
Lemmy
12609 readers
5 users here now
Everything about Lemmy; bugs, gripes, praises, and advocacy.
For discussion about the lemmy.ml instance, go to !meta@lemmy.ml.
founded 4 years ago
MODERATORS
User accounts can be independent of anyone else's instance. You just have to host your own.
But it's always going to be much more convenient to register your account on someone else's instance, than to set up your own. Even if instance setup was made to be as effortless as possible, and single-user instances were made to be as lightweight as possible, say you download and run a single binary onto your computer that runs a lemmy instance and everything is automatic from there, most people still wouldn't want to do that.
The idea that you should be able to log in to your account from any instance is...less practical than you might think.
The technical reasons why are hard to boil down into an easy explanation. But the very short version is that everything comes with pros and cons. Doing it this way makes it a little less convenient for users, and a little harder to make a good UX for. Doing it another way could make it more convenient, at the cost of making it very easy for a bad actor to do things like post fake content under another user's name, or could add inconvenience somewhere else, like making it so that users have to manage a private key instead of or in addition to their username and password.
I do think there's room for improvement, but I think the overall idea of logging in and interacting with content specifically via the instance you're registered with is ultimately very unlikely to change.
It would also be cool to be able to not have communities be locked to where they're created or at least make them mobile.
I’d like to see a live replication kind of thing. So if you’re on !games@lemmy.ml it can merge with !games@behaw.meh and they super federate and advertise that this group exists, replicated, on four or five lemmy servers and the client tracks that every X hours and knows what the failovers are.
Solves some of the fragmentation issues and the backup/archive issues at the same time. Might even help with load balancing a bit if we have some kind of routing algo on the endpoints.