this post was submitted on 25 Jan 2024
12 points (100.0% liked)

Announcements

23277 readers
14 users here now

Official announcements from the Lemmy project. Subscribe to this community or add it to your RSS reader in order to be notified about new releases and important updates.

You can also find major news on join-lemmy.org

founded 5 years ago
MODERATORS
 

This will take place ~24 hours from now. Feel free to post and upvote questions beforehand in this post, as it will turn into the AMA tomorrow.

TimeZone Converter Link

This is a chance for any users, admins, or developers to ask anything they'd like to myself, @[email protected] , SleeplessOne , or @[email protected] about Lemmy, its future, and wider issues about the social media landscape today.

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

What is currently in the works to help admins locate spammers and problematic users on their instance?

Right now I believe it relies heavily on users reporting and admins looking through a users history however I think that is really inefficient.

Are there any better visualization tools that could be made to aid admins?

[–] [email protected] 1 points 9 months ago (1 children)

Registration applications, and user reports are the best way to handle trolls. The first stops 90% of them, the second means we can ban and remove all their spam at the click of a button.

I don't see how you could prematurely know about spammers or trolls until someone reports them. We don't plan on adding any text-analyzing AI or anything like that into lemmy's codebase.

[–] [email protected] 1 points 9 months ago* (last edited 9 months ago) (1 children)

I don’t see how you could prematurely know about spammers or trolls until someone reports them.

I don't think you can. My suggestion was more focused on how admins make decisions after a report. Right now they have to do a manual scan of the person's comment history and that is the part I find inefficient. If it was possible to just show extra high level information on the user it might make it easier for the admin to make a decision.

We don’t plan on adding any text-analyzing AI or anything like that into lemmy’s codebase.

Yeah using AI to try and analyze comments would be overkill and probably prone to manipulation anyways.

Edit: I'm sorta talking more specifically towards banning a user or seeing if what a user is doing is a repeated pattern.

[–] [email protected] 1 points 9 months ago

I don't think there's a way you could avoid going into their history. I do that as an admin to verify that the account in question is indeed repeatedly breaking rules. I'm open to suggestions tho.

[–] [email protected] 1 points 9 months ago (1 children)

How would you suggest to make it more efficient?

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

Well I am not 100% sure on what the best method would be.

I think the addition of letting moderators see who is voting on what posts is a nice addition since they would tend to be closer to where the content is.

More generally I was thinking about creating a dashboard that gave the admins statistics about that user.

Similar to how we as users can see how many comments and posts any user makes, it might be useful to allow admins to see statistics about which communities the user interacts with or some rudimentary similarity score with other users?

These are some ideas I thought of on the fly and have not thought about the implications but the gist is something that allows the admins to get a better understanding of what is going on from like a bird eye's view.

Edit: and where -> on what posts

[–] [email protected] 1 points 9 months ago

This seems like a big change that also requires a lot of brainstorming to flesh out. It sounds like it would best be made as an RFC for now.

[–] [email protected] 1 points 9 months ago (1 children)

The main implication is that someone would have to implement it, and we dont have enough developers for that.

[–] [email protected] 1 points 9 months ago

Yeah that's fair. It was just more of a possible what if.

Hopefully you're able to get more people that can help develop the features that are in the backlog.

Anyways thx for answering. I was half expecting it to be skipped.