As the Fediverse grows more and more, rules and regulations become more important. For example, is Lemmy GDPR complient? If not, are admins aware of the possible consequence? What does this mean for the growth of Lemmy?
As the Fediverse grows more and more, rules and regulations become more important. For example, is Lemmy GDPR complient? If not, are admins aware of the possible consequence? What does this mean for the growth of Lemmy?
I mean I wouldn’t mind a multi-reddit sorta feature like you describe, but I actually like that there are silo’d instances, I don’t always want to see EVERY post about a subject on the fediverse if my own community has higher quality content of that subject. Also, not every instance needs to be a generalized place with every topic, I like that many of them cater to certain themes.
I would like the option to see everything of a certain subject at once, don’t get me wrong, but I see the small silo’d instances as a feature, not necessarily a bug.
The problem is that it’s easy to filter only local content. But the current system is biased for local content first. So paradoxically this means local content will wither and die because no one will see it.
Content should be global first and local second. That way, you can post wherever you like and it will get global exposure.
This way users will not be incentivized to only post in the biggest community on the biggest instance, while leaving everywhere else a desert.
The current way it’s built will recreate a centralized Reddit like with few fragmented communities
The problem with multireddit, why they were not able to fulfill to promise of bringing multiple communities together was that only a minuscule subset of users used them.
I guess as I’ve been using Lemmy more, I see that this is actually a fairly large issue. When I post to, say, a Videos community, I crosspost the link to every other Videos community I can find on the lemmyverse. But that’s clunky, and if anyone is subscribed to all of those communities for redundancy, it shows up in their feed multiple times, which is likely a little annoying.
It does seem like the community recognizes this is a problem, and there are open issues for it on the github page. I have to assume that at some point the devs will address this issue, it seems odd that they would purposefully choose to ignore it.