the only mass solution i found to this was that i installed pgadmin, logged into the db, and manually removed all the bot accounts from local_user. you should also remove them from the person table as well (you can easily find them if you do SELECT * FROM person WHERE local = true ORDER BY published DESC in the query tool), that way they don't show up in your instance stats, but removing them from local_user would be enough to stop them from logging in.
this post was submitted on 18 Jul 2023
60 points (95.5% liked)
Lemmy
2172 readers
57 users here now
Everything about Lemmy; bugs, gripes, praises, and advocacy.
For discussion about the lemmy.ml instance, go to [email protected].
founded 4 years ago
MODERATORS
thanks I will try this.
I feel attacked. 😂
In all seriousness. They probably are bots but I personally just let bitwarden make me a username and this is the default way to generate one.
lol, this made me chuckle... Are you an AI bot?
No fellow human of course I am not an Artificial Intelligence. I have no idea what would make you think I was.
Bitwarden is great, takes out all the creativity and you end up with a username like mine.
I guessing you just deleted to numbers and went with the first option like I did 😂
This is a problem for any web application. There are many solutions, none are perfect.
On some sites (like 4chan) you're required to solve a captcha every single time you post, unless you pay a yearly fee not to.
To avoid it, you would need people actively monitoring, banning, and setting up bot detection patterns.
Then again, there are cheap services online where real people are hired to create human accounts and spam you anyway, so..
You should be able to purge the user if you visit their profile.
And How would I do that in the UI? This is the issue, haven't found a way to even find those users on my system, even though it marks at 15 extra users.
Did you find a solution. The above comment with the database query should work. You can access the docker container where the database is running with docker exec -it instancedomain_postgres_1 busybox /bin/sh and then run psql -U databaseuser which by default is 'lemmy'.
Check docker ps to know the exact name of the postgres container which in your case likely is lemmytalungorg_postgres_1
Thanks, I have gone through and identified the REAL accounts gathered the ID's and deleted the rest from local_user and person tables.
Haven't really played much with Postgress so took some time to look up all the functionality with that.
EDIT: yup, made sure the person one was local only :)
view more: next ›