Hello, I started to experience a problem with Mull and Duolingo (and also bromite) that started about 1 month ago.

Basically Duolingo tells me that my browser is not supported but it worked perfectly fine before. Anyone experienced this issue? I can’t find an issue on mull repo apparently about this specific issue. Dunno if it is something about resisting fingerprint but I wonder why that happens…

  • stoly@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    11 months ago

    I pretty much instantly lose respect for people who design sites to only support specific browsers. With the exception of Firefox, it’s all Chromium anyway so they don’t really need to worry about it. This isn’t like when Internet Explorer was a thing and broke web pages.

    • ErwinLottemann@feddit.de
      link
      fedilink
      arrow-up
      1
      ·
      11 months ago

      i guess it’s not about the actual site not supporting some browser. it’s usually about not wanting to deal with users that have problems with the page in some obscure browser caused by some random plugin or something but the user blaming it on the service. or because of tracking.

      • brianary@startrek.website
        link
        fedilink
        arrow-up
        0
        ·
        11 months ago

        So do feature testing, not user-agent sniffing! For Pete’s sake, it’s 2024! That’s been the best practice for decades!

        • ErwinLottemann@feddit.de
          link
          fedilink
          arrow-up
          1
          ·
          11 months ago

          that’s not the point. the user is going to open a ticket because something does not work because their browser does not support it. and it’s way easier to tell them to install ‘this browser’ than to install ‘a browser that supports a specific feature’. most of the users don’t even know what a browser is…

  • brokenlcd@feddit.it
    link
    fedilink
    arrow-up
    0
    ·
    edit-2
    11 months ago

    You can try with an extension that changes the user agent of your browser; if you use the one from either firefox or chrome for android it should work. Usually its the only thing checked by sites when identifing browsers for non telemetry reasons; if the problem persists I’m not sure what it could be