Earlier quoted context omitted.
Looks like I judged them well in not doing so. I would have been such a sucker. After all, donating to corporations is for bootlickers. https://www.waterfox.com/blog/waterfox-has-joined-system1/ So they’re just shilling their own search product on their own browser. No different from Google and Chrome. Except with some corporate bootlicking from running dog lackeys. He literally sold it to an online advertising compa…
Right. So you don't ever donate to anything, right? Just in case. The future. You know?
15 Years of Forking
61–65 of 65 posts
Re: 15 Years of Forking
#62I am surprise there is no mention of Librewolf here. The differences of Librewolf and Waterfox is pretty hard to grasp, I am digging a little bit but so far I guess I would say using any of them is still way better than the main alternatives. Librewolf is, to me, the way better alternative as this is really in the FOSS mindset : a tool for everyone to use and by anyone to contribute. Seeing their plateform alone (Lem…
> The differences of Librewolf and Waterfox is pretty hard to grasp I use Waterfox on Linux and one of the things I like the most is that it works with the global menu bar in Unity, Xfce and so on. LibreWolf, in my testing, does not. My experiment with it ended there, TBH. (Neither did Floorp.) Hopping between Waterfox and Firefox is easy because Waterfox works with Mozilla Sync. I think LibreWolf might not, and I ha…
Re: 15 Years of Forking
#63Earlier quoted context omitted.
Nothing to "fix" per se - webextensions need to interact with website data, otherwise they wouldn't be much use. Any extension with content script access can read page content including form fields. The only real mitigation is being selective about which extensions you install and what permissions you grant them (even then, ownership of extensions change hands, updates can change what they do... it's a never ending b…
My naive fix would be to disable extensions from accessing form field data without explicit approval. Hell, add different approval boxes for read, write, and hidden-text. What am I missing?
Never mind the technical challenge to allow doing anything with the DOM but disallow reading the forms. Like, prevent the forms leaking its text when you do funny things like testing character width via line breaking or font changes.
Re: 15 Years of Forking
#64> Mozilla : Break free from big tech - our products put you in control of a safer, more private internet experience. (Adds AI that needs 7 about:config entries to disable, until users roast it enough that they add an off switch.) > Waterfox : And we still don’t have AI in the browser. That hasn’t changed. The browser’s job is to load web pages, keep your data private, and get out of the way. It seems other browsers h…
Re: 15 Years of Forking
#65Earlier quoted context omitted.
There was a recent comment: "if you don't know: any browser extension can read input/password fields across all site(s) you gave it access to (yeah, it's crazy but unfortunately true)." https://news.ycombinator.com/item?id=47553048 Would either WF or LW fix that? Is it true?
Nothing to "fix" per se - webextensions need to interact with website data, otherwise they wouldn't be much use. Any extension with content script access can read page content including form fields. The only real mitigation is being selective about which extensions you install and what permissions you grant them (even then, ownership of extensions change hands, updates can change what they do... it's a never ending b…