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.
Not entirely sure about the misframing thing, because I see a pretty clear pattern of arguing towards perfection, I’m not sure how one could look at that and not arrive at the interpretation. It didn’t seem to matter how complex the task was, the point was always “that version can be overcome - it’s pointless”.
All the while missing the point. If we’re arguing “stops enough to matter” then the answer is self evident. The captcha is currently the difference between a bot problem and not for many and that’s what’s happening now, not in the future (as near or as distant it may be). Multiple things can be true indeed “This is a bad implementation and needs replacement” “this is currently stopping things from getting worse”, but that doesn’t also mean “We should remove it now and not worry about a replacement until afterwards”.