- cross-posted to:
- mildlyinfuriating
- cross-posted to:
- mildlyinfuriating
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. 🤷
You must log in or register to comment.
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.
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.
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.
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.
They’re required to use a garbage app, but they’re also not willing to drop their favorite browser. No choice but to compromise.
A good user agent switcher should support per-site settings.
Right, but that doesn’t change the fact that the site you use it on can gather statistics to show what the most popular browser is.
Well yeah, but it’s limited to Microsoft Teams. All other websites will still see it as Firefox. Otherwise you would need to install some Chromium garbage on your system and use it for Teams. And guess what, that way, you would also show up as a Chromium user.
Does it work if you change your user agent?
Yep it does, funnily enough
So it’s just an arbitrary restriction as a “fück you” to people using FF
Not the first time I’ve had that sadly
@CallumWells @Floshie :blobangery:
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.
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.
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
Still slow, at least on my Intel Mac.
And electron does support ARM, or at least it runs on M1 Macbooks. We use Teams extensively in our org, and we have a mix of M1 and Intel Macs, and we also have an electron app we maintain (and our QA uses an M1 Mac for testing).
It running on m1 macbooks is no sign of arm support as macos has a translation layer to translate x86/x64 to arm64. However, electron apparently has arm64 support on macos since version 10.
Electron is basically chrome and it shows lol.It literally embeds Chrome in an application layer with a Node.js layer on top for application logic. So unless Electron maintainers royally screw it up (or a particular app embeds non-JS code), it should work on all platforms Chrome supports.
Teams is absolute garbage in firefox. I just opted to use teams for linux from flathub cause the web version on firefox was nearly umusable
Frankly it is garbage anyway. We currently use it in my company and there’s no other option and I think teams is the worst conferencing app so far.
100%. When job hunting, Teams is a con/negative for that employer.
I’ve been open minded to it but got my first impression of it in the wild recently when we had a meeting with an intl supplier that uses it, and have to agree it sucked. Aside from the organiser being late, everyone else was ready to start, but other parties on supplier end could not approve our entry because they didn’t set the meeting. Apparently we could work around it if we created Microsoft accounts.within 30 seconds I started an instant Google meet and sent them a pre-approved link to join, and upon joining the call they expressed surprise about how easy that was.
You could have also tried with jitsi since it is foss and doesn’t require an account.
Yeah, just the company uses G Suite so I defaulted to the platform my boss was comfortable with. Comment not intended to promote Google products
That’s good. Better that you used this because as you said, they might be more comfortable.
How does the flathub version perform? I noticed v2 can be run in the browser, and thought to give it a whirl in edge (under Linux, since it supports sync now).
I am using the flathub version and it works fine
They don’t support Linux applications, they don’t support the main Linux browser. They don’t want you to use Linux
Except WSL
That’s so people who want/need Linux can stay on Windows.
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.
Teams is very bugged…
I do teams meetings all the time.
The issue is just for 1 on 1 phone calls, meetings seem to work fine.
Yeah, I can get into meetings with Firefox, as I did yesterday.
Huh???
