this post was submitted on 19 Jun 2023
26 points (100.0% liked)
Lemmy Support
4654 readers
3 users here now
Support / questions about Lemmy.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
What worked for me is manually deleting those entries from the database through the console. Gotta delete it from the postgresql database if you don't have any real user sign ups during the spam sign ups, you can just delete all entries after a certain point. That's how I did it.
Did you actually delete them or set the deleted column? I'm anxious of leaving dangling references which might cause errors to pop up elsewhere but I'd rather get rid of them completely if that doesn't seem to cause problems.
I also found it wasn't reflected in the user count until I manually manipulated the
site_aggregatestable. I don't know if that would have caught up eventually.You have to delete them from local_users and person tables. Be careful with person table to not delete entries from users outside your Instance. It worked for me and fixed the user count in my sidebar.
Cool. I think I'm going to give it a few days in case I deleted someone I didn't want to. If I hear no complaints (I'm pretty sure I'm the only real local user on my instance anyway 😂) I'll delete out the db. Thanks!
No problem! Hopefully others that had this problem can fix their instance too. Since we don't know when the spam accounts will become active and start posting or if that spam attack was just to mess with us.