If you confront Microsoft with this, then they will say they don’t have enough resources to test “thousands” of browsers which is why they have restricted their efforts to Chromium only, while making billions of dollars in profits each year.
I’ve tried it today and yeah, 1-to-1 calls magically/unsurprisingly start working. In fact, the whole UI gets a facelift and lots of new features.
If I had to guess, I’d say Microsoft keeps around a version of their UI, which hasn’t been maintained in over a year, and serves that to anyone initiating communication with a user-agent string they don’t like.
If that’s true, that’s a massive security vulnerability. Admittedly, also unsurprising for Microsoft.
@[email protected]
Does changing user agent mitigate some of those issues?
In a just world, the fact of changing the user agent fixing the issues would make for a slam-dunk anti-trust case.
If you confront Microsoft with this, then they will say they don’t have enough resources to test “thousands” of browsers which is why they have restricted their efforts to Chromium only, while making billions of dollars in profits each year.
It really should, no doubt, but this is not a perfect world
I’ve tried it today and yeah, 1-to-1 calls magically/unsurprisingly start working. In fact, the whole UI gets a facelift and lots of new features.
If I had to guess, I’d say Microsoft keeps around a version of their UI, which hasn’t been maintained in over a year, and serves that to anyone initiating communication with a user-agent string they don’t like.
If that’s true, that’s a massive security vulnerability. Admittedly, also unsurprising for Microsoft. @[email protected]
Thanks a lot for this…time to get an extension.
Wow, that’s egregious on so many levels!
This kind of browser apartheid should be illegal