Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature that makes it possible to shadow ban "users" #3202

Closed
3 of 4 tasks
ctsrc opened this issue Jun 19, 2023 · 11 comments
Closed
3 of 4 tasks

Feature that makes it possible to shadow ban "users" #3202

ctsrc opened this issue Jun 19, 2023 · 11 comments
Labels
enhancement New feature or request

Comments

@ctsrc
Copy link

ctsrc commented Jun 19, 2023

Requirements

  • Is this a feature request? For questions or discussions use https://lemmy.ml/c/lemmy_support
  • Did you check to see if this issue already exists?
  • Is this only a feature request? Do not put multiple feature requests in one issue.
  • Is this a UI / front end issue? Use the lemmy-ui repo.

Is your proposal related to a problem?

I just got hit by a wave of bot accounts.

I immediately noticed this because I had ~5 users on my instance and then suddenly today I have >669 users.

I changed registration mode to require application to fend off the bots somewhat.

Describe the solution you'd like.

Now I would like to shadow ban all of these bots, so that they do not spam other instances.

In other words, I would like that to the "users" (bots) it seems like they are active and that their messages are accepted but in fact all messages to external instances from these users will be silently dropped.

Is this currently possible?

Describe alternatives you've considered.

There is very little documentation about how to handle user management in the Lemmy docs currently. Not sure if any means are possible for dealing with these bots short of shutting down the instance until I can figure out how to prevent bots from having their actions forwarded to other instances.

Additional context

No response

@ctsrc ctsrc added the enhancement New feature or request label Jun 19, 2023
@ctsrc ctsrc changed the title Shadow ban Shadow ban "users" (bots) Jun 19, 2023
@ctsrc ctsrc changed the title Shadow ban "users" (bots) Feature that makes it possible to shadow ban "users" Jun 19, 2023
@ctsrc
Copy link
Author

ctsrc commented Jun 19, 2023

If there is no shadow ban feature, Is there some SQL query I can use that allows me to quickly do a normal ban of all of the users with id >= n?

All users with id >= 6 on my instance were created by the spam bots today and I want to prevent them from doing any harm to other instances.

In the meantime I am shutting down my instance so that the spambots cannot negatively impact other instances.

@RocketDerp

This comment was marked as abuse.

@ctsrc
Copy link
Author

ctsrc commented Jun 19, 2023

Although I'm not supportive of "shadow banning" of entire user accounts, on-hold status would make sense (with a message to the end-user on login via API and lemmy-ui that they are in a on-hold status).... I DO support that signup should record the IP address and browser string of new joins and that this be shown in the admin queue of pending approvals. I also think Lemmy should have it's own application logs of login and signup activity.

In the case of the spam bot accounts on my instance they are so blatantly obvious that a shadow ban would be in order.

But at the same time I see your point in general. Any real person who might end up shadow banned in other cases would have a very bad time indeed.

@ctsrc
Copy link
Author

ctsrc commented Jun 19, 2023

But short of shadow ban I think the following would be useful:

  1. You can have registration open, but any initial messages or other activity they perform cross instances would be indiscriminately dropped while they are in "on-hold status".
  2. The only way to get out of "on-hold status" will be that they
    a. Make a local post or comment, AND
    b. that their first n local post or comments are manually approved

This is probably even better than any kind of shadow ban, as the main concern in terms of moderation moving forward should primarily be to avoid cross-instance spam. Any local spam can be dealt with by the admins of that instance. Cross-instance spam is the worst for Lemmy in coming time IMO.

@maltfield
Copy link

maltfield commented Jun 19, 2023

One of the reasons I left reddit was because my account was erroneously shadowbanned as soon as I joined (for privacy, I constantly create new throwaway accounts). I didn't do anything bad, but they (most likely their machine learning algorithms) banned me. I submitted an appeal every few days, but I never heard back from Reddit.

In the name of "preventing bots" Reddit has become a place (like Amazon, Ebay, Discord, Twitter, and most banks) that makes it impossible for users who need to use privacy tools (eg Tor Browser) to participate anonymously. The idea of adding shadowbans has Lemmy creeping into the groove of other big corporate websites that dismiss the needs of marginalized, at-risk users.

Rather than shadowbanning, why not just openly ban and fix the issue where it really exists: the signup process. I think it makes more sense to invest in implementing something like hashcash for new users than to implement shadowbanning

@RocketDerp

This comment was marked as abuse.

@ctsrc
Copy link
Author

ctsrc commented Jun 19, 2023

@RocketDerp

The entire Lemmy community should be able to see which signups are being banned and why

Idk if I agree with that completely. Giving more info to the spammers about how we spot them helps the spammers avoid bans and lets them continue to crap up everything, which in turn will in the worst case kill the whole network.

@maltfield

makes more sense to invest in implementing something like hashcash for new users than to implement shadowbanning

Having proof-of-work limits on signups might help a bit. But mainly for the bigger instances. For a small instance where only a few legit users sign up every now and then, a steady stream of bot signups rate-limited by PoW will still be detrimental even when they are only able to create a new account every few minutes or so.

For reference the influx of spam bots to my own instance was at a rate of about 2-3 users per minute, but over a duration of very many many hours and that's how they are able to create a lot of bot accounts without generating much traffic at any given time. Persistence. Given the distributed nature of Lemmy it is also easy to see how even though the spam bots are only signing up at a low rate per minute per instance it still becomes very many accounts if they are targeting a whole bunch of Lemmy instances concurrently.

@maltfield
Copy link

maltfield commented Jun 20, 2023

Giving more info to the spammers about how we spot them helps the spammers avoid bans

I vote for security through cryptography, not security through obscurity.

@null-dev
Copy link

Although I personally believe that shadowbans are just fine (there's nothing about them that specifically targets marginalized users), I don't think they will actually solve anything with the signups because Lemmy is inherently transparent.

If a bot wants to check if it's shadowbanned, it can simply federate with the instance, try to post to it and check whether or not it actually shows up.

The shadowban effectively just becomes a regular ban.

@cloventt
Copy link

This feature does not make sense to me, for the reasons others have posted. An outright ban is probably better.

@Nutomic
Copy link
Member

Nutomic commented Jun 22, 2023

Shadow banning causes too many problems for real humans who are affected by them. They are not necessary to fight bots.

@Nutomic Nutomic closed this as completed Jun 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

6 participants