4 ms·

Are you certain? The last I heard about it from Vivaldi[0], they were only going to keep the MV2 code around so long as it's in the upstream codebase: > We wil

Are you certain? The last I heard about it from Vivaldi[0], they were only going to keep the MV2 code around so long as it's in the upstream codebase: > We will keep Manifest v2 for as long as it’s still available in Chromium. We expect to drop support in June 2025, but we may maintain it longer or be forced to drop support for it sooner, depending on the precise nature of the changes to the code. Note that June 2025 is the same date Google plans to drop support completely[1]. [0] https://vivaldi.com/blog/manifest-v3-update-vivaldi-is-future-proofed-with-its-built-in-functionality/ https://vivaldi.com/blog/manifest-v3-update-vivaldi-is-futur... [1] https://developer.chrome.com/docs/extensions/develop/migrate/mv2-deprecation-timeline https://developer.chrome.com/docs/extensions/develop/migrate...

yborg 2y ago
Vivaldi team does not respond to any comments asking about ongoing v2 manifest support; safe to assume it's gone as soon as it's out of Chromium upstream. Given Tetzchner's continual messaging on how important user privacy is to Vivaldi it seems like a strange decision, but I don't know how much effort would be required to maintain the support. They're a small team, so it would be understandable if they would just say it's too hard, but instead they have avoided the topic entirely, which suggests they agree with the direction.
- Raed667 2y ago
  Or they just don't want to admit publicly that they're too small to maintain a fork when it diverges this much
  - tourmalinetaco 2y ago
    Well Vivaldi is open source, right? Personally I would be reaching out to Brave, who already plans on maintaining V2 support, and see about a joint venture with a forked chromium.
    - Sophira 2y ago
      Vivaldi is not open-source: https://vivaldi.com/blog/technology/why-isnt-vivaldi-browser-open-source/ https://vivaldi.com/blog/technology/why-isnt-vivaldi-browser...
      - saagarjha 2y ago
        > Even though our license doesn’t strictly allow this, we welcome it and we encourage users to share these code modifications on our forums. lmao wtf
      - tourmalinetaco 2y ago
        Ah. They can go fuck themselves then. I had assumed given the fact that the source was available.
        cute_boi 2y ago
        c++ sources are available.
    - rpdillon 2y ago
      I was intensely interested in this, and after much reading, here's my best understanding: Neither Brave nor Vivaldi are proposing to maintain engine support for v2: they both point to the codebase retaining support after Chrome drops support (likely for enterprise) as being the driver of their ability to offer v2. Both say that once those codepaths are removed, so too will v2 support be removed from Vivaldi and Brave. No idea when Google will make that call.
      - tourmalinetaco 2y ago
        Alright, so they’re both literally just useless wastes of man-hours then. Good to know.
- deleted 2y ago
  [deleted]
bambax 2y ago
But... what could possibly be the point of using a chromium based browser that is not Chrome, if not for MV2 support?
- int_19h 2y ago
  In case of Vivaldi, it's features like vertical tabs, and extreme customizability for the built-in stuff (for tabs alone the options dialog is like 3 pages of checkboxes for all the various aspects of how they behave). Also for those who use cloud bookmark/history/tab sync, people might just not want Google specifically to have that data; Vivaldi does its own sync.
  - KetoManx64 2y ago
    I use both Vivaldi, Brave and Firefox, all have their own strenghts. Brave now has built in vertical tabs as well: https://brave.com/blog/vertical-tabs/ https://brave.com/blog/vertical-tabs/
- andmalc 2y ago
  MS Edge, Arc, and Sidekick have features Chrome doesn't such as split screen, side panels, and vertical tabs. Likewise for Firefox forks such as Zen.
  - aydyn 2y ago
    None of those things are anything close to killer features much less reasons to switch. Verticle tabs, seriously?
    - ysabri 2y ago
      It is all a gimmick but as long as people are switching to a chromium based browser and not Firefox I'm happy. With that said, I don't know how anyone would trust a small team to build them a secure and safe browser. Chrome is so battle tested at this point and Google puts a lot of resources in maintaining it, they stand to lose a lot more given their scale.

yborg 2y ago

Vivaldi team does not respond to any comments asking about ongoing v2 manifest support; safe to assume it's gone as soon as it's out of Chromium upstream. Given Tetzchner's continual messaging on how important user privacy is to Vivaldi it seems like a strange decision, but I don't know how much effort would be required to maintain the support. They're a small team, so it would be understandable if they would just say it's too hard, but instead they have avoided the topic entirely, which suggests they agree with the direction.

Raed667 2y ago
Or they just don't want to admit publicly that they're too small to maintain a fork when it diverges this much
- tourmalinetaco 2y ago
  Well Vivaldi is open source, right? Personally I would be reaching out to Brave, who already plans on maintaining V2 support, and see about a joint venture with a forked chromium.
  - Sophira 2y ago
    Vivaldi is not open-source: https://vivaldi.com/blog/technology/why-isnt-vivaldi-browser-open-source/ https://vivaldi.com/blog/technology/why-isnt-vivaldi-browser...
    - saagarjha 2y ago
      > Even though our license doesn’t strictly allow this, we welcome it and we encourage users to share these code modifications on our forums. lmao wtf
    - tourmalinetaco 2y ago
      Ah. They can go fuck themselves then. I had assumed given the fact that the source was available.
      - cute_boi 2y ago
        c++ sources are available.
  - rpdillon 2y ago
    I was intensely interested in this, and after much reading, here's my best understanding: Neither Brave nor Vivaldi are proposing to maintain engine support for v2: they both point to the codebase retaining support after Chrome drops support (likely for enterprise) as being the driver of their ability to offer v2. Both say that once those codepaths are removed, so too will v2 support be removed from Vivaldi and Brave. No idea when Google will make that call.
    - tourmalinetaco 2y ago
      Alright, so they’re both literally just useless wastes of man-hours then. Good to know.
deleted 2y ago
[deleted]

bambax 2y ago

But... what could possibly be the point of using a chromium based browser that is not Chrome, if not for MV2 support?

int_19h 2y ago
In case of Vivaldi, it's features like vertical tabs, and extreme customizability for the built-in stuff (for tabs alone the options dialog is like 3 pages of checkboxes for all the various aspects of how they behave). Also for those who use cloud bookmark/history/tab sync, people might just not want Google specifically to have that data; Vivaldi does its own sync.
- KetoManx64 2y ago
  I use both Vivaldi, Brave and Firefox, all have their own strenghts. Brave now has built in vertical tabs as well: https://brave.com/blog/vertical-tabs/ https://brave.com/blog/vertical-tabs/
andmalc 2y ago
MS Edge, Arc, and Sidekick have features Chrome doesn't such as split screen, side panels, and vertical tabs. Likewise for Firefox forks such as Zen.
- aydyn 2y ago
  None of those things are anything close to killer features much less reasons to switch. Verticle tabs, seriously?
  - ysabri 2y ago
    It is all a gimmick but as long as people are switching to a chromium based browser and not Firefox I'm happy. With that said, I don't know how anyone would trust a small team to build them a secure and safe browser. Chrome is so battle tested at this point and Google puts a lot of resources in maintaining it, they stand to lose a lot more given their scale.