this post was submitted on 16 Jun 2023
126 points (100.0% liked)
Technology
37747 readers
347 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I think people will eventually get used to the idea that the name of a community is not just the part before the "@".
I mean, even regular people have no difficulty understanding that e-mail addresses like bob@google.com and bob@microsoft.com are two different "identifiers" and, most likely, two completely different people. Given a bit of time, I think there will be a general understanding that "!foo@lemmy.ml" and "!foo@beehaw.org" are different names.
I think this is exactly what OP is trying to point out - they are two different communities, when on reddit there would only be one - therefore the fragmentation.
The person you were talking to started the conversation with a screenshot showing 5 subreddits for "Blue Protocol", apparently a MMORPG. Similar examples exist for almost any subject big enough.
The phenomenon exists for all systems where there is no central authority deciding names and categories, which is true for both reddit and lemmy. Individual users can decide to create a new group regardless of existing groups, for a variety of reasons. This naturally leads to some duplicates.
they were all different names, there could be only one BlueProtocol.
And as sunaurus said, they all have different names on Lemmy too, once you realize you need to count the entire identifier and not just the part before the @.
On reddit you'd have /r/tech and /r/technology, both serving the same thing but with clearly different names. On Lemmy you'll have /c/tech@instance1 and /c/tech@instance2 both serving the same thing but with clearly different names. Eventually one will win out and the other will wither away. Or they'll diverge enough to make subscribing to both worthwhile.
on reddit you have r/tech and r/technology, the analogue on lemmy would be /c/tech@instance1, /c/tech@instance2, ..., /c/technology@instance1, /c/technology@instance2, ... - the chance for fragmentation is much greater.
Agreed. This is exactly what I've been saying as well.
And like some other commenters have said: Lemmy is still very new and no standards and a lot of UX features still need to emerge. I am of the opinion that this fragmentation is a symptom of a UX problem and not inherent to anything specific to Lemmy.
Search needs to be improved to show communities from yet-to-be-discovered instances and provide a way for the user to view them by subscriber, popularity or newest, for example. But right now, it relies on the user to initiate a subscription to a community in another server for server discovery.
I could see a list of “popular instances” emerging at some point as a means for instance maintainers to prepopulate this in the future.m and Lemmy to support importing such a list to seed federation on new instances.
Thankfully it looks like this sort of thing is already on the radar.
We can just subscribe to both though. I think we can even cross post. At least I've seen some things that look like cross posts. Frankly, I don't see any difference.
I think what they mean is that taking your example with blue protocol, that same thing can happen both within instances and between instances. I do think it will eventually sort itself out but will take longer.