1106
Teams apparently can't call when using Firefox (lemmy.world)
submitted 2 years ago by to c/mildlyinfuriating@lemmy.world
197 comments fedilink hide all child comments
 

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

you are viewing a single comment's thread
view the rest of the comments
[–] 61 points 2 years ago (5 children)

Sidenote:

HTTP user agents have become absolutely bonkers over the years.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 10 child comments
    •
  • [–] 4 points 2 years ago (1 child)

    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/

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [+] -19 points 2 years ago (2 children)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 29 points 2 years 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.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 9 points 2 years ago* (last edited 2 years 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)

  • permalink
  • fedilink
  • source
  • parent