this post was submitted on 05 Jul 2023
76 points (98.7% liked)

Asklemmy

43803 readers
763 users here now

A loosely moderated place to ask open-ended questions

Search asklemmy πŸ”

If your post meets the following criteria, it's welcome here!

  1. Open-ended question
  2. Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
  3. Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
  4. Not ad nauseam inducing: please make sure it is a question that would be new to most members
  5. An actual topic of discussion

Looking for support?

Looking for a community?

~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~

founded 5 years ago
MODERATORS
 

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?

you are viewing a single comment's thread
view the rest of the comments
[–] ProdigalFrog@slrpnk.net 3 points 1 year ago (1 children)

Can you elaborate on this? How does it not care about those things?

[–] interdimensionalmeme@lemmy.ml 1 points 1 year ago (1 children)

If you're not in the main instance, your going to be handicapped in your ability to stay in the loop. First because now everything goes through federation, which was a design afterthought for Lemmy, and that means stuff outside the instance always takes second place to what is inside the instance. Then you have issues like federation which are extra layers of censorship for everything outside your instance. I've of the biggest problem is accessing outside communities. First you have to actually go to other instances and find them. They won't show up until at least one person subscribes. And this has to be fine in every instance for every other instance and every communities in each of their instances before they would even become visible. Of course, this is such a high bar that by the time you do all this, you'll realize 99.99% of users will not go through this trouble. They will just go to the biggest community on the biggest instance.

Last problem, if you go to your instance/c/acommunity , you'll see only that instance's "acommunity" There is no way to refer to "acommunity" for the entire fediverse. There is no fediverse community. Only parallel, same named but unrelated communities that would require extra steps to view all at once if it were even possible.

There is a proposal , an old proposal, to create multireddit like feature for Lemmy. But first, the devs so not want to test down this barrier, si they won't do it. But even if they did, it would not work. Since you'd have to take extra action to aglomerate selected communities with a multireddit, you would be one of very few people to do so because agglomeration would still not be the default. And that means most communities would remain empty deserts anyway.

[–] ProdigalFrog@slrpnk.net 1 points 1 year ago (1 children)

First because now everything goes through federation, which was a design afterthought for Lemmy, and that means stuff outside the instance always takes second place to what is inside the instance.

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.

First you have to actually go to other instances and find them. They won’t show up until at least one person subscribes.

That isn't ideal, I will admit. Without Lemmyverse.net it would be difficult to find everything that interested me.

But first, the devs so not want to test down this barrier, si they won’t do it.

If Lemmy won't, then I suspect that would leave the door open for Kbin to implement.

[–] interdimensionalmeme@lemmy.ml 1 points 1 year ago (1 children)

It's not going to be a problem to find the communities. Since people on arandominstance.com won't be posting on arandominstance.com/c/interestingtopic

They will know if they did, no one would every see it, except for the dozen other people on arandominstance.com

Instead, they'll Google for the biggest /c/interestingtopic , find on what instance it is and go post there

We don't get to the part of having difficulty finding them because they don't get created in the first place

[–] ProdigalFrog@slrpnk.net 1 points 1 year ago (1 children)

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?

[–] interdimensionalmeme@lemmy.ml 1 points 1 year ago (1 children)

I mean, 600 users that's a lot and yet you look at

https://slrpnk.net/c/knitting

And there isn't one post.

This is what I mean. Your knitting users have to go off instance to https://lemmy.world/c/knitting

In a working system based on federation, it wouldn't matter in what instance you make a /c/knitting post, it would be seen on all instance's /c/knitting

There is no indication this big will every get fixed, and many inducations this is against Lemmy developpement philosophy. I have seen no indication of kbin doing differently either.

Either you post on the big /c/knitting , or nobody (less than 1% of 1% of all Lemmy users) will see your post before it goes stale (72 hrs)

[–] ProdigalFrog@slrpnk.net 1 points 1 year ago (1 children)

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.

[–] interdimensionalmeme@lemmy.ml 1 points 1 year ago (1 children)

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.

[–] ProdigalFrog@slrpnk.net 1 points 1 year ago

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.