this post was submitted on 20 Jun 2023
202 points (100.0% liked)
Technology
37699 readers
324 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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Just enable admin approval and put a sensible registration rate limit. Works better without being a massive accessibility problem with dubious help against bots.
Sure, that might work for me, but it doesn't scale well for many other larger instances.
I'm not saying to not improve, quite the contrary, improvement is important. I'm saying don't take away the ONE thing that's preventing the spam issue from getting worse.
To be clear, I am a developer in real life. I'm not just talking out of my ass. There are way to roll out a new implementation without leaving everyone exposed.
Since you're a dev, submit a PR for a new captcha. I'm not even using the feature on my instance as I have open signups disabled. So no, I won't be hassling the devs. If something comes up that I want changed badly enough, I'll implement it myself.
Maybe the problem is with running larger instances without enough staff?
I do see a potential problem in that lack of attention will result in waves of defederation over time. But I don’t think captchas will provide a long-term solution. Long-form applications work well for mid-sized sites and smaller… or at least will until bots start using AI to fill them out.