Vivaldi (@Vivaldi@vivaldi.net)
social.vivaldi.net
Attached: 1 image Many have tagged us in discussions about a specific Google extension built into Chromium browsers and asked us what we've done about it. This is a part of the Google Meets browser extension, which we bundle in order to allow Google Meets to work. This can be disabled in Settings > Privacy and Security > Google Extensions > Meets. Disabling it will break Meets. We expose this as a setting because we want you to be able to control it, and disable it if you want to. Disabling it by default would be great, but doing so would break Meets for users who are not able to understand why it’s broken, or what they need to change in order to allow it to work. Unfortunately, when websites break, either because of browser detection, or missing features, users invariably assume the browser is at fault rather than the website, and we have to make choices about what needs to be done to make websites work. We do not take these kinds of decisions lightly. We do find it very interesting that Google, who run the Chromium browser project, choose to give Meets additional information that is not given to other videoconferencing websites, and this could easily be seen to be uncompetitive behaviour. Hopefully, the EU's competition enforcement agencies can add this to their radar, and require a change in Google's Meets functionality.

Full toot:

Many have tagged us in discussions about a specific Google extension built into Chromium browsers and asked us what we’ve done about it.

This is a part of the Google Meets browser extension, which we bundle in order to allow Google Meets to work. This can be disabled in Settings > Privacy and Security > Google Extensions > Meets. Disabling it will break Meets. We expose this as a setting because we want you to be able to control it, and disable it if you want to.

Disabling it by default would be great, but doing so would break Meets for users who are not able to understand why it’s broken, or what they need to change in order to allow it to work. Unfortunately, when websites break, either because of browser detection, or missing features, users invariably assume the browser is at fault rather than the website, and we have to make choices about what needs to be done to make websites work. We do not take these kinds of decisions lightly.

We do find it very interesting that Google, who run the Chromium browser project, choose to give Meets additional information that is not given to other videoconferencing websites, and this could easily be seen to be uncompetitive behaviour. Hopefully, the EU’s competition enforcement agencies can add this to their radar, and require a change in Google’s Meets functionality.

  • narc0tic_bird@lemm.ee
    15·
    4 months ago

    I feel like most of Vivaldi’s target audience is knowledgeable enough to enable an extension that’s disabled by default. Heck, just display a notification asking whether to enable the extension when a Google Meet site is opened.

    These proprietary, bundled-by-default extensions are just a taste of what a browser engine monopoly looks like. Alternative frontends to the Chromium engine don’t make a difference as these frontends will suck up whatever changes upstream. We only have 3 major/relevant engines left, Blink (Chromium), Gecko (Firefox) and WebKit (Safari, originated in Konqueror I think), with Blink being a fork of WebKit (although very diverged by now).

    The web is so complex now that I don’t really see more engines becoming actually usable. Even Microsoft bailed out and eventually switched Edge over to Chromium.

    • Captain Beyond@linkage.ds8.zone
      5·
      4 months ago

      Vivaldi’s target audience is people who don’t mind proprietary blobs as long as they are “good” or make things “work better.” Given that Vivaldi itself is essentially a proprietary blob combined with a Chromium backend this makes sense.

    • Ilandar@aussie.zone
      2·
      4 months ago

      I feel like most of Vivaldi’s target audience is knowledgeable enough to enable an extension that’s disabled by default.

      You could make the same argument in reverse. It’s irrelevant if we’re talking about knowledgeable people. The target market for significant growth is less knowledgeable people, so it makes more sense to cater defaults to that type of user.