> Yes, you could. You can adapt the code and use an extension to use your "fork" instead of the provided one. Ok, that's possible to do but it's not a solution

> Yes, you could. You can adapt the code and use an extension to use your "fork" instead of the provided one. Ok, that's possible to do but it's not a solution to the problem because: - You would not have much use of it because javascript is often very dependent on the web page and the server so if any of those changes, your script breaks. There is no expectation that people do this so the website owners have no reason to keep a stable API. - Only the people who use that extension or browser benefit from having that freedom. Compare this to traditional software where forks can easily be created and maintained and get more popular than the original fork. Now people who don't even know about the forks will benefit from it because they will likely use the fork that gets popular which can be the better one. An example of this is software distributions (like Debian and so on) that may modify upstream software in a way that benefits all users, even the ones who are not aware. That would be extremely difficult to do with all websites on the web without things constantly breaking.