219
submitted 1 year ago* (last edited 1 year ago) by th3raid0r@tucson.social to c/technology@beehaw.org

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.

(page 2) 50 comments
sorted by: hot top controversial new old

Just created the instance, now the spammers consumed all my email allowances today :( I just enabled CAPTCHA now, now I'm gonna wait till tomorrow how much this makes difference.

[-] MJBrune@beehaw.org 6 points 1 year ago* (last edited 1 year ago)

While I am glad that they listened to the community. Everyone seemed to forget that you do not have to upgrade to the latest version. If the risks outweigh the benefits it's perfectly fine to stay at the last working version. There is also the possibility of backports (forward ports in this case?) and manual restoration of Captchas to get the features you want out of the later versions if you have the development skillset to do so.

[-] fastfinge@rblind.com 5 points 1 year ago

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.

load more comments (1 replies)
[-] caron@lemmy.ca 3 points 1 year ago

I don't have a responsibility to do anything. This isn't my issue and you can't force me to care.

load more comments (2 replies)
load more comments
view more: ‹ prev next ›
this post was submitted on 20 Jun 2023
219 points (100.0% liked)

Technology

37739 readers
720 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:


This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago
MODERATORS