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.

  • th3raid0r@tucson.socialOPEnglish
    1·
    1 year ago

    5 huh? That’s actually noteable. So far I haven’t seen a real human user take longer than a couple of hours to validate. Human registrations on my instance seem to have a 30% attrition. That is, of 10 real human users, I can reasonably expect that 3 won’t complete the flow. It seems like your case might be nearing 40-50% which isn’t unheard of but couple this with the quickness that these accounts were created - I think you are looking at bots.

    The kicker is, though, if one of them IS a real user, it’s going to be almost impossible to find out.

    This is indeed getting more sophisticated.

    I wish I could see this time period on a cloudflare security dashboard, I’m sure there could be a few more indicators there.

    • HTTP_404_NotFound@lemmyonline.comEnglish
      1·
      1 year ago

      cloudflare security dashboard

      Didn’t really see anything that stood out there either. A handful of users accessing via tor, but, thats about it.

      Ended up turning the security policy from low, back up a bit though, forgot I turned it down while troubleshooting some federation issues.

      • th3raid0r@tucson.socialOPEnglish
        3·
        1 year ago

        Oh! I just remembered something. Isn’t there a site that recommends a lemmy instance? Might it make sense that multiple users found your website because they change the recommendation to distribute new users to smaller instances (hourly perhaps)? Does that sort of pattern hold in this case?

          • th3raid0r@tucson.socialOPEnglish
            0·
            1 year ago

            Interesting, I definitely see mine. I’m wayyyyyy at the bottom of the popular section, (likely due to the 9 bots that added themselves before I banned the accounts.).

            I wonder if one of the settings in your firewall is blocking that particular bot?

            I don’t recall when I would’ve done the same, but I do recall not being on join-lemmy until - well - now actually.

            • HTTP_404_NotFound@lemmyonline.comEnglish
              1·
              1 year ago

              /shrugs. isn’t much in the way of firewall logic, even at the cloudflare logic. Although- only :443 is actually forwarded to go anywhere.