CharmCityCrab
commented
2 years ago This has come up in the past.
Apparently, and this is just my understanding as a lay person, I may not have all the technology terms right, Fenix-based browsers consist of three main components or parts. All of the Iceraven specific modifications at this time are to one of those components or parts.
Adding AkenFox user.js would mean extending the fork to changes in a second of the three parts. The lead developer of Iceraven doesn't necessarily have a problem with that in principle, but is not inclined to do it on his own. I think he would probably want someone to volunteer to make the changes and to keep that new part of the code up to date and compatible- so a volunteer with the ability to do that would be required.
The other thing is that Iceraven, while intended to be more private than Chrome, Firefox, or most mainstream browsers, is not willing to sacrifice the functionality and compatibility necessary to be as ultra-private as, say, Tor.
So, what I guess what would be needed to get this into the build would be first a developer to join the team and create and maintain that part of the code, and then second the new person would have to have a talk with interfect about which of the user js changes Akenfox institutes should be included and should not be included by default in Iceraven.
I wonder if "ArkenFox user.js" can be added internally
Link : https://github.com/arkenfox/user.js