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

  • Hellfire103@sopuli.xyz
    link
    fedilink
    English
    arrow-up
    64
    arrow-down
    1
    ·
    11 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.institute
      link
      fedilink
      English
      arrow-up
      13
      ·
      11 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.world
      link
      fedilink
      English
      arrow-up
      49
      arrow-down
      1
      ·
      11 months ago

      Sidenote:

      HTTP user agents have become absolutely bonkers over the years.

      • dan@upvote.au
        link
        fedilink
        English
        arrow-up
        3
        arrow-down
        1
        ·
        11 months ago

        There’s an API called “client hits” that’s replacing user-agent. Some of the hints will require the user to provide permission for the site to use them, since they could be used for fingerprinting.

        Major browsers (Chrome and I thibk Firefox) are freezing the user-agent. The only thing that’ll be changing in user agents is the major browser version. Other parts including platform will be static. Chrome on Windows will always report itself as Windows 10 for example. https://www.chromium.org/updates/ua-reduction/

      • eek2121@lemmy.world
        link
        fedilink
        English
        arrow-up
        3
        arrow-down
        19
        ·
        11 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.

        • waigl@lemmy.world
          link
          fedilink
          English
          arrow-up
          25
          ·
          11 months ago

          There is more information in there that isn’t actually true and only supposed to trick some old web servers into treating it a certain way than there is actually correct information,

          It mentions three different browsers, only one of which is actually true, and three different rendering engines, none of which is actually what’s used.

        • dan@upvote.au
          link
          fedilink
          English
          arrow-up
          5
          ·
          edit-2
          11 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)

  • 𝒎𝒂𝒏𝒊𝒆𝒍@lemmy.ml
    link
    fedilink
    English
    arrow-up
    5
    arrow-down
    25
    ·
    11 months ago

    Yeah, as far as I know it’s not some browser chauvinism, but Firefox not supporting some multimedia protocols, that doesn’t mean it’s Firefox fault though, I’d install some chrome fork just for this kind of interactions

  • Evkob@lemmy.ca
    link
    fedilink
    English
    arrow-up
    20
    arrow-down
    1
    ·
    11 months ago

    Have you tried changing your user agent string to Chrome? I know it can sometimes sidestep these types of “errors”. It can be changed manually through about:config under general.useragent.override, or there exists plenty of addons to switch it more easily.

    • qaz@lemmy.worldOP
      link
      fedilink
      English
      arrow-up
      6
      ·
      11 months ago

      I’ve avoided changing my user agent because Firefox’s apperant market share is already so low. I’ve installed the extension and will it try it with my work container though.

  • Kallioapina@lemmy.world
    link
    fedilink
    English
    arrow-up
    174
    arrow-down
    5
    ·
    11 months ago

    Well they are just lying, it works fine with Firefox and has worked fine for years. I live in the EU though. Sucks to be american these days, I guess?

  • NoisyFlake@lemm.ee
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    5
    ·
    11 months ago

    You can use private mode or a different browser to login with multiple Teams accounts.

  • Sanctus@lemmy.world
    link
    fedilink
    English
    arrow-up
    101
    arrow-down
    1
    ·
    11 months ago

    Its cool how all these companies are allowed to just lie to you about their products functionality.

  • Eager Eagle@lemmy.world
    link
    fedilink
    English
    arrow-up
    23
    ·
    edit-2
    11 months ago

    given the love Teams receives, it not working in [ insert browser ] is definitely a feature

  • seedd@lemmy.world
    link
    fedilink
    English
    arrow-up
    4
    ·
    11 months ago

    I use floorp, it has user agent spoofing. Set it to chrome, works like a charm.

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

            Yeah thats what i thought too, ive been a librewolf user for a long time. Then i tried this, its underrated af. It just has a shitload of features.

  • Magister@lemmy.world
    link
    fedilink
    English
    arrow-up
    9
    ·
    edit-2
    11 months ago

    I’m in Linux, I had so much problem with FF and Teams that I installed Edge and Teams as a PWA, no more problem with calls and video

  • PoolloverNathan@programming.dev
    link
    fedilink
    English
    arrow-up
    13
    ·
    edit-2
    11 months ago

    Teams also doesn’t support multiple “work” accounts

    Firefox lets you have completely separate profiles with separate accounts (URL: about:profiles, it can’t be linked to for security reasons) and also an official extension to have another layer of profiles on a per-tab basis (containers).

    • Thorry84@feddit.nl
      link
      fedilink
      English
      arrow-up
      6
      ·
      edit-2
      11 months ago

      Also no idea what he is talking about, I have 4 work accounts in Teams. Ever since they rebuilt their frontend to the “New Teams” multiple accounts have been working just fine.

      In the past I had multiple Team instances as PWA for different work accounts, nowadays it’s all in one app and works pretty good.

      Not to defend Teams, it’s total shit, a lot of shit straight up doesn’t work half of the time, including important shit like notifications for new messages and content. But it has come a long way from the days including any image in chat would crash Teams for all participants. It isn’t perfect and the amount of resources it used to do what it does is awful, but compared to most modern apps it’s pretty good.

      Just don’t tell a Teams dev Microsoft Messenger did 99% of the same stuff and ran super fast on a Pentium 3 333mhz with 64MB of ram, they’ll cry and you’ll be called out for being a bully.

  • dan@upvote.au
    link
    fedilink
    English
    arrow-up
    62
    arrow-down
    2
    ·
    edit-2
    11 months ago

    This is likely legacy code. Firefox used to have a lot of issues with WebRTC, so practically all video conferencing systems blocked it. Teams probably has some “block Firefox because it doesn’t work properly” check that was written 5+ years ago and none of the current developers are even aware of its existence.

    Well-coded ones did feature detection instead of checking the user-agent, meaning they automatically started allowing Firefox as soon as it implemented all the required features.

    Feature detection is usually the way to go. If your website / webapp depends on a particular feature, check if that specific feature exists, rather than checking for particular browsers. Browser checks are still needed in some cases, for example Safari sometimes reports that it supports particular features but it really doesn’t (or they’re so buggy to the point where they’re unusable), but that’s relatively rare.

    • DacoTaco@lemmy.world
      link
      fedilink
      English
      arrow-up
      3
      ·
      11 months ago

      This is indeed the case. I use firefox daily, including for teams. I have to fake my user agent to do it, but it works. Its purely teams just saying fuck you to firefox…

    • drathvedro@lemm.ee
      link
      fedilink
      English
      arrow-up
      13
      ·
      11 months ago

      Feature detection is usually the way to go. If your website / webapp depends on a particular feature, check if that specific feature exists, rather than checking for particular browsers. Browser checks are still needed in some cases, for example Safari sometimes reports that it supports particular features but it really doesn’t (or they’re so buggy to the point where they’re unusable), but that’s relatively rare.

      This is tough to implement when the feature is present, but implemented wrong. Or, even worse, when it’s implemented right, but the most popular browser implements it wrong and almost everyone else follow suit for compatibility reasons, except for one that takes the stance of following standards. I know safari is notorious for this, think pale moon had those issues, too, and there are still echoes from the past from pre-chrome internet explorer, thank god it’s finally dead.

        • dan@upvote.au
          link
          fedilink
          English
          arrow-up
          1
          arrow-down
          3
          ·
          11 months ago

          At least Chrome is mostly standards-compliant and doesn’t do anything too weirdly. I’d say Safari is the new IE - lots of weird bugs that no other browser has, and sometimes you need hacks specific to Safari.

          • Monument@lemmy.sdf.org
            link
            fedilink
            English
            arrow-up
            2
            ·
            11 months ago

            That’s fair. I meant that more in terms of using market dominance to shape the browser market, and not in entirely good ways.

            I’ll rue the day that every website insists it only works with Chrome because of some user-privacy degrading feature that Google insists is a core web technology.

    • hemko@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      4
      ·
      edit-2
      11 months ago

      Teams used to have more features on Firefox. Microsoft has intentionally started stripping off shit to move people to edgium

  • pedroapero@lemmy.ml
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    1
    ·
    11 months ago

    It’s never worked on FF for me. I installed Chromium just to be able to log into several Teams accounts. And tabs are still not working. Classic Microsoft mess.