this post was submitted on 18 Jan 2024
362 points (97.6% liked)

Firefox

17602 readers
290 users here now

A place to discuss the news and latest developments on the open-source browser Firefox

founded 4 years ago
MODERATORS
 

cross-posted from: https://lemmy.world/post/10829773

Teams apparently can't call when using Firefox

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

all 30 comments
sorted by: hot top controversial new old
[–] takeda@lemmy.world 95 points 8 months ago (1 children)

Exactly, this is how Microsoft operates. This time they gave an excuse they still allow plenty of other browsers (with the same engine). Google loves it, because it hurts Firefox and they can say they are not responsible for 3rd parties blocking sites.

I wouldn't be surprised if this is coordinated based on lessons learned with IE.

[–] jmcs@discuss.tchncs.de 18 points 8 months ago (2 children)

As a bonus it gives companies that want to use or allow Firefox a reason to use Google Workspace because Google Meet works perfectly on Firefox.

[–] JackGreenEarth@lemm.ee 3 points 8 months ago

If they want to use Firefox, wouldn't they also want to use a FOSS meeting software?

My org actually uses both, as well as Slack. We use:

  • Teams - most meetings
  • Meet - some meetings w/ outside orgs
  • Slack - 1:1 and small group, impromptu meetings

I use the Teams and Slack apps, and Meet in the web.

[–] KpntAutismus@lemmy.world 74 points 8 months ago (2 children)

people using user agent switcher so they can use bullshit like teams probably introduces errors into the statistics so microsoft can claim most users use chromium anyway.

[–] 65gmexl3@lemmy.world 39 points 8 months ago

They're required to use a garbage app, but they're also not willing to drop their favorite browser. No choice but to compromise.

[–] Dehydrated@lemmy.world 9 points 8 months ago

A good user agent switcher should support per-site settings.

[–] ISOmorph@feddit.de 71 points 8 months ago (2 children)

Does it work if you change your user agent?

[–] Floshie@lemmy.blahaj.zone 63 points 8 months ago (1 children)

Yep it does, funnily enough

[–] CallumWells@lemmy.ml 7 points 8 months ago (2 children)

So it's just an arbitrary restriction as a "fΓΌck you" to people using FF

[–] Floshie@lemmy.blahaj.zone 2 points 8 months ago

Not the first time I've had that sadly

[–] navi@lemmy.tespia.org 1 points 8 months ago

Could be using experimental APIs Chrome has, there are plenty of them.

This is the issue with one giant browser. They can make the "spec" what ever they want without any consideration of other browsers.

[–] some_guy@lemmy.sdf.org 65 points 8 months ago (1 children)

Teams is shit in any form. Slowest app to launch on my M2 MacBook Pro, but it’s what we use where I work so I have no choice.

[–] DacoTaco@lemmy.world 5 points 8 months ago

Should be better with v2, normally. V1 uses electron and an old angular version which both were slow as fuck and used a shit ton of resources. I also think electron doesnt support the arm platform yet? (citation needed).

Anyway, v2 uses react and a better webapp engine to run as an app so it should be faster. Not surprised if it still ran as shit though haha

[–] Neikon@lemmy.world 21 points 8 months ago (1 children)

They don't support Linux applications, they don't support the main Linux browser. They don't want you to use Linux

[–] Tabula_stercore@lemmy.world 7 points 8 months ago (1 children)
[–] jackpot@lemmy.ml 2 points 8 months ago

Extend and Extinguish. Why move when you can just usr our WSL? Get used to it, get reliant on it. Then we'll fuck you over.

[–] Aradia@lemmy.ml 11 points 8 months ago

Teams is very bugged...

[–] TropicalDingdong@lemmy.world 7 points 8 months ago
[–] LodeMike@lemmy.today 4 points 8 months ago

I do teams meetings all the time.