A loosely moderated place to ask open-ended questions
Search asklemmy π
If your post meets the following criteria, it's welcome here!
Looking for support?
Looking for a community?
~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~
Maybe that's a good idea. Going to /C/technology shows a view of all /c/technology sub's that the instance is aware of :)
Posting to /C/technology would just post to your instances /c/technology
Or maybe differentiate between communities and topics? /t/technology aggregates all the communities around technology? That would be cool IMO
In my opinion, it makes most sense that they get treated like the same community.
If you subscribe to "c/memes", you will see the posts from any communities on any instances that's name is "memes".
And if any individual one is causing issue, you or your instance can ban the problem instances' version.
Here's one scenario where that idea doesn't work. I was subscribed to /r/pax on Reddit. Occasionally, people would wander through and post about their vapes or ecigs or whatever, not noticing that every post in the subreddit was about the Penny Arcade Expo and not about the ecig/vape brand. (Sorry. I don't know the difference between a vape and an e-cigarette, if there even is one. π )
All that to set up this question: what happens when a community is created on one Lemmy instance called "pax" referring to the Penny Arcade Expo while, on another instance, the first mover on "pax" is an e-cig/vape enthusiast? I subscribe for updates on the Penny Arcade Expo, and now, instead of an occasional misguided individual coming through posting about their nicotine enthusiasm, half or more of my posts on "pax" are about that?
Yeah that's fair.
I think the best situation is that as a general guideline short abbreviations like that are avoided, and in the case of unavoidable name collisions one or both communities would have to further specify the name to avoid conflict.
So the pros are easier user accessibility, a fix of duplicate communities, and the cons is name collisions and potential abuse from communities on different instances.
This is a great idea but I see problems with it. Someone has to define the topics but this can be done by name matching. The bigger problem is the decentralized nature of Lemmy. Every server has to scan every other server for the communities to create a topic. Now letβs say we have 10 servers and each of them will have to fetch from the other 9 servers the communities list. This would already be 90 requests sent global. Now scale this up to 1000 and a single server will have to send 999 requests and respond to 999.
Edit: Currently we have over 1426 servers