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

  • bouh@lemmy.world
    link
    fedilink
    English
    arrow-up
    32
    arrow-down
    1
    ·
    5 months ago

    MS purposefully not respecting the standards for its softwares to only work on their own browsers is a feature since they made Internet Explorer. It’s an industrial strategy to trap the users into their own tools. It’s to the point they don’t respect even their own standards in the case of docx for example so that there is no easy interoperability with libreoffice.

    • hamid@lemmy.world
      link
      fedilink
      English
      arrow-up
      3
      ·
      5 months ago

      I agree with you that the real reason for it is EEE but their justification for it is that for enterprise and corporate customers, the only ones they care about, they can’t control Firefox in the same was as they can Edge or Chrome with the Microsoft Account add in which allows the MDM agents like InTune to apply DRM. Their primary concern (so they claim) is the enterprise administrators ability to control the computer, provide settings, configure defender xdr security and all the other bs products they sell.

    • Katana314@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      arrow-down
      1
      ·
      5 months ago

      That remark, while truthful a long time ago, didn’t really apply during the later periods of IE, or the early periods of Edge before it became a webkit clone. When it needed to win back users, there was a lot of focus on standardization, meaning that when I worked on sites, I tested them through MDN Docs, and in Firefox and IE first, made sure my solutions were not using any -webkit- nonsense, and then they would be fine on other browsers. Anytime I did find IE bugs late in its life, it was usually because some other browser coder was not correctly following standards.