Started to get this message when accessing Reddit. I use LibreWolf as a browser, which does indeed provide a more generic user agent to combat fingerprinting, but nothing out of the ordinary either (Mozilla/5.0 (Windows NT 10.0; rv:109.0) Gecko/20100101 Firefox/119.0). Anyone else experiencing this?

Edit: seems to have resolved itself. Thanks for confirming I wasn’t doing anything wrong. Let’s hope this isn’t some new algorithm to test if for insufficient fingerprinting so Reddit can kick ad-resistant users.

  • ZeroCool@feddit.ch
    link
    fedilink
    English
    arrow-up
    88
    arrow-down
    1
    ·
    1 year ago

    https://www.reddit.com/r/ModSupport/comments/17vbyr8/whoa_there_pardner_error_message/

    Text:

    Hey all!

    It looks like most of you had difficulty reaching the site for about 5 minutes, but those issues should have subsided.

    During that time, you may have been shown an incorrect error message that read:

    Whoa there, pardner! reddit's awesome and all, but you may have a bit of a problem.
    
    Make sure your User-Agent is not empty, is something unique and descriptive and try again. if you're supplying an alternate User-Agent string, try changing back to default as that can sometimes result in a block.
    

    To share some additional context on what happened - we pushed a bad code change in our tooling that resulted in a significant amount of users getting blocked without doing anything wrong. So if you happened to see that error message within the last hour, don’t fret! We’ve reverted the code change that caused this error and things should be back to normal very soon if they aren’t already.

    • brax@sh.itjust.works
      link
      fedilink
      arrow-up
      54
      arrow-down
      3
      ·
      1 year ago

      “bad code change” describes pretty much every vide change they’ve done over the past 7ish years lol

        • Stumblinbear@pawb.social
          link
          fedilink
          arrow-up
          2
          arrow-down
          4
          ·
          1 year ago

          Or it was just a bug. You know, the thing that happens literally all the time in every codebase in the world

          • Flying Squid@lemmy.world
            link
            fedilink
            arrow-up
            4
            arrow-down
            2
            ·
            1 year ago

            Maybe, but this is exactly the sort of thing I would expect them to do a test run for. They are desperate to stop ad-blocking.

            • Stumblinbear@pawb.social
              link
              fedilink
              arrow-up
              1
              ·
              edit-2
              1 year ago

              Tests and QA don’t catch everything. From what I can tell this affects a small percent of users, so it’s very likely that it slipped through any testing that was done if that’s the case