Look, we can debate the proper and private way to do Captchas all day, but if we remove the existing implementation we will be plunged into a world of hurt.
I run tucson.social - a tiny instance with barely any users and I find myself really ticked off at other Admin’s abdication of duty when it comes to engaging with the developers.
For all the Fediverse discussion on this, where are the github issue comments? Where is our attempt to convince the devs in this.
No, seriously WHERE ARE THEY?
Oh, you think that just because an “Issue” exists to bring back Captchas is the best you can do?
NO it is not the best we can do, we need to be applying some pressure to the developers here and that requires EVERYONE to do their part.
The Devs can’t make Lemmy an awesome place for us if us admins refuse to meaningfully engage with the project and provide feedback on crucial things like this.
So are you an admin? If so, we need more comments here: https://github.com/LemmyNet/lemmy/issues/3200
We need to make it VERY clear that Captcha is required before v0.18’s release. Not after when we’ll all be scrambling…
EDIT: To be clear I’m talking to all instance admins, not just Beehaw’s.
UPDATE: Our voices were heard! https://github.com/LemmyNet/lemmy/issues/3200#issuecomment-1600505757
The important part was that this was a decision to re-implement the old (if imperfect) solution in time for the upcoming release. mCaptcha and better techs are indeed the better solution, but at least we won’t make ourselves more vulnerable at this critical juncture.
Nope. This is a huge accessibility fail. Any instance that has captcha enabled is locking out anyone even slightly low vision. Everyone should be manually approving all applications. It keeps instances small, and ensures that the fediverse remains distributed. Once we start having a spam problem, we should all just be defederating every instance that offers open registration; make a script to scan for it, and update the blocklist. Nobody should be running that way. If you are, not only are you allowing spam, you’re also probably allowing humans who are engaged in ban evasion and other bad things. All posts and comments that come from your instance are in some small part your responsibility. Be at least vaguely aware of who your users are. If you ban one, and you run open registration, how do you intend to make sure they’re not the user you just banned, signing up with another email address? We’re not big tech, so we don’t have the kinds of tools (IP reputation lists, lists of VPN IP addresses, etc) to fight ban evasion in any kind of automated way.
Almost every captcha implementation has an audio method in addition to the image portion. This is throwing the baby out with the bath water.
IP reputation lists, deny lists, username/email bans, are trivially bypasses and not worth the admin effort to update or maintain.
I use audio captcha regularly? Which major implementations don’t support audio captchas?
And everyone should pay their mods for their time? I can get behind that. Not sure how successful a paid service would be in replacing a free one tho…
Other bad things like slippery slope fallacies?
Wait, what solution are you suggesting? Did your instance involve a background check or something? I don’t want to use lemmy if it means I have to dox myself.
Also a leap in logic. Domain providers (ex. Cloudflare) regularly offer these services very affordably. Kind of ironic that you believe a completely digital, federated message board in this day and age can’t leverage computers to run it. This feels like an argument someone made on a Usenet forum in 1990.