5 ms·

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

by 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]

by yborg 2y ago

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]