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.

  • Gaywallet (they/it)@beehaw.org
    link
    fedilink
    English
    arrow-up
    60
    ·
    edit-2
    1 year ago

    I find it reasonably amusing that many people’s solutions seem to be “just defederate bro”. As in if this conversation isn’t happening on an instance which chose to defederate and received thousands of negative comments, from other instances, about this choice. We’re still being harassed by users from other instances, on posts all over our instance, who are unhappy with this.

    I also find it amusing that many people say the solution is to build your own solution. Do you not want the fediverse to grow? If you want people to feel like they can just spin up their own instances, you need to stop assuming that they have the ability to do their own development, their own sysop and sysad, their own security, their own community management, their own… everything. People are not omniscient and the outright hostility towards someone asking for help, or surfacing their opinion on the matter isn’t helping.

    Without adequate tools, I don’t see how most instances aren’t driven towards simply existing on their own. Large instances need tools to deal with malicious actors, as they are the targets. The solution to defederate ignores the ability for people to just spin up new instances, to hijack existing small instances with less resources for security, sysops, to watch/manage their DB, to prevent malicious actors. I’ve already seen proposed solutions which involve scraping for all instances with less than a certain number of users to defederate on principle (inactive, too many users/post ratio). We’re fighting spam bots right now, who are targeting instances which don’t have captcha enabled.

    Follow this thinking through to it’s conclusion. If the solution is to defederate, and there are potentially unlimited attack vectors, what must a large instance do to not overburden its resources? Switch from blacklist to whitelist? Defederate from all small instances? How is this sustainable for the fediverse? If you want people to be interacting with each other, you need to provide the tools for this to happen in the presence of malicious actors. You can’t just assume these malicious actors won’t exist, or will just overcome any and all obstacles you throw in their way because you’re smart enough to understand how to bypass captcha or other issues.

    This isn’t just an issue of whether captcha or some other anti-spam measure is used, it’s an issue about the overall health of the fediverse. Please think wider about the impact before offering your 2c about how captchas are worthless or how you hate cloudflare. I don’t think the user that posted this cares about the soapbox you want to preach from- they’re looking for solutions.

    • alyaza [they/she]@beehaw.orgM
      link
      fedilink
      English
      arrow-up
      25
      ·
      edit-2
      1 year ago

      I also find it amusing that many people say the solution is to build your own solution. Do you not want the fediverse to grow? If you want people to feel like they can just spin up their own instances, you need to stop assuming that they have the ability to do their own development, their own sysop and sysad, their own security, their own community management, their own… everything. People are not omniscient and the outright hostility towards someone asking for help, or surfacing their opinion on the matter isn’t helping.

      to underscore this: if we had to do all of this this instance would not exist and/or we would have shut off applications about 10,000 people ago. we do not have the capabilities to do all of this even now with like a dozen people volunteering to help us! we are one of the largest instances on Lemmy and one of the most active! please recognize how ridiculous and burdensome it is to just throw more non-inbuilt tech at problems like this, and how exclusionary that is going to be to anybody who is without free time and extremely tech-savviness. if you want this space to grow it needs to be at a point where people can just use it and not have to worry about this shit.

      • th3raid0r@tucson.socialOP
        link
        fedilink
        English
        arrow-up
        22
        ·
        edit-2
        1 year ago

        I’m a DevOps/SysOps/SecOps engineer - have been for over a decade now. Even if I CAN do all the things listed, it takes time to do it. It takes time to configure your networking layer, especially when documentation of the underlying app is in flux and never 100% correct. It takes time to secure your server, especially when the “prod” configuration in the repo isn’t really that secure at all.

        Folks saying to just “code it myself” - sure, let me stop doing my day job and start planning on this completely unpaid enhancement. Let me tell my wife - “Sorry babe, gotta prove this internet person wrong and it must be today - can’t go to board game night with you”. I mean, I’ll actually likely end up coding it myself, but when I can. Not when the trolls who say “Oh, come on, it’ll be EZ” - yeah, I know better than that.

        Folks just say to “Use other solutions” - Great! I already budgeted 150/month of my own money. Oh wait, that doesn’t matter much when I have to worry about instances that can’t spend that type of scratch.

        • towerful@beehaw.org
          link
          fedilink
          English
          arrow-up
          6
          ·
          1 year ago

          The 2 Lemmy devs have funding. About 1500 total from community support, with the rest coming from a sponsorship/incubator type deal. A deal which pays out when targets/goals are achieved.
          Which made me laugh at this:

          sure, let me stop doing my day job and start planning on this completely unpaid enhancement

          Which is entirely what you are asking the Lemmy devs to do.

          Thanks for raising awareness of the spam-bot-account issue.

          • th3raid0r@tucson.socialOP
            link
            fedilink
            English
            arrow-up
            3
            ·
            1 year ago

            Well I am making a distinction between creating a newer implementation and rolling back to an older, known implementation. It’s why I find it bizarre when folks point out that there’s a new feature request and a PR is guarenteed accepted - yes, but that will take more time than reverting some commits and maybe retrofitting if needed. The entire point I was trying to make is that they could just roll back, and when the new feature is ready, we can go right to it. I’m not (at least intentionally) asking for grandiose work and assuming going back is quicker and more readily available than waiting for a new solution to be implemented.

          • progandy@feddit.de
            link
            fedilink
            English
            arrow-up
            2
            ·
            edit-2
            1 year ago

            In the same article where they provided that 1500 number, the developers said they currently do not receive sponsorship money, as they are delaying those targets in order to improve stability and robustness.

            Update: It looks like that number is about double now, about 3000 accross their three donation platforms.

    • th3raid0r@tucson.socialOP
      link
      fedilink
      English
      arrow-up
      18
      ·
      1 year ago

      Personally, I find it reasonably amusing that defending an open source, arguably collectivist project requires appeals to individualism.

      “You can build it” “Just defederate” “It’s the instance owner’s responsibility” “You can do X for your instance, its in your control”

      Like, which is it? Is this a collective undertaking by a community of multiple stakeholders or is this the Dev’s individual project and they don’t have to listen to anyone?

      • DrWeevilJammer@lm.rdbt.no
        link
        fedilink
        English
        arrow-up
        7
        ·
        1 year ago

        Is this a collective undertaking by a community of multiple stakeholders or is this the Dev’s individual project and they don’t have to listen to anyone?

        Devs, especially extremely busy ones “listen” via pull requests. Instead of badgering the devs, put together some devs of your own, get some code working, and submit it as a PR.

        If they don’t accept it, you now have code that does what you want, and it would be easy to create your own fork.

        • th3raid0r@tucson.socialOP
          link
          fedilink
          English
          arrow-up
          15
          ·
          1 year ago

          Yeah, and this would work fine for new features. But for removing existing features that alter the entire ecosystem regardless if you upgrade or not? This isn’t at all the same, and casting it as such isn’t honest.

          I feel like folks keep making this a technical merit discussion when that’s not at all what it is. A better technical solution is required, I agree. I’m not even disagreeing that captcha can be bypassed - but so can a lock, or a door, or any security feature really given a sufficiently intelligent threat.

          But so far the captcha has already made some difference in what instances have spam account problems and those that don’t. To argue that it isn’t perfect is a logical fallacy that’s making my head hurt. Shall we get rid of door locks because they can be picked? Should we get rid of garage doors entirely with the new hacking devices available - obviously the security isn’t perfect so why have it at all?

          Since when did perfect become the enemy of good? We had a good solution… And now we’re throwing it out of a better one, fine! But leave the good one in place until then.

    • Freeman@lemmy.pub
      link
      fedilink
      English
      arrow-up
      9
      ·
      1 year ago

      I’ve already seen proposed solutions which involve scraping for all instances with less than a certain number of users to defederate on principle (inactive, too many users/post ratio). We’re fighting spam bots right now, who are targeting instances which don’t have captcha enabled.

      There are folks that are running their own instances as well, as single user instances or are working to get the federation to the point to open it up in anticipation for a larger flood. That doesnt make us spammers at all.

      The questions of how to handle it are legitimate. In the end I feel the “fediverse” will need some user only instances (that is instances that just host users and not loads of communities) to help with the load and scaling issues MANY are seeing. Beehaw seems to have handled the influx to date the best, others like lemmy.ml and lemmy.world seem to have service level impacts that I can only really assume is due to scaling and load. And thats supposed to be the entire point right?

  • Saik0@lemmy.saik0.com
    link
    fedilink
    English
    arrow-up
    39
    ·
    1 year ago

    You ALL have a responsibility to communicate back to lemmy devs to try to stop it.

    No I don’t. Stop trying to brigade people to an issue. If you have an issue with it… Fork the lemmy UI code and make your own. Or stay on pre 0.18 code.

    It’s one thing to bring awareness to the issue. It’s another to demand that I take action on something that’s not only a non-issue for me (and likely many other admins of instances) but that the devs don’t have to support. You’re not paying them… you’re not their mother. You don’t get to force them to do anything they don’t want to do.

    Honestly the captchas that lemmy uses are terrible anyway. https://addons.mozilla.org/en-US/firefox/addon/2captcha-solver/ You can even solve them yourself as a browser extension… There’s no point to them in today’s world.

    • Speff@melly.0x-ia.moe
      link
      fedilink
      English
      arrow-up
      14
      ·
      1 year ago

      You’re not paying them… you’re not their mother. You don’t get to force them to do anything they don’t want to do.

      I’m trying to think of what it would be like if one of my projects had a defined roadmap and then I suddenly get hundred of messages a day telling me I have to do something. lol, no. Maybe if I was actually being paid well for the project.

    • Rentlar@beehaw.org
      link
      fedilink
      English
      arrow-up
      8
      ·
      edit-2
      1 year ago

      Exactly, instance admins that want to keep CAPTCHA have two good options here:

      1. Stay on 0.17.x until 0.18.y drops that re-implements CAPTCHA satisfactorily
      2. Fork and modify lemmy to version 0.18-captcha, undo the commit removing the old Captcha code.

      I totally get the project maintainers are stubborn but no one has a “responsibility to stop the devs from doing it”. It reeks of open-source entitlement.

      • Troy@lemmy.ca
        link
        fedilink
        English
        arrow-up
        4
        ·
        1 year ago

        It reeks of open-source entitlement.

        I used to contribute to a very large open source project. One day I posted a blog about our project not really needing users, except that some small portion of users turned into developers. The users were incensed. “How can you not need us?” It was a “The customer is always right” mindset, except that doesn’t work with open source when they’re using something they downloaded for free.

        That said, Lemmy might be a special exception, because it’s goal is to have a lot of users – network effects are important to the health and longevity of social media platforms. So Lemmy might actually need the users to be a healthy project. Unfortunately, this will create a bunch of entitled users in the process :/

        • DrWeevilJammer@lm.rdbt.no
          link
          fedilink
          English
          arrow-up
          2
          ·
          1 year ago

          “The customer is always right” mindset, except that doesn’t work with open source when they’re using something they downloaded for free.

          You’ve put your finger on the thing that was bothering me about the tone of the original post - it’s very similar to a Nextdoor post.

      • th3raid0r@tucson.socialOP
        link
        fedilink
        English
        arrow-up
        3
        ·
        1 year ago

        You won’t see me making call to action posts for undelivered features or other small-fry items. I’m a dev, I get it.

        But there are always times were vulnerabilities come up and a dev might not otherwise know that it’s being exploited. It’s one thing to have a feature to fix that vulnerability and get to it as part of your own priority list. It’s another when that vulnerability is actively impacting the people using the software - that’s when getting vocal about an issue is appropriate to help me alter my priorities, IMO.

        • Rentlar@beehaw.org
          link
          fedilink
          English
          arrow-up
          5
          ·
          1 year ago

          Your concerns about security of the application and community are valid. I get that this is essentially a vulnerability that should be mitigated and fixed. Raising awareness of it is fine.

          Where I take issue, I suppose you didn’t entirely intend this, is that our responsibility is to put pressure on the main developers to fix the issue before the 0.18 release and dictate their priorities for them.

          I would rather we discuss workarounds, mitigation steps in the interim, assist in solving the issues through Pull Requests and discussion on the issues page and forums. I just think it’s a bad idea to point blaming fingers at devs for being slow to respond, or badger them to make these changes, when they are volunteering their own time to share Lemmy with us (some also maintaining Jerboa and Lemmy UI at the same time)

          With the way the licensing is, I would rather the project be forked by someone that would want to fix the issue. The repo maintainers are entitled to set their own priorities, just like Lemmy instance admins are allowed to determine how they run the server.

          • th3raid0r@tucson.socialOP
            link
            fedilink
            English
            arrow-up
            1
            ·
            edit-2
            1 year ago

            Thank you for the measured take on this.

            You are correct, I don’t intend to pressure or cause harm! But I certainly see the results, and it is indeed pressure. As another commenter pointed out, there are many instance admins who work a bit closer to the team on the Matrix chatrooms and that’s their preferred method of communication. Now that I know this, I’ll let things cool down and join myself. I definitely intend to contribute where I can in the codebase, and I wouldn’t dream of escalating to public pressure for smaller concerns.

            However, I have a slight, and perhaps pedantic disagreement about making changes. In this case, the request was for not making a change. If it weren’t for the fact that the feature was already ripped out it would be as simple as not removing it (or in this case re-working it a bit). I understand that it isn’t the current reality, and that it required work to revert - and if not for a ton of spambots, I think It would’ve been easier to adapt.

            Ultimately it will take time to discuss workarounds and help others implement them, and the deadline is ultimately the arrival of the version that drops the older captcha (or was, in this case - it’s getting merged back in as we speak - might even be done now). With that reality, I had a sense that this could be an existential problem for the early Threadiverse.

            I definitely didn’t intend to suggest that the Devs were in any way at fault here. I read the github issues enough to come with the takeaway was that the feedback they were receiving seemed to be “Admins and devs alike are okay moving forward and opinions to the contrary are minimal, let’s move forward”. It was definitely intended to be a way to communicate using raw numbers (but not harassment). I’d like to think I’m fairly pragmatic in that if it IS working for folks, then that is a contrary opinion, and that it was missing.

            Where I definitely failed was my overly emotional messaging. It’s certainly not an excuse, but my recent autism diagnosis does at least help explain why I have an extremely strong sense of justice and can sometimes react in ways that are less than productive in some ways.

            As for the licensing, I agree! I’m talking to some good friends of mine because I want to take my instance WAY further than most others - goal is a non-profit that answers to Tucsonans and residents of larger Pima county rather than someone not in the community. There’s just a lot of features this concept would need that it might diverge so much from the Lemmy vision that it needs to be something new - and hopefully a template for hyper-local social networks that can take on Nextdoor.

            • Rentlar@beehaw.org
              link
              fedilink
              English
              arrow-up
              1
              ·
              1 year ago

              I can see better where our disagreement is, and I appreciate you being reasonable about it as well. Thank you for that.

              Sounds like you have some great plans coming with your Tucson social project. All the best!

    • Zetaphor@zemmy.cc
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 year ago

      They’ve now said they’re open to a PR that implements captchas in 0.18, which will require new work since it’s not just a matter of reverting the removal from 0.17. I look forward to seeing OP’s submission.

      • th3raid0r@tucson.socialOP
        link
        fedilink
        English
        arrow-up
        3
        ·
        1 year ago

        Looks like someone already opened a PR to roll back to a retrofitted solution (I had to wait until the weekend before I could find the time to work on this).

        The devs are willing to accept a retro-fitted captcha (rather than just mCaptcha) in time for v0.18 and they communicated as such about 9 hours ago (for me). So for me, my push for visibility is complete unless they block the incoming PR for whatever reason. The devs have been made aware that this is contentious and the community could be impacted negatively and they see the need for it.

        For me, that indicates that the Lemmy devs will listen to key, important issues, that impact the health of the larger fediverse as long as the community is clear about what the largest issues actually are.

        A lot of folks here characterized me as someone wanting to “brigade”, but that’s not quite true. I just know that sometimes developers don’t know what’s going on with admins unless the admins are loud, clear, and coordinated. That doesn’t mean that I was asking folks to “force” the devs to do anything or be abusive, just that enough feedback might convince them to see things from a different perspective than a perfect technical solution.

        • Zetaphor@zemmy.cc
          link
          fedilink
          English
          arrow-up
          3
          ·
          1 year ago

          A lot of folks here characterized me as someone wanting to “brigade”, but that’s not quite true. I just know that sometimes developers don’t know what’s going on with admins unless the admins are loud, clear, and coordinated.

          The language of your post was quite hostile and painted (and continues to paint) the developers as being out of touch with instance admins. The instance admins are already “loud, clear and coordinated”, and are working in full communication with the maintainers.

          …and I find myself really ticked off at other Admin’s abdication of duty when it comes to engaging with the developers.

          The majority of PR’s coming into the project are coming from instance admins seeking to solve their personal pain points.

          Both the issue and the PR you’re referring to were created by ruud, the admin of the single largest Lemmy instance, lemmy.world. Both your signaling to this issue and the outcry it attempted to rally were completely unnecessary.

          • th3raid0r@tucson.socialOP
            link
            fedilink
            English
            arrow-up
            1
            ·
            1 year ago

            The language of your post was quite hostile and painted (and continues to paint) the developers as being out of touch with instance admins. The instance admins are already “loud, clear and coordinated”, and are working in full communication with the maintainers.

            Right now the instance admins that I’m working with are largely independent with only a couple of outliers. The newer instances that have just joined the fediverse didn’t really echo back their concerns. So while you’re statement might be true (I dunno, I don’t see any coordination, and it’s not always clear what admin concerns are important.) the rapid growth has brought even more stakeholders and admins to the fediverse. Some far less technical than others. I’m going to need more proof of deeper coordination, because as it stands many Admins say “Devs are tankies” and refuse to federate with the maintainer’s instance, let alone contribute code or money.

            The majority of PR’s coming into the project are coming from instance admins seeking to solve their personal pain points. Both the issue and the PR you’re referring to were created by ruud…

            This is a new phenomenon, the total lines of code written by the primary devs are still much larger than any other combination of PRs. I don’t envy the position of having to sort through thousands upon thousands of PRs that may or may not coincide to the project’s vision or code quality standards. Rolling back to a known prior state is almost always lower effort than minting a fresh new implementation.

            Also, ruud did not create the PR I’m referring to, that honor goes to TKillFree. Heck, why do you think I’m attacking the author here rather than trying to bring more weight to his Github issue? It’s because of ruud that I even know what’s going on - and the instance admins I know were pretty clueless about the pending change.

            I’ll grant you that my tone and signalling needs work, but I do think that an attempt to rally more folks did indeed influence the solutions that the maintainers were willing to accept. From “New, better implementation only - remove the existing flawed one now” to “Okay we can keep the flawed method, but we need an enhanced version and soon”.

            At this point its hard to tell because we don’t live in a universe where I didn’t make that post to compare. Maybe you’re right and this would’ve all shaken out eventually.

            • Zetaphor@zemmy.cc
              link
              fedilink
              English
              arrow-up
              1
              ·
              1 year ago

              Right now the instance admins that I’m working with are largely independent with only a couple of outliers. The newer instances that have just joined the fediverse didn’t really echo back their concerns. So while you’re statement might be true (I dunno, I don’t see any coordination, and it’s not always clear what admin concerns are important.) the rapid growth has brought even more stakeholders and admins to the fediverse.

              Are you in the Matrix server? This is where the coordination is happening between both maintainers and the development community, as well as playing out across Github issues.

              I’m going to need more proof of deeper coordination, because as it stands many Admins say “Devs are tankies” and refuse to federate with the maintainer’s instance, let alone contribute code or money.

              You just said you’re only interacting with a small group of independent admins, but now you’re making a conflated statement of “many Admins”. They have a right to their opinion, but they can’t also expect the maintainers and devs/admins who are contributing code to listen to their demands when they’re bringing nothing to the table except complaints and personal attacks.

              You have the choice to either support with code, support with money, or be happy with what you got for free and if you don’t like something you can make changes to it yourself.

              The only reason you got what you wanted in the end was because someone else put in the work to make it happen, which I’m certain would have happened regardless of your post because it was already being raised both in the Matrix channel amongst other admins as well as by ruud.

              • th3raid0r@tucson.socialOP
                link
                fedilink
                English
                arrow-up
                1
                ·
                1 year ago

                Guess I best get over there then. Sounds like a place to voice my concerns without resorting to public appeals.

                You just said you’re only interacting with a small group of independent admins, but now you’re making a conflated statement of “many Admins”.

                I can be working with a small set of independent instance admins (brought together by a newer instance and discussions mostly through discord) and I’ve helped them test a few things and our little discord meta-community is already constructing new features, auto-posting bots of different types (RSS feeds, even posts, etc), and a few other things.

                However, this is different from “Most Admins” where my interactions are largely based in the meta/support channels for other instances. This is a much more confusing population to me since many were exposed to the entire “Lemmy is for Authoritarian Communists” that was making the rounds on reddit. It’s resulted in a newer cohort of Admins that aren’t nearly as friendly to the development team.

                The only reason you got what you wanted in the end was because someone else put in the work to make it happen

                Nah, I would’ve made the change myself, but it wouldn’t do a darn thing because it depends on the inherent security of less technical admins. This project is as much impacted by individual decisions as they are collective ones.

                And until the maintainers changed their mind, they likely wouldn’t have allowed a resurrection of the old Captcha anyways - so your point about another person “doing the work” only was really possible once the maintainers communicated that it was acceptable. Because, as stated in my previous point, an individual instance with this change (reverting captcha) doesn’t protect them from instances that don’t.

                This all points back to my original point which revolves around new admins understanding the importance of engaging the maintainers and making themselves heard. The fact that people who already do this took offence to my post is a little bizarre because I’m clearly not talking about the people who haven’t been communicating.

                Sure, those who’ve been with the Fediverse for a bit are familiar with Matrix and how to use it to communicate back to the core developers. But the new influx of instances and their admins either A - don’t know where to go, B - don’t care, or C - are so ideologically opposed to the rumors they want nothing to do with them.

  • Steve@compuverse.uk
    link
    fedilink
    English
    arrow-up
    33
    ·
    edit-2
    1 year ago

    There are other options.

    I’m just a hobbyist, but I have built a couple websites with a few hundred users.

    A stupidly simple and effective option I’ve been using for several years now, is adding a dummy field to the application form. If you add an address field, and hide it with CSS, users won’t see it and leave it blank. Bots on the other hand will see it and fill it in, because they always fill in everything. So any application that has an address can be automatically dropped. Or at least set aside for manual review.

    I don’t know how long such a simple trick will work on larger sites. But other options are possible.

    • th3raid0r@tucson.socialOP
      link
      fedilink
      English
      arrow-up
      9
      ·
      1 year ago

      Fun fact, I purposefully goaded the bots into attacking my instance.

      Turns out they aren’t even using the web form, they’re going straight to the register api endpoint with python. The api endpoint lives at a different place from the signup page and putting a captcha in front of that page was useless in stopping the bots. Now, we can’t just challenge requests going to the API endpoint since it’s not an interactive session - it would break registration for normal users as well.

      The in-built captcha was part of the API form in a way that prevented this attack where the standard Cloudflare rules are either too weak (providing no protection) or too strong (breaking functionality).

      In my case I had to create some special rules to exclude python clients and other bots while making sure to keep valid browser attempts working. It was kind of a pain, actually. There’s a lot of Lemmy that seems to trip the optional OWASP managed rules so there’s a lot of “artisanally crafted” exclusions to keep the site functional.

      Anyways, I guess my point is form interaction is just one way to spam sites, but this particular attacker is using the backend API and forgoing the sign-up page entirely. Hidden fields wouldn’t be useful here, IMO.

    • bionicjoey@lemmy.ca
      link
      fedilink
      English
      arrow-up
      9
      ·
      1 year ago

      Couldn’t the bots just be programmed to not fill out that field? Or not fill out any field flagged as hidden?

      • Steve@compuverse.uk
        link
        fedilink
        English
        arrow-up
        13
        ·
        1 year ago

        You’d think so.

        But it’s not flagged as hidden. Instead you use CSS to set display as none. So the bot needs to do more than look at the direct HTML. It needs to fully analyze all the linked HTML, CSS, and even JavaScript files. Basically it needs to be as complex as a whole browser. It can’t be a simple script anymore. It becomes impracticality complicated for the not maker.

        • Hyperz@beehaw.org
          link
          fedilink
          English
          arrow-up
          14
          ·
          1 year ago

          This might work against very generic bots, but it won’t work against specialized bots. Those wouldn’t even need to parse the DOM, just recreate the HTTP requests.

          • Steve@compuverse.uk
            link
            fedilink
            English
            arrow-up
            6
            ·
            1 year ago

            Which is why you’d need something else for popular sites worth targeting directly. But there are more options than standard capta’s. Replacing them isn’t necessarily a bad idea.

            • Hyperz@beehaw.org
              link
              fedilink
              English
              arrow-up
              5
              ·
              1 year ago

              This is what I’m worried about. As the fediverse grows and gains popularity it will undoubtedly become worth targeting. It’s not hard to imagine it becoming a lucrative target for things like astroturfing, vote brigading etc bots. For centralized sites it’s not hard to come up with some solutions to at least minimize the problem. But when everyone can just spin up a Lemmy, Kbin, etc instance it becomes a much, much harder problem to tackle because instances can also be ran by bot farms themselves, where they have complete control over the backend and frontend as well. That’s a pretty scary scenario which I’m not sure can be “fixed”. Maybe something can be done on the ActivityPub side, I don’t know.

              • Steve@compuverse.uk
                link
                fedilink
                English
                arrow-up
                8
                ·
                1 year ago

                That’s where simple defederation happens. It’s mostly why behaww cut off lemmy.world.

                • Hyperz@beehaw.org
                  link
                  fedilink
                  English
                  arrow-up
                  2
                  ·
                  1 year ago

                  What if you have 100s or 1000s of such instances? At some point you defeat the entire purpose of the federation.

      • kool_newt@beehaw.org
        link
        fedilink
        English
        arrow-up
        7
        ·
        1 year ago

        Yes, but it would take more work specific to this problem, which if it’s not a widespread technique would be viewed as impractical.

    • jjhidalgar@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      4
      ·
      1 year ago

      When you automate a browser process like signing up, you very likely manually set in your code the fields you want to fill, not sure why a bot would do that automatically… I don’t think this would be effective at all

      • Steve@compuverse.uk
        link
        fedilink
        English
        arrow-up
        4
        ·
        1 year ago

        The bots for the most part are generic. They fill in all fields with randomly generated nonsense mostly. If the site is large enough you could make a bespoke script, which is why I’m not sure how well it will scale to large sites.

        But that’s only the simplest option. Annother I’ve see is using a collection of movie posters, you have the user pick the title from 5 or 6 options. There are lots of simple ways to defeat bots of all kinds.

    • Azure@beehaw.org
      link
      fedilink
      English
      arrow-up
      3
      ·
      1 year ago

      Thanks for sharing that tip, I’m working with someone doing a small instance and we aren’t for sure we want to be allowing applications, but if we do this is good to think about!

  • fragmentcity@lemm.ee
    link
    fedilink
    English
    arrow-up
    26
    ·
    1 year ago

    Despite what you’re implying, the devs have no duty to fix admin-reported problems using admin-dictated solutions.

    They have already said they would accept a PR adding support for captchas. Someone will undoubtedly do this before long.

    Until then, why the urgency? What is it that’s preventing you from keeping your instance on 0.17?

    • th3raid0r@tucson.socialOP
      link
      fedilink
      English
      arrow-up
      10
      ·
      1 year ago

      I disagree, once your open source project “sprouts wings” you enter an unspoken power battle. If enough of the community disagrees with something the chance of a successful fork grows. Once a project is forked away, you no longer have any control at all.

      Also, even if I don’t upgrade to v0.18, I have to live in a fediverse that have other instances that WILL, and they might pose a problem with increased spam.

      • Dusty@lemmy.dustybeer.com
        link
        fedilink
        English
        arrow-up
        12
        ·
        edit-2
        1 year ago

        I disagree, once your open source project “sprouts wings” you enter an unspoken power battle

        You’ve seen Hackers one too many times. Again you can run your instance however you want, and can defederate from instances that don’t implement things they way you are demanding they should, but you do not dictate how others (or the developers) run things.

        The beauty of open source is you can always fork your own. The beauty of federation is you can block whoever you want or whatever instance you want.

        Other than that, you have no right to demand anything of anyone.

        • th3raid0r@tucson.socialOP
          link
          fedilink
          English
          arrow-up
          11
          ·
          1 year ago

          No, I was around when SysV Init was “replaced” by Systemd and how that impacted the Debian project (and other distros).

          But you know what, sure, let’s stick to your bad faith, insulting interpretation, after all it is more becoming of an internet troll. I’m sure it’ll get you lots of updoots from similarly trollish individuals.

          Personally, I believe in something called collective responsibility, and that does including expecting community members to do their fair share. But it sounds like you envision federations as mini fiefdoms.

        • averagedrunk@lemmy.ml
          link
          fedilink
          English
          arrow-up
          2
          ·
          1 year ago

          I’m not part of this conversation, I am not a mod, I am not an admin, and I’m not necessarily informed enough to make any determination on who is right and wrong. However,

          You’ve seen Hackers one too many times.

          There’s no such thing.

      • Speff@melly.0x-ia.moe
        link
        fedilink
        English
        arrow-up
        10
        ·
        edit-2
        1 year ago

        … once again, the devs already said they would accept a PR with mCapchas. I don’t see why any capable dev would fork a project rather than just contribute code. The community can disagree all they want - it takes actual programmers to split.

        And if other instances start becoming spambots, just defederate.

      • fragmentcity@lemm.ee
        link
        fedilink
        English
        arrow-up
        8
        ·
        1 year ago

        Also, even if I don’t upgrade to v0.18, I have to live in a fediverse that have other instances that WILL, and they might pose a problem with increased spam.

        A fork avoids this problem how?

        I disagree, once your open source project “sprouts wings” you enter an unspoken power battle. If enough of the community disagrees with something the chance of a successful fork grows. Once a project is forked away, you no longer have any control at all.

        Who’s writing the code for the fork? If you see them, can you ask them to just submit the PR that the devs said they’ll approve?

        • th3raid0r@tucson.socialOP
          link
          fedilink
          English
          arrow-up
          5
          ·
          1 year ago

          That assumes that the fork would be mCaptcha rather than a simple reversion to the existing captcha. But yeah, the fork would initially be a roll back until mCaptcha is implemented either in our own or in the base repo.

      • Spzi@lemmy.click
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 year ago

        Once a project is forked away, you no longer have any control at all.

        What does that mean in the context of lemmy’s license? As I understand it, everyone is allowed to fork it away, but not allowed to change the license. Which allows everyone to fork it further away or back.

        I don’t understand what control means in this context. Isn’t it a thing people can just modify and use, now and for all future?

        • th3raid0r@tucson.socialOP
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 year ago

          That’s a bit decontextualized, but the idea is that other than the license terms ensuring that derivatives are also open source, there is also a power of community consensus and popular appeal. Your project will go further and get more improvements if it is popular and used by other developers. It’s less about forking having actual power, but what happens when folks feel they must fork because of a core issue with something the original project did that might take a while to be resolved. It can create a larger group of people in the latter group and thus make a fork to garner more interest than the original project.

      • Suppoze@beehaw.org
        link
        fedilink
        English
        arrow-up
        0
        ·
        1 year ago

        So, do you think we need to step up to the developers to implement captcha or give way to the community and support a fork with better anty-spam measures?

        • th3raid0r@tucson.socialOP
          link
          fedilink
          English
          arrow-up
          3
          ·
          1 year ago

          I’m already in talks with some other admins about a potential fork. Initially we’d just roll back ONLY the captcha change, then work on a better implementation and roll it out in a way that doesn’t leave instances exposed.

          It would be seamless for most users since it’s essentially the same thing as before, just with the Captcha code still included.

          • Suppoze@beehaw.org
            link
            fedilink
            English
            arrow-up
            1
            ·
            edit-2
            1 year ago

            Sounds good, thank you for your efforts! I think the decision is bad for the current state of the lemmyverse, we need some roadblocks for spam bots.

            I think forks and OG projects can live side by side, even more so, they can have a symbiotic relationship. The beauty of open source that we can learn from each other.

  • Zetaphor@zemmy.cc
    link
    fedilink
    English
    arrow-up
    25
    ·
    1 year ago

    Nutomic has said they’re open to restoring captchas, but it will require a fair amount of work to bring the 0.17 implementation into 0.18, which the currently don’t have the bandwidth to implement.

    They’ve also said they’re open to PR’s, so if someone really wants this feature they can open a PR for inclusion in the 0.18 release

    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.

    I sure hope you’re supporting them financially considering the demands you’re making that require their time and labor.

    • DrWeevilJammer@lm.rdbt.no
      link
      fedilink
      English
      arrow-up
      10
      ·
      1 year ago

      Someone has already submitted a PR with the changes the dev recommended. The captcha stuff is in a new db table instead of in-memory at the websocket server.

      However, from one of the devs:

      One note, is that captchas (and all signup blocking methods) being optional, it still won’t prevent people from creating bot-only instances. The only effective way being to block them, or switch to allow-only federation.

      Once people discover the lemmy-bots that have been made that can bypass the previous captcha method, it also won’t help (unless a new captcha method like the suggested ones above are implemented).

      The root of the issue seems to be that they’ve removed websockets, for the following reasons:

      Huge burden to maintain, both on the server and in lemmy-ui. Possible memory leaks. Not scalable.

      I can understand them wanting to make their lives a bit easier (see "huge burden to maintain) - Lemmy has exploded recently (see “not scalable”) and there are far bigger issues to fix, and an even larger number of bad actors (see “possible memory leaks”) who have learned about Lemmy at the same time as everyone else and want to exploit or break it.

      • rog
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        Blocking bot instances is fine, im more concerned about small instances getting over run and then blocked because the admin couldnt keep on top of it.

        The more admin tools the better IMO.

        There is definitely some admin responsibility, and there are other ways to try and minimise bots on an instance, and no doubt there is some bandwidth and technical limitations, its just a shame to lose such a basic and widely adopted tool

  • Dusty@lemmy.dustybeer.com
    link
    fedilink
    English
    arrow-up
    23
    ·
    1 year ago

    I find myself really ticked off at other Admin’s abdication of duty when it comes to engaging with the developers.

    Abdication of duty? Seriously? Do you think this is a job for people? Or that people that want a privacy related instance are “abdicating their duty” by not using captcha? Talk about hyperbole.

    Run your instance how you want. Raise an issue with the devs if you want. Throw a fit if you want. But do not attempt to tell others how to run their instances or talk for other people and their “duties” when it comes to their own servers.

  • HTTP_404_NotFound@lemmyonline.com
    link
    fedilink
    English
    arrow-up
    21
    ·
    1 year ago

    We need to make it VERY clear that Captcha is required before v0.18’s release. Not after when we’ll all be scrambling…

    You would honestly be surprised. Captcha isn’t nearly as effective at stopping spam. It only stops the lowest hanging fruit.

    Most of the “spambot” developers, started using AI-based tools a while back.

    It only helps stopping the lowest-hanging of fruit.

    Also, due to the way federation and all works… well, just remember, there are a million ways for spammers to get access currently…

    • th3raid0r@tucson.socialOP
      link
      fedilink
      English
      arrow-up
      4
      ·
      1 year ago

      Sure, I agree that the current implementation isn’t the most robust in stopping all conceivable bots. Heck, it’s quite poor as some others have pointed out.

      The reality is, though, that it is currently making a difference for many server admins, now, today.

      Let’s use a convoluted metaphor!

      It’s as if each lemmy instance has some poorly constructed umbrellas (old captcha). Now a storm has arrived (bot signups) and while the umbrella is indeed leaky, but the umbrella operator is not as wet as they would be without it. Now imagine that these magical, auto-upgrading umbrellas receive an update during this storm that removes the fabric entirely while they work on making a less leaky solution. It would be madness right? It’s not about improving on the product, that’s desired and good! It’s about making sure the old way of doing things is there until the newer solution is delivered and present.

      As a user of this “magical umbrella”, I’d be scrambling because the sudden removal of a feature that was working (albeit poorly and imperfectly) doesn’t exist at all anymore. Good thing I have a MUCH bigger umbrella that I pay $$$ for (cloudflare) to set-up in the meantime. However this huge umbrella is too big, and if I don’t cut some holes in it, it’ll be to “dark” to function. So not even this solution is perfect.

      • HTTP_404_NotFound@lemmyonline.com
        link
        fedilink
        English
        arrow-up
        5
        ·
        1 year ago

        The reality is, though, that it is currently making a difference for many server admins, now, today.

        Don’t hear me wrong- I am not advocating for its removal. I am not saying it’s not currently effective!

        Let’s be perfectly honest, it is THE most effective tool at our disposal currently.

        I am just saying, as this platform explodes in size- since the implementation for the captcha is also open source, it’s only a matter of time before it’s rendered completely inoperable- to where it only stops the easiest attacks.

  • Stumblinbear@pawb.social
    link
    fedilink
    English
    arrow-up
    19
    ·
    1 year ago

    Captchas pretty much worthless. They’re easily bypassed for basically free. You’re better off putting your instance behind Cloudflare with their captcha

    • th3raid0r@tucson.socialOP
      link
      fedilink
      English
      arrow-up
      9
      ·
      1 year ago

      Okay, so do you mind explaining why the servers onboarding the most spam users are the ones without Captchas?

      If they are so ineffective, why are they effective now?

      • Stumblinbear@pawb.social
        link
        fedilink
        English
        arrow-up
        12
        ·
        1 year ago

        Invisible captchas are about as useful as graphical ones and are significantly less annoying to the end user

        • th3raid0r@tucson.socialOP
          link
          fedilink
          English
          arrow-up
          12
          ·
          1 year ago

          Sure, so implement them in v.0.18 rather than leaving that essential feature for a future release - that’s all I personally want.

          I don’t care about the technical implementation of the Captcha, but given the current threat landscape of low effort bot attacks, removing the feature in the meantime just makes the fediverse worse off.

        • redcalcium@c.calciumlabs.com
          link
          fedilink
          English
          arrow-up
          2
          ·
          edit-2
          1 year ago

          I’m mixed about this. When applied correctly, a graphical captcha will let zero bots in, at the expense of false positives and frustrated users. On the other hand, invisible / proof-of-work captchas will let a fraction of the bots in (blocking majority but not all bots, by design), while providing better experience for legitimate users. Pick your poison basically.

          • Stumblinbear@pawb.social
            link
            fedilink
            English
            arrow-up
            8
            ·
            1 year ago

            When applied correctly, a graphical captcha will let zero bots in

            Absolutely untrue. There are services that will solve captchas for you for hundredths of a penny. It’s essentially free.

            • redcalcium@c.calciumlabs.com
              link
              fedilink
              English
              arrow-up
              2
              ·
              edit-2
              1 year ago

              Then it’s no longer only a bot, right? There are real humans working on those captcha farm. Those captcha farm also won’t solve the captcha instantly, but there will be some delays for a human to solve the captcha. You’re effectively turning graphical captcha into proof-of-work captcha this way, which will have the same effect as mCaptcha due to increased cost (in this case, captcha farm cost instead of computational cost) for the bot operator.

            • th3raid0r@tucson.socialOP
              link
              fedilink
              English
              arrow-up
              2
              ·
              1 year ago

              To be fair, “Captcha” can now mean those ai photo discrimination tests. Captcha: “Select the cats” - Me: “You call these cats?” Looks at the cartoon depictions of nightmare fuel “cats” as depicted by Picasso.

              There are still graphical tests we perform that are much harder for computers to perform - at least without near-nation-state sized financial backing.

              Yes, the ol’ scrambled captcha has been solved by multiple approaches these days, but Its not nation states I’m seeking to keep out (and I’ll be fucked if they ever did, I might add), I’m just looking to make it harder for some internet edgelord’s low effort spam attempts.