Protect. Moderate. Purge. Your. Sever.
Please. Captcha by default. Email domain filters. Auto-block federation from servers that don't respect. By default. Urgent.
And yes, to refute some comments, this publication is being upvoted by bots. A single computer was needed, not "thousands of dollars" spent.
As someone with his own email domain, screw you for even thinking about suggesting domain filters.
And blacklist domain filters are pretty useless when you can create unlimited emails with johndoe+anything@gmail.com
Thank you for voicing this out! Was literally my first reaction as well
d
I second this
This right here.
Op, if you’re not ready to moderate, don’t spin up your own server or do your own private instance. If you’re going to moderate, do it properly and don’t spew bad ideas while hiding behind a dumb “alert” throwaway.
I'm not really enthusiastic about email filters either, from a privacy standpoint. Plenty of companies that go harvest email addresses to link identities to activity.
If the CAPTCHA can't handle it, then it ain't doing its job.
No, you've (maybe) limited your singular solitary instance's growth: your instance is not "Lemmy" and admins should do whatever they find works for them, is something they can easily enforce, and resolves the problem.
If you want to geoip limit signups to Skokie, Illinois? Great! If it works for you and keeps your instance from being The Problem, then it's a valid solution.
(I don't disagree that email domain blocks are not a singular solution to any abuse problem, but I also think that whatever works for the individual admin is perfectly reasonable, and email blocks CAN be worthwhile.)
I believe you can literally just add a . To the end of your own gmail and it will go to yours. Ie hello.1@gmail.com will go to hello@gmail.com.
First of all: I'm posting this from my .ml alt. Because i can not do it from my .world main. That i can't do it, i found out just because i was waiting for a response on a comment where is was sure that the OP would respond. After searching, i found out that my comment and my DM's never where federated to .ml.
So, that said: I'm all for defederating bad instances, i'm all for separation where it makes sense. BUT:
Minimal features we need:
Currently, all we do is: Make lemmy look broken
And before someone starts with: "Then help!", i do. I do in my field of expertice. I'm a PostgreSQL Professional. So i have build a setup to messure the lemmy SQL performance, usage patterns, and will contribute everything i can to make lemmy better.
(I tried rust, but i'm to much C++ guy to bring something usefull to the table beyond database stuff, sry :( )
Show users that the community they try to interact with is on a server that defederated the users instance
Not only that, also show users when comments in any community are made by users from an instance that your instance defederated.
Because you(instance A) may very well only be able to see half of the comments in a thread of a community of instance B because half of them were made by users of instance C which instance A defederated.
Right now the comments just don't get copied to your instance at all, which also leads to followup comments not being visible even if they are not from defederated instances.
Instead I'd like everything to be copied and then flagged based on defederations. Just don't show the original content and instead show a hint that a comment can't be seen because of defederation would be enough.
At least that way we know that we're missing something.
Because simply not showing it also leads to confusion why you see less comments than other users on another instance.
And this goes both ways. The user from the other instance(who can still see your comment because his instance didn't defederate yours) should also see that I'm from an instance that defederated his instance directly by looking at my post before commenting, maybe in form of a symbol or a note next to my username, so that he knows it doesn't make any sense to comment on my post.
In theory, yes. You only need a Activitypub library and some lines of code.
Everyone is talking about how these things won't work. And they're right, they won't work 100% of the time.
However, they work 80-90% of the time and help keep the numbers under control. Most importantly, they're available now. This keeps Lemmy from being a known easy target. It gives us some time to come up with a better solution.
This will take some time to sort out. Take care of the low hanging fruit first.
Plus, if this becomes the "bot wild west" at such an early stage, the credibility hit will be a serious hindrance to future growth...
The admin https://lemmy.dbzer0.com/u/db0 from the lemmy.dbzer0.com instance possibly made a solution that uses a chain of trust system between instances to whitelist each other and build larger whitelists to contain the spam/bot problem. Instead of constantly blacklisting. For admins and mods maybe take a look at their blog post explaining it in more detail. https://dbzer0.com/blog/overseer-a-fediverse-chain-of-trust/
So defeating the point of Lemmy? Nah, that's a terrible "solution" that will only serve to empower big servers imposing on smaller or even personal one's.
It's probably the opposite. I'd say that right now, the incentives for a larger server with an actual active user base is to move to a whitelist only model, given the insane number or small servers with no activity but incredibly high account registrations happening right now. When the people controlling all of those bot accounts start flexing their muscle, and flooding the fediverse with spam it'll become clear that new and unproven servers have to be cut off. This post just straight up proves that. It's the most upvoted Lemmy post I've ever seen.
If I'm right, and the flood of spam commeth then a chain of trust is literally the only way a smaller instance will ever get to integrate with the wider ecosystem. Reaching out to someone and having to register to be included isn't too much of an ask for me. Hell, most instances require an email for a user account, and some even do the questionnaires.
The (simplified) way it works is it reads data from the public observer's API and check if ((total users > (totalPosts + totalComments) > susScore) as a "suspicious" community. "susScore" is configurable if you want to run your own instance of it.
db0 probably knows what they're talking about, but the idea that there would be an "Overseer Control Plane" managed by one single person sounds like a recipe for disaster
I hear you. For what it's worth it is mentioned in the end of the blog post, the project is open source, people can run their own overseer API and create less strict or more strict whitelists, instances can also be registered to multiple chains. Don't mistake my enthousiasm for self run open social media platforms for trying to promote a single tool as the the be-all and end-all solution. Under the swiss cheese security model/idea, this could be another tool in the toolbox to curb the annoyance to a point where spam or bots become less effective. Edit: *The be-all and end-all *not be and end all solution
The blog post dives into how it's hard for spammers to automate adding themselves onto the whitelist because its a chain of trust. You have to have an existing instance owner to vouch for you, which they can revoke at any time. A spammer couldn't do things like run a "clean" instance, and then whitelist off that, because presumably someone would try to contact the owner of the presumed "clean" instance to get them to remove the spam. When they don't respond, or only partially address the issue, it's possible to pull rank and contact the person further up the chain of trust.
In short, it's real people talking to each other about spam issues, but in a way that scales so that an owner of one instance doesn't need to personally trust and know every other instance owner. It should allow for small single user instances to get set up about as easily as any other instance. Everyone has to know and talk to someone along the chain.
The real downside of the system is that people are human, and cliques are going to form that may defederate swathes of the fediverse from each other. I kinda think that's going to happen anyways though.
A chain of trust is the best proposal I've seen for addressing the scaling issues associated with the fediverse. I'm not associated with that guy at all, just saying I like his idea.
-- edit
On second thought, getting your instance added to the chain of trust is literally no more difficult than signing up for an instance with a questionnaire. It's basically that but at the instance level instead of the user level.
Aren't in e-mail it basically impossible to host your own servers anymore?
Obviously biased, but I'm really concerned this will lead to it becoming infeasible to self-host with working federation and result in further centralization of the network.
Mastodon has a ton more users and I'm not aware of that having to resort to IRC-style federation whitelists.
I'm wondering if this is just another instance of kbin/lemmy moderation tools being insufficient for the task and if that needs to be fixed before considering breaking federation for small/individual instances.
He explained it already. It looks for a ratio of number of users to posts. If your "small" instance has 5000 users and 2 posts, it would probably assume a lot of those users would be spam bots. If your instance has 2 users and 3 posts, it would assume your users are real. There's a ratio, and the admin of each server that utilizes it can control the level at which it assumes a server is overrun by spam accounts.
Who controls the Overseer Control?
It's been answered further below. Yeah it's that one bloke who did it at https://lemmy.dbzer0.com/u/db0 . The projects also open source though, so anyone can run their own Overseer Control server, with their own chain of trust whitelist. I suspect many whitelists will pop up as the fediverse evolves.
My understanding from the beehaw defed is that more surgical moderation tools just don't exist right now (and likely won't for awhile unless the two Lemmy devs get some major help). Admins only really have a singular nuclear option to deal with other instances that aren't able to tackle the bot problem.
Personally I don't see defederating as a bad thing. People and instances are working through who they want to be in their social network. The well managed servers will eventually rise to the top with the bot infested and draconian ones eventually falling into irrelevance.
As a user this will result in some growing pains since Lemmy currently doesn't offer a way to migrate your account. Personally I already have 3 Lemmy accounts. A good app front end that minimizes the friction from account switching would greatly help these growing pains.
Lemmy.world has rules that are up on https://mastodon.world/about - if posts from other instances do not follow these rules the posts will be deleted and if needed the user will be warned/banned. If there is an entire instance that might be a problem, they might ultimately become defederated. Yes this is the last option, but sometimes it's also the only option. Mod and admin tools are quite limited currently and there's just some content we don't want to be linked with.
Read more about the defederation of exploding-heads.com here: https://lemmy.world/post/747912
I'm against email domain whitelists and captchas (at the very least Google's captchas).
Why against captchas? Why Google's in particular?
It largely just trains their AI, and a lot of people don't want to do that.
Also, a lot of captcha implementations have issues with content blockers and whatnot.
@archchan@lemmy.ml have a literary "arch" in their name. Do you really have to ask why a fan of arch linux is against anything that google has even touched?
Look up the origins of IRC's EFNet, which was created specifically to exclude a server that allowed too-easy federation and thus became an abuse magnet.
Now that’s a name I’ve not heard in a long time… a long time
Folks running new federated networks gotta learn this stuff!
that was my home network for many years
Wow it’s been so long since I’ve thought about IRC. Does anyone you know still use it regularly?
What's the requirement to become federated? Say someone starts their own server, are they able to load it with bots prior to federating then suddenly go online and fuck shit up before they get defederated?
I guess what I'm asking is there action needed by every instance before they are federated with a new instance. Do the admins of each instance have the opportunity to do their due diligence before federating with someone or is it automatic?
If someone really wants to attack the network, they'll attack it with custom software, not just by clicking on a lot of buttons in the web UI.
Auto-block federation from servers that don't respect.
NO! Do NOT defederate due to how an instance chooses to operate internally. It is not your concern. You should only defederate if this instance causes you repeated trouble offenses. Do not issue pre-emprive blanket blocks.
If they choose not to take measures against bots defederation is the only way to keep that wave out of your own instance.
Do not make assumptions on how other instances are operating. You don't know what measures they're taking. If they did not cause you trouble yet, don't try to predict it by making generalizations. It creates an echo chamber Internet.
Agree! Defederation is a nuclear option. The more we do it, the more we reduce the value of "the fediverse", and the more likely we are to kill this whole project.
I think defederation should only be a consideration if an instance is consistently, frequently becoming a problem for your instance over a large period of time. It's not a pre-emptive action.
Ah shit i was just about to set up a monolith forum
Isn't this what all you lemmy-worlders got mad at Beehaw for doing? I don't think it's unreasonable to ask for a small statement from people as an anti-spam measure (a sort of advanced captcha), though of course the big problem there is reviewing all the applications in a timely manner. Still, I think there's room for more and less exclusive instances. The tools are there for instance owners to protect their instances however they choose.
We already have existing anti-bot measures in the world that don't involve writing a lame sentence. Also, it's very easy to spoof an introductory sentence. You could train a fairly small language model to do so.
Beehaw got their knickers in a twist because of some spammers, back when lemmy.world and shitjustworks had... maybe 30,000 registered users in total. The solution there was adding more moderators. You don't chop your leg off because you got a few papercuts.
If you look at the volume of bots (some instances went from hundreds of users to >12,000 overnight), that's potential for worry. There's ~500,000 bot accounts sitting out there waiting to be activated. No amount of moderators can block that fast enough, and that's when de-federation should be considered.
Please stop trying to tell me how to run my instance. If I wanted your input or your rules I would have joined your instance.
If you have a problem with my instance you're in your right to defederate or block me. But I do not care about your plea to enable shit that I don't want to enable.
What I will say is that congrats! You've shown that you're willing to bot manipulate your post. That earns a ban from my instance! That's the glory of the Fediverse.
I get you probably don't care at all about people who interact with your community but letting bots run free is something I really dislike. I suspect the majority of users feel the same.
Just takes one disgruntled person who is unhappy with you to flood your server without any captcha or other measures taken to prevent it. Might be still under the radar to a degree as of right now but that will not always be the case.
for larger instances, this makes sense. For us smaller instances, just add a custom application requirement that isn't about reddit. though i'll be adding captcha too if they keep at it (every hour, 2 bots apply).
I've seen bots trying to create accounts, it's the same boring message about needing a new home because "random reason about reddit". I'll borrow a quote from Mr Samuel Jackson: "I don't remember asking you a god damn thing about reddit"... and application is denied.
I mentioned Reddit in an application. I feel like that would come up in legitimate applications at the moment. Is it easy to tell the bots from actual applicants?
In my case, yes. I asked for a reason written in code (working or not). Since I intend to be a DevOps focused instance, there’s no excuse. Most humans would read the application and I don’t feel bad for denying based on this requirement.
Also helps that after 8 of those bots apps, the message is very similar. If there was a human in that mix, they can dm me and ask for reconsideration.
I somehow missed your first bit about asking for it specifically to not be about reddit. That makes sense.
actually needing a new home from reddit is the exact terminology I used. That doesn't mean bots lmao
Mine got blown up a day or two ago before I had enabled Captch. About 100 accounts were created before I started getting rate-limited (or similar) by Google.
Better admin tools are definitely needed to handle the scale. We need a pane of glass to see signups and other user details. Hopefully it’s in the works.
Looking at you oceanbreeze.earth, your instance is worth defending from bots
I learned about this community from your post. That's so unfortunate.
Auto-block federation from servers that don’t respect.
What does this mean?
In other words, for every server that does not adhere to the other rules mentioned (captchas, email requirements, etc), automatically de-federate from all of them.
If you're not familiar with what "de-federate" means, check out this article on federation concepts
We need a distributed decentralized curated whitelist that new servers will apply to be on it and hopefully get a quick week max response after some kind of precisely defined anti spam/bot audit. Also then periodic checks of existing servers.
Like crypto has transaction ledger confirmed some kind of notabot confirmation ledger chain.
Weak side if bot servers get on whitelist somehow in enough numbers they can poison it
Mind you this whitelist chain has nothing to do with content itself just whether it is AI or human
Agreed, this is actually the use case for a blockchain. Intances should produce documents attesting to the quality of other instances. This would allow each instance to construct white or black lists off thes data and propogate info on bad actors or new quality servers. It would be decintalized, consistent and signed.
There is a number of blockchain attempts to do this already. Because they are servers, it should work well here.
Just saw a WAVE of bot art flow down the "Top New" feed. It then promptly stopped. And then when I reloaded the page, it was gone. So I think it's working...
Please calm down lol
dude, it's important.
Email domain filters
Okay, gmail should definitely be blacklisted, because it's extremely easy to abuse. Microsoft email domains too. What domains should be allowed then?
Email domain filtering makes no sense when it is easy enough to just set up your own email server for bots. It will only hinder legit users and low level bad actors, not the real threat of major bot farms.
Lmao are you the guy from yesterday?
You have bots altering this content.
Post HERE
Image Transcription: Meme
['Man vs. Giant' - Dramatic artwork depicting 'Yhorm the Giant' from 'Dark Souls 3' towering over the protagonist from 'Dark Souls 3', 'Ashen One'. The giant figure holds a massive sword that is planted in the ground with both hands, while the comparitively tiny 'Ashen One' holds a regular sized sword in his right hand and adopts a fighting stance. Text placed over the stomach of the giant character, and over the smaller protagonist figure, reads as follows]
I'm a human volunteer transcribing posts in a format compatible with screen readers, for blind and visually impaired users!
Whats the purpose of these bots?
Spam and vote manipulation are the two biggest concerns.___
Votes are visible to the world, unlike with Reddit, so that'll be vulnerable to data analysis on behavior.
Crappily malicious username you have there, are you the baddie?
No, thankfully, I only have 0.6% of the villain's capacity.
this
Is it possible to require an authentication app or something to make an account? Require a specific score on a flash game like snake? Or is that stupid? I don't know, I'm not a dev ¯(ツ)_/¯
You dropped this
Here’s how you type it in markdown:
¯\\\_(ツ)\_/¯
Can't wait to have other people say what I can or cannot see. /s
Sigh....
All of those ideas are bad.
I am not saying captchas are completely useless, they do block the lowest hanging fruit currently. That- being most of the script kiddies.
Issue number one, has already been covered below/above by others. You can use a single gmail account, to basically register an unlimited number of accounts.
Issue number two. Spammers LOVE to use office 365 for spamming. Most of the spam I find, actually comes from *.onmicrosoft.com inboxes. its quick for them to spin it up on a trial, and by the time the trial is over, they have moved to another inbox.
This is how you destroy the platform. When you block legitimate users, the users will think the platform is broken. Because, none of their comments are working. They can't see posts properly.
They don't know this is due to admins defederating servers. All they see, is broken content.
At this time, your best option is for admin approvals, combined with keeping tabs on users.
If you notice an instance is offering spammers. Lets- use my instance for example- I have my contact information right on the side-bar, If you notice there is spam, WORK WITH US, and we will help resolve this issue.
I review my reports. I review spam on my instance. None of us are going to be perfect.
There are very intelligent people who make lots of money creating "bots" and "spam". NOBODY is going to stop all of it.
The only way to resolve this, is to work together, to identify problems, and take action.
Nuking every server that doesn't have captcha enabled, is just going to piss off the users, and ruin this movement.
One possible thing that might help-
Is just to be able to have an easy listing of registered users in a server. I noticed- that actually... doesn't appear to be easily accessible, without hitting rest apis or querying the database.
This is all 100% correct. People have already written captcha-bypassing bots for lemmy, we know from experience.
The only way to stop bots, is the way that has worked for forums for years: registration applications. At lemmy.ml we historically have blocked any server that doesn't have them turned on, because of the likelihood of bot infiltration from them.
Registration applications have 100% stopped bots here.
You're right that captchas can be bypassed, but I disagree that they're useless.
Do you lock your house? Are you aware that most locks can be picked and windows can be smashed?
captchas can be defeated, but that doesn't mean they're useless - they increase the level of friction required to automate malicious activity. Maybe not a lot, but along with other measures, it may make it tricky enough to circumvent that it discourages a good percentage of bot spammers. It's the "Swiss cheese" model of security.
Registration applications stop bots, but it also stops legitimate users. I almost didn't get onto the fediverse because of registration applications. I filled out applications at lemmy.ml and beehaw.org, and then forgot about it. Two days later, I got reminded of the fediverse, and luckily I found this instance that didn't require some sort of application to join.
But even then, however, what's to stop an army of bots from just ChatGPTing their way through the application process?
I went to a website to generate a random username, picked the first option of polarbear_gender, and then just stuck that and the application questions for lemmy.ml into ChatGPT to get the following:
I don't know the full criteria that people are approved or declined for, but would these answers pass the sniff test?
I'm just worried that placing too much trust in the application process contributes to a false sense of security. A community that is supposedly "protected" from bots can be silently infiltrated by them and cause more damage than in communities where you can either reasonably assume bots are everywhere, or there are more reliable filtering measures in place than a simple statement of purpose.
chatgpt.
Wait what's the difference between the suggested auto block and you historically blocking instances without applications? Is there other criteria you use to determine the block?
Not saying I know the answer, just curious.
Haven't you heard of the "Swiss cheese" model of security?
The best way to ensure your server is protected is to unplug it from the Internet and put it in an EMF-shielded Faraday cage.
There's always a tradeoff between security, usability and cost.
captchas can be defeated, but that doesn't mean they're useless - they increase the level of friction required to automate malicious activity. Maybe not a lot, but along with other measures, it may make it tricky enough to circumvent that it discourages a good percentage of bot spammers.
I disagree. I think the solution is moderation. Basically, have a set of tools that identify likely bots, and let human moderators make the call.
If you require admins to manually approve accounts, admins will either automate approvals or stop approving. That's just how people tend to operate imo. And the more steps you put between people wanting to sign up and actually getting an account, the fewer people you'll get to actually go through with it.
So I'm against applications. What we need is better moderation tools. My ideal would be a web of trust. Basically, you get more privileges the more trusted people that trust you. I think that should start from the admins, then to the mods, and then to regular users.
But lemmy isn't that sophisticated. Maybe it will be some day, IDK, but it's the direction I'd like to see things go.
HackerNews does something similar where new users don't have the ability to down vote until they have earned enough upvotes from other users.
We could extend that, and literally not allow upvotes to properly register if the user is too new. The vote would still show on the comment/post, but the ranking of the comment/post will only be influenced by seasoned users. That way, users could scroll down a thread, see a very highly upvoted comment bang in the middle, and think for themselves "huh, probably bots".
Very hierarchical solution, heavily reliant on the mods not playing favourites or having their own agenda.
But- that is basically agreeing with the context of what I said.
I don't like them either, but, the problem is, I don't have ANY other tools at my disposal for interacting with and viewing the other users.
Just a way to audit user activity and comments would be a big start. I honestly cannot find a method for doing this via the UI. Having to resort to querying the database just to dig up details.
Captcha is like locking your car... There are still ways to get in, but it blocks the casual efforts.
Do you review upvote bots? The spam is an easily replaceable account, the coordinated army of upvote bots may be harder to track down.