152
Lemmy and GDPR - What is the current state?
(lemmy.world)
A loosely moderated place to ask open-ended questions
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~
Posts in the Lemmy instances contain information relating to an identifiable natural person (by their user handle), as they contain the person’s ideas and opinions. Therefore the Lemmy instances are handling personal data and must comply with the GDPR.
That is a terrible option, cuts off a huge amount of potential users, and basically impossible to do fediverse wide. In fact, The European Union actually has official Fediverse accounts (on Mastodon, custom instance), and if the EU itself is willing to use a platform, that means it's probably not gonna be taken down by the EU.
Can you elaborate on this? How does it not care about those things?
At least for me, that hasn't seemed to be a problem. I found everything I wanted to subscribe to from my smaller server via Lemmyverse.net, and now when I look at my subscriptions page, I see all the newest posts from all those different communities. Unless you mean that it prioritizes local content on the 'All' page instead of subscriptions.
That isn't ideal, I will admit. Without Lemmyverse.net it would be difficult to find everything that interested me.
If Lemmy won't, then I suspect that would leave the door open for Kbin to implement.
Speaking for myself, my home instance of slrpnk.net is still quite small with only around 600-ish members, but seems active enough to be engaging and certainly worth posting and commenting in. It's not terribly different from posting in a small niche sub on reddit.
If there really was only a dozen members in an instance, I could see where there likely wouldn't be much activity unless it was a group of friends, but I don't see how it wouldn't still function as an effective portal to the other bigger servers, if account creation is ever closed on those.
Are you sure these growing pains will never be addressed? I don't really see why the Lemmy devs would be inclined to not eventually fix these issues. Do you feel the kbin devs would be more receptive to these ideas?
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.
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.
lemmy.world should really shut off signups to allow other instances to grow
This is a really bad idea as it would discourage new users to even sign up. lemmy.world could offer you the instance list when signing up but stopping altogether is just too much
This is a natural phenomenon called the Pareto principle. Roughly 80% of the users will sign up for the top 20% of instances. It happens everywhere in nature and it's unavoidable. But I don't think it will be a problem, federation is designed to work like this. You're not forced to stay on lemmy.world, you can move whenever you want.
Lemmy is developed using EU funds and many of the biggest instances are in the EU
Ah, yes. I believe this was step 4 of setting up your self-hosted instance.