this post was submitted on 17 Jun 2023
229 points (100.0% liked)

Technology

37742 readers
496 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
 

In my opinion, there are two big things holding Lemmy back right now:

  1. Lemmy needs DIDs.

    No, not dissociative identity disorder, Decentralized Identities.

    The problem is that signing up on one instance locks you to that instance. If the instance goes down, so does all of your data, history, settings, etc. Sure, you can create multiple accounts, but then it's up to you to create secure, unique passwords for each and manage syncing between them. Nobody will do this for more than two instances.

    Without this, people will be less willing to sign up for instances that they perceive "might not make it", and flock for the biggest ones, thus removing the benefits of federation.

    This is especially bad for moderators. Currently, external communities that exist locally on defederated instances cannot be moderated by the home-instance accounts. This isn't a problem of moderation tooling, but it can be (mostly*) solved by having a single identity that can be used on any instance.

    *Banning the account could create the same issue.

  2. Communities need to federate too.

    Just as instances can share their posts in one page, communities should be able to federate with other, similar communities. This would help to solve the problem of fragmentation and better unify the instances.

Obviously there are plenty of bugs and QoL features that could dramatically improve the usage of Lemmy, but these two things are critical to unification across decentralized services.

What do you think?

EDIT: There's been a lot (much more than I expected) of good discussion here, so thank you all for providing your opinions.

It was pointed out that there are github issues #1 and #2 addressing these points already, so I wanted to put that in the main post.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 3 points 1 year ago (3 children)

For sure. But beehaw in a good example of aggressive moderating (which is totally their right) that can limit growth and why a decentralized approach is necessary. There can’t be a single massive place for x content. It’s rife for abuse. Allow it to be categorized and decentralized where beehaw can contribute but in their own way and users outside of beehaw can index and participate with them and even other instances that maybe beehaw defederated.

[–] [email protected] 5 points 1 year ago (1 children)

I don't think it's fair to call it "Aggressive Moderation". It's barely possible to moderate on Lemmy right now at all, and that's why they defederated. They simply cannot trust outside instances as much as their own, because they screen every user, and they can't keep up with moderation. Defederating is their only option until mod tools get better.

[–] [email protected] 4 points 1 year ago

I mean. It’s clearly subjective and I’m not judging whatsoever. It’s their prerogative and frankly I think there are some positives to it. And if it helps their space then that’s all that matters. I’m just a control freak and want to be in control of my account, backups, location etc.

But if you weren’t one that’s a troll on one of these others and were cut off it’s a tough pill too. I get there’s no easy answer.

When I looked at the mod log I was seeing some instances where, imho, it seemed aggressive policing of symantics. Individuals were t necessarily being offensive or trolling, though their opinions may not have been well formed or fully thought out or in line with others there and were bounced. And again that’s their call.

I’m not saying I would do better. In fact it’s why I’m not open and EVEN if I open my instance I’m not gonna have communities. I have no interest in policing fools that argue in bad faith or just want to get their jollies off angering others.

[–] [email protected] 2 points 1 year ago (1 children)

https://static.xtremeownage.com/blog/2023/join-the-fediverse/

Not sure if it helps or not, but, I made that post earlier to assist onboarding a bit.

[–] [email protected] 1 points 1 year ago (1 children)

Nice. Thanks. I spent a good amount of time on a few links jsut mass adding communities of interest. Will just remove ones that don’t work out. No way to really organize or group them by topic though.

[–] [email protected] 1 points 1 year ago (3 children)

There is a github issue to allow communities to be federated-

Ie, this community can be hosted on multiple instances, for example.

That would help some too.

[–] [email protected] 2 points 1 year ago* (last edited 1 year ago) (1 children)

On a side note. Do you mind if i post your blog post in the sidebar on my instance (i already did, but can pull it down if you want, no one is looking at my site most likely)

Right now my instance isnt open. But given a possible surge coming on 7/1 I am chewing on opening it up to be a "user-only" federated instance. As in, no real communities, just a speed instance to setup an account and join other communities.

Not sure if im going to even do it, just thinking about it right now.

[–] [email protected] 2 points 1 year ago (1 children)

Feel free- Just do me a favor, if you come across some useful information we can share to others, please let me know and I will update it.

Right now my instance isnt open. But given a possible surge coming on 7/1 I am chewing on opening it up to be a “user-only” federated instance. As in, no real communities, just a speed instance to setup an account and join other communities.

After reading some of the concerns from other various communities today, I ended up locking down my registrations to requiring both approval, and a valid email. I don't expect to get a ton of users, but, I wanted to reduce the chance of "Troll users" joining, and then giving my instance a bad name.... Or users posting content, which is not appropriate/illegal.

“user-only” federated instance. As in, no real communities, just a speed instance to setup an account and join other communities.

That is essentially what my instance is. The small handful of communities here, are either for my instance itself for me to share news, OR, communities related to some of my public projects.

[–] [email protected] 2 points 1 year ago* (last edited 1 year ago) (1 children)

Feel free- Just do me a favor, if you come across some useful information we can share to others, please let me know and I will update it.

Absolutely will.

I'm having the same thoughts on registration. Require email at least to just...reduce throwaways and trolls. Mines application only because "closing" it is confusing as it just spins. And I may leave it to application only.

Same with NSFW content. I don't know of a good way to defederate some of those instances and track that. So i unchecked the box and tossed a disclaimer in. I really just don't want drama from my hosting provider. Just want a place people can login and go to some of the other instances that are more focused on curating content and communities. I just dont have time for that myself.

[–] [email protected] 2 points 1 year ago (1 children)

drama from my hosting provider

That is an easy fix! Just host behind cloudflare. Your ISP/Datacenter/etc can't see anything as the data is encrypted between lemmy <---> cloudflare.

I don't care if anyone posts NSFW content, AS LONG AS... its in a NSFW community and/or tagged NSFW. (AND, obviously not questionable/illegal)

[–] [email protected] 2 points 1 year ago

Yeah. Strongly considering cloudflare for sure.

[–] [email protected] 1 points 1 year ago

Absolutely. Multiple ways to address some of these issues. Hopeful for the future.

[–] [email protected] 1 points 1 year ago

Would different parts of the community be hosted on different instances, thereby spreading out the burden? Or would the entire community be mirrored to each of the hosting instances, thereby providing backup security?

I've actually been wondering about that. For example, what if an instance with a popular community went down or defederated from everyone? Would all the content of that community be lost to everyone else? I'm guessing that under those circumstances one or more new communities would be started to replace the "lost" community, although things could get complicated if there were more than one trying to replace the original - or if the original community refederated after the replacement communities developed.

[–] [email protected] 2 points 1 year ago (1 children)

Beehaw did nothing that isn't common in the fediverse. I know people that are new to all this may be shocked by Beehaw's decision, but defederating from intances that promote intolerant discourses or allow trolling is the way to keep an instance alive. People will end up suspecting and defederating from an instance that interacts with intances that allow or promote that type of content or behaviour.

[–] [email protected] 2 points 1 year ago* (last edited 1 year ago) (1 children)

Again. Its not a criticism of beehaw. Just kind of an example of you are who you associate with sometimes IRL, but in the fediverse. Its unfortunate and I understand why they are building what they are. I support that.

Its also a reason why having very large concentrated communities can be bad and why federation or de-centralization is important. But with that, it does appear we need some better tools for cross-instance moderation and cross-instance community grouping so that you can say...create a "technology multi-community" that includes [email protected] and [email protected] and [email protected] or whatever etc. etc.

That would allow for decentralization but still give people the ability to browse them as one community and if you so happen to be registered on something like lemmy.world, then you cant see the beehaw.org content but can see the rest etc.

[–] [email protected] 1 points 1 year ago

That's why it's important to look at what instance you're planning to join, and not just join the "original" or "most popular".

The idea of multi-intance communities isn't bad, while respecting (de)federation, and should be implemented if ever possible.

But the biggest issue here is that most people are joining the same 3 instances. The less instances there are, the less possibility of federation there is.