Teams also doesn’t support multiple “work” accounts, so I had to boot up a laptop to accept the call. 🤷

  • Hellfire103@sopuli.xyzEnglish
    0·
    8 months ago

    Try changing your user agent to a Chrome one (e.g. Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36). Works a treat!

    • redcalcium@lemmy.instituteEnglish
      0·
      8 months ago

      Feels like we’re back to 2007 again when spoofing firefox user agent to IE would fix websites not working properly, only now we spoof it to chrome instead.

    • waigl@lemmy.worldEnglish
      0·
      8 months ago

      Sidenote:

      HTTP user agents have become absolutely bonkers over the years.

      • eek2121@lemmy.worldEnglish
        0·
        8 months ago

        Not really. The example listed above is perfectly readable.

        Knowing the versions of webkit, browser version, etc. is important due to inconsistencies, new features, mossing features, and deprecated features. Sure it can be faked, but that is on the end user.

        • dan@upvote.auEnglish
          0·
          8 months ago

          Chrome doesn’t use Webkit, and the referenced Webkit version is probably 10 years old at this point. The user agent is full of stuff for backwards compatibility. That’s why it’s being deprecated in favour of a better API (client hints)