Waterfox Browser

The downloads on both sites are hosted on the same site but they do point to different versions[2][3].

Both pages link to the same BuyMeACoffee page[4].

The GitHub repository has a link to the net[5].

But the GitHub profile of the developer links the the org[6].

Very old versions[7] and the current version[8] of the wikipedia page list the org as the official website.

The org seems to have been the site for the project since as early as 2012 according to the wayback[9].

However the net doesn't seem to have been associated with the project (or anything) before 2019[10].

The most recent crawls of the org got 301 redirected to the net[11].

[0] https://www.waterfoxproject.org

[1] https://www.waterfox.net/

[2] https://storage-waterfox.netdna-ssl.com/releases/linux64/ins...

[3] https://storage-waterfox.netdna-ssl.com/releases/linux64/ins...

[4] https://www.buymeacoffee.com/waterfox

[5] https://github.com/MrAlex94/Waterfox

[6] https://github.com/MrAlex94

[7] https://en.wikipedia.org/w/index.php?title=Waterfox&oldid=59...

[8] https://en.wikipedia.org/w/index.php?title=Waterfox&oldid=89...

[9] http://web.archive.org/web/20120117003924/http://waterfoxpro...

[10] http://web.archive.org/web/20190418195027/https://www.waterf...

[11] http://web.archive.org/web/20190527072632/https://waterfoxpr...

I used Waterfox about 8 years ago, since standard Firefox didn't provide 64-bit Windows releases. After about a year, I got frustrated that it was skipping every other release, so I went back to standard Firefox. Between using NoScript (blocking most scripts), and benchmarks showing 64-bit wasn't much (if any) faster, I didn't notice standard Firefox being slow.

There's even more if you include WebKit-based browsers[1]. Out of those I would strongly recommend surf[2], which is not discontinued despite what Wikipedia says (latest upstream commit was a few months ago[3], but there are many active forks as well).

Shameless plug, but I've used my own fork[4] as main web browser for the past few months, and despite the amount of hacks and limitations, it fits my workflow on Linux quite well. It does involve some external tooling and configuration, and I still keep Firefox and Chromium around for tricky sites, but it's provided a great user experience more often than not.

The key benefit of surf is its simplicity, which we should all strive for as programmers and consumers of technology. The entire browser is under 3KLOC of very readable and well-documented C code. Granted, it relies heavily on WebKitGTK, but it avoids all the mess and complexity of modern browsers, extensions and security concerns simply because of its minimalism.

I would encourage anyone willing to make certain compromises to give it a try and contribute so we can make it easier to use and approachable for a larger and non-technical user base. As web browsers have become the main gateway to the Internet for a vast majority of people, we should actively work towards preventing abuses of user freedoms via aggressive advertising, fueled by corporate greed. We need to take the web back, and simplicity is key.

My goal would be to eventually strip out WebKit entirely, but that's a gargantuan task with no clear way forward, unfortunately. As mentioned in today's Google/ad-blocking thread, we need new and alternative browser engines, outside of the sphere of influence of large corporations.

[0]: https://en.wikipedia.org/wiki/List_of_web_browsers#Blink-bas...

[1]: https://en.wikipedia.org/wiki/List_of_web_browsers#WebKit-ba...

[2]: https://surf.suckless.org/

[3]: https://git.suckless.org/surf/

[4]: https://github.com/imiric/surf

And a few of my friends say that they have Waterfox deployed company wide because of NPAPI support, which means they don't have to still use an out-dated browser which is cool!