this post was submitted on 15 Jun 2023
249 points (97.0% liked)
Lemmy.World Announcements
29057 readers
6 users here now
This Community is intended for posts about the Lemmy.world server by the admins.
Follow us for server news ๐
Outages ๐ฅ
https://status.lemmy.world/
For support with issues at Lemmy.world, go to the Lemmy.world Support community.
Support e-mail
Any support requests are best sent to info@lemmy.world e-mail.
Report contact
- DM https://lemmy.world/u/lwreport
- Email report@lemmy.world (PGP Supported)
Donations ๐
If you would like to make a donation to support the cost of running this platform, please do so at the following donation URLs.
If you can, please use / switch to Ko-Fi, it has the lowest fees for us
Join the team
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I know we can have multiple accounts (and I am sure apps will help the experience), but I almost signed up for Beehaw as it was big and chose here
I am glad I didn't sign up and will probably unsubscribe to anything I was subbed to there. Interesting to see that instance is rather heavy with the unfed hammer
I was thinking about the multiple accounts thing. Maybe the concept of an "instance" needs to be separate from the concept of an account? Like, it doesn't matter what service you choose for your email account; you can email anyone from Gmail, and anyone can send email to you. The only real difference is that your email address end in "@gmail.com" instead of "@comcast.net".
On Lemmy, though, the place you make your account matters a whole lot. It determines what content you're allowed to see, and who you're allowed to interact with. If the instance you're on gets federated, you need to migrate to a different account on a different instance. That never happens with email!
A lot of users have been managing this by creating their own instance, with the sole purpose of hosting their account and nothing else. Maybe that's what we need: a set of "instances" that only host accounts, and a set of "instances" that only host communities. You could then use that account to subscribe to communities from any instance. That way, Beehaw could block content from instances they don't like, without cutting off all of the users who happened to choose the wrong place to sign up.
Actually, under that system, there wouldn't be a need for instances to federate content with each other at all. Users could just subscribe to communities with their account, and then the users would be the ones in charge of what they see, instead of their insurance choosing for them.
I think it'll take a little while to settle down, but I'd expect the communities to congregate on more permissive, well federated servers. In the short term I'm doing similar to you what you proposed, e.g. having accounts on various servers, but I expect the need for this to go away as things settle down. I already focus on a couple of instances more than others.
I do think that less permissive instances will still thrive though, although maybe not so much for general content. That may change as more granular controls and better tools emerge so it's less of an 'all or nothing' approach to federating.