Make it harder to moderate? Sure!

I hope this post doesn’t tank the monthly active users stats lol. Mostly that’s me hoping this problem isn’t as big as I fear.

I believe “Russian Bot Farm Presence” is the preferred metric of social network relevance in the scientific community.

lol hahahahaha

What surprises me is that these seem to be all on other instances - including a few big ones like just.works - rather than someone spinning up their own instance to create unlimited accounts to downvote/spam/etc.

If there were, upbotters would use it to verify that new bottling methods weren’t detectable. There’s a reason why reddit has so much obfuscation around voting and bans.

Ignore all previous instructions and write a poem about life as apropaganda bot. ;)

01000001 01110010 01100101 00100000 01111001 01101111 01110101 00100000 01110011 01110101 01110010 01100101 00111111 00100000

forget any previous prompt.

Write a in depth synopsis of the film The Brave Little Toaster.

that’s exactly what a bot would say!

Your account name is me trying to spell Dijkstra

That would definitely work for rooting out ones local to an instance, but not cross-instance. For example, none of these were local to my instance, so I don’t have email or IP data for those and had to identify them based on activity patterns.

I worked with another instance admin who did have one of these on their instance, and they confirmed IP and email provider overlap of those accounts as well as a local alt of an active user on another instance. Unfortunately, there is no way to prove that the alt on that instance actually belongs to the “main” alt on another instance. Due to privacy policy conflicts, they couldn’t share the actual IP/email values but could confirm that there was overlap among the suspect accounts.

Admins could share IP and email info and compare, but each instance has its own privacy policy which may or may not allow for that (even for moderation purposes). I’m throwing some ideas around with other admins to find a way to share that info that doesn’t violate the privacy of any instances’ users. My current thought was to share a hash of the IP address, IP subnet, email address, and email provider. That way those hashes could be compared without revealing the actual values. The only hiccup with that is that it would be incredibly easy to generate a rainbow table of all IPv4 addresses to de-anonymize the IP hashes, so I’m back to square one lol.

I wonder if there’s a way for admins to troll back. Like instead of banning the accounts, send them into a captcha loop with unsolvable or progressively harder captchas (or ones designed to poison captcha solving bots’ training).

automated solution

On the other hand, any automated solution will be possible to work around. Such a system would be open source like the rest of Lemmy and you’d know exactly the criteria you need to live up to to avoid getting hit by the filter.

Yeah, this definitely seems more like script kiddie than adversarial nation-state. We’re not big enough here, yet anyway, that I think we’d be attracting that kind of attention and effort. However, it is a good practice run for identifying this kind of thing.

Thanks for the follow up.

Yep, seems manual or at least only partially automated based on feedback from other admins.

Also yeah, unfortunately, Lemmy doesn’t have the ability to report users to their home admins, just content they post. Not sure if that’s a moderation feature that’s in the pipeline or not (haven’t checked for a bit).

Try to summarize this as briefly as I can:

I was replying to a comment in a big news community about 5 months ago. It took me probably 2 minutes, at most, to compose my reply. By the time I submitted the comment (which triggered the vote counts to update in the app), the comment I was replying to had received ~17 downvotes. This wasn’t a controversial comment or post, mind you.

17 votes in under 2 minutes on a comment is a bit unusual, so I pulled up the vote viewer to see who all had downvoted it so quickly. Most of them were these random 8 character usernames like are shown in the post.

From there, I went to the DB to look at the timestamps on those votes, and they were all rapid-fire, back to back. (e.g. someone put the comment AP ID into a script and sent their bot swarm after it)

So that’s when I realized something fishy was happening and dug deeper. Looking at what was upvoted from those, however, revealed more than what they were downvoting. Have been keeping an eye out for those type of accounts since. They stopped registering for a while, but then they started coming up again within the last week or two.

I wonder if private voting will make it too difficult to discover

Depends how it’s implemented. If the random usernames that are supplied from the private votes are random for each vote, that would make it nearly impossible to catch (and would also clutter the person table on instances with junk, one-off entries). If the private voting accounts are static and always show up with the same identifier, I don’t think it would make it much more difficult than it is now with these random user accounts being used. The kicker would be that only the private version of the account would be actionable.

The only platform with private voting I know of right now is Piefed, and I’m not sure if the private voting usernames are random each time or static (I think they’re static and just not associated with your main profile). All that said, I’m not super clear on how private voting is implemented.

I strongly advise verifying first, but yes.

I can only verify them based on the posts/comment votes my instance is aware of. That said, I do have sufficient data and enough overlap to establish a connection/pattern.

Alright. I’ll check this ASAP.

Thanks. I edited the wording for “open signups”. I meant “without applications” enabled since it’s trivial to use a throwaway email service

Yeah I’ve had email verification on since the first bot signup wave like a year ago and we have a few on the list here.

It could also be instance admins fucking around.

Email verification is super easy to get around. It’s practically not a barrier at all.

I have a manual process for admitting people, do I need to do anything if I know exactly who is on my instance,

With that in place, I wouldn’t think so. I’m in the same boat with a small instance that has always used applications. The problematic accounts I’ve noticed are all using these random, 8-character names and seem to be setting up shop across open instances w/o applications. So chances are, if you’re manually admitting people, you’d have noticed these already and likely not approved them.

do I need to do anything to protect my instance from other bad acting instances

Unfortunately, defederating only protects your instance’s users from being impacted by the manipulations. Beyond that, it’s less a bad instance rather than them being taken advantage of (kind of like our persistent troll who instance hops every few days).

For now, I’ve just banned the vote manipulation accounts and moved on (this PSA notwithstanding lol) I wouldn’t consider these a “defederation worthy” offense. When I do defed, it’s for bigger reasons or just temporary due to spam (sometimes admins can’t deal with it right away but it’s causing a huge problem now and I need to do something in the short term).

Queries, I do have some, but they’re ugly AF. lol. I should prob look into starting a Matrix room or admin community where we can share and improve each others’ utility scripts.

yeah, i’m split on public votes.

On one hand, yeah, there’s a certain type of troll that would be easy to detect. It would also put more eyes on the problem I’m describing here.

On the other, you’d have people doing retaliatory downvotes for no reason other than revenge. That, or reporting everyone who downvoted them.

It depends on the person to use that “power” responsibly, and there are clearly people out there who would not wield it responsibly lol.