Microsoft is now in the process of turning off Manifest V2-based extensions in Edge, such as uBlock Origin. However, not everything is lost at this point.
The reason why Chromium uses LGPL is because they forked the code from Safari, which had previously forked the code from KHTML (KDE’s web rendering component, used in Konqueror). The LGPL was provably insufficient to prevent corporate usurpation of the project, as a historical fact.
As for the “A” part of AGPL not being relevant for locally-run software, (1) it doesn’t hurt either, and (2) having maximal protections could prevent weird corporate shenanigans that we haven’t thought of yet.
The LGPL does its job, it’s not as copyleft as GPL or AGPL, but having those licenses doesn’t guarantee that companies will use it, like Gab, which used a fork of Mastodont, Truth Social, or Pawoo. If you want a more restrictive license, the OSI basically won’t accept it as open source because it doesn’t meet their guidelines.
Also, there are no other browsers due to the standards set by W3C and therefore browsers have to have corporate support.
The reason why Chromium uses LGPL is because they forked the code from Safari, which had previously forked the code from KHTML (KDE’s web rendering component, used in Konqueror). The LGPL was provably insufficient to prevent corporate usurpation of the project, as a historical fact.
As for the “A” part of AGPL not being relevant for locally-run software, (1) it doesn’t hurt either, and (2) having maximal protections could prevent weird corporate shenanigans that we haven’t thought of yet.
The LGPL does its job, it’s not as copyleft as GPL or AGPL, but having those licenses doesn’t guarantee that companies will use it, like Gab, which used a fork of Mastodont, Truth Social, or Pawoo. If you want a more restrictive license, the OSI basically won’t accept it as open source because it doesn’t meet their guidelines.
Also, there are no other browsers due to the standards set by W3C and therefore browsers have to have corporate support.