this post was submitted on 17 Jun 2023
153 points (82.6% liked)
Lemmy.World Announcements
29042 readers
1 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'm one of those USENET greybeards and I think this would probably be a mistake. If you let a name be uniquely claimed by an instance, how do you decide which instance gets to be "in charge" of that?
Better IMO would be to update the various interfaces to be much more explicit about including the instance name along with the user/community name. So that it's always clear that a user or community is at a particular instance.
We do still need better migration tools for moving users and communities around, though.
Itβs not about allowing a single instance to own the name. The name would belong to the federation in a global namespace.
A possible scenario is to define multiple namespaces. Each namespace can be local to a single instance, or shared between many. Within each namespace, a single community name is unique.
In this model, each instance would have a namespace that it owns, and the ability to participate in many others.
The trick is in how we name the namespaces and communities. We could do this the USENET way and do something like ., so beehaw.gaming vs. global.gaming. There are other models that could work too.
I'm not sure how that would be different from what we've already got.
IMO the main feature kbin/Lemmy are missing is an equivalent to "multireddits." That would allow multiple communities to be seamlessly aggregated for a user, they'd see all the content blended together as if they were one. I remember seeing a Codeberg issue over on the kbin repo discussing how to implement that, and I'm sure Lemmy's devs are working on it too, so that feature will probably come along fairly soon. Then it shouldn't matter much if the same subject has had multiple instances set up communities.