Live data from Hacker News

Waterfox Browser

waterfox.net

101–110 of 111 posts

Re: Waterfox Browser

#101
post #94

Earlier quoted context omitted.

I would say matching a repository based solely on a person's name is not a great way to ensure you have the right code.

Note that while website does not link to repository, repository does link to website.

Well it would, wouldn't it?

Re: Waterfox Browser

#102

> Waterfox does not collect ANY telemetry, meaning you don't have to worry about any tracking or usage information about what you do inside YOUR browser. This is woefully uninformed or malicious. There's a lot of tracking that is out of your hands. Such as canvas fingerprinting. Even sending back 0's (like tor does) doesn't prevent fingerprinting. In either case I lost confidence for the browser just by reading what…

Sorry maybe I worded it badly? But I thought the context of the sentence made it clear that Waterfox itself does not collect any telemetry or usage information. This sentence has nothing to do with websites themselves. I'll try and make the sentence a bit more obvious to avoid confusion :-)

Awesome! I think it makes sense to most people on HN, because we know about these things, but I doubt to anyone not on here (and I'm willing to bet more people than we'd suspect here).

I think there could be a simple fix that specifies that Watermark is not doing the tracking.

> Waterfox does not collect ANY telemetry, meaning you don't have to worry about us tracking or using information about what you do inside YOUR browser.

I think this sentence is still compelling and I don't find misleading.

Re: Waterfox Browser

#103
post #39
post #29

Why does it need to send your OS and browser version to check for updates? Couldn't it just look up whatever the latest versions are?

Well, I guess you can check for update without disclosing OS, but since binaries differ between OS you need to disclose OS to actually download the update. Browser version is not necessary, but sending browser version allows serving smaller binary diff instead of full binary, which Firefox actually does.

Ah! That makes sense. I had forgotten about binary diffs. I guess I can put my tinfoil hat back on the shelf...

Re: Waterfox Browser

#104
post #54

Earlier quoted context omitted.

I guess if someone really needs to use a legacy extension, it's a good thing that it's around, but I'm personally glad that XUL is dead both from a developer standpoint and as a user.

I'm still waiting for a working vertical tabs extension that doesn't leave the tab bar across the top wasting space. Dumping XUL is why it's hard to see firefox as a viable browser.

You can still remove the top tab bar in the current version of Firefox, though it is significantly more annoying to do so than it used to be.

https://github.com/piroor/treestyletab/wiki/Code-snippets-fo...

Re: Waterfox Browser

#105
post #8

I wanted to use Waterfox, but I wasn't sure about the security side of things. When vulnerabilities are found in Firefox, we can expect them to be fixed pretty quickly. Can the same be said for this project?

I managed to get the security patches out from ESR the same time, I don’t think I do too badly on that front. Not always easy though!

Re: Waterfox Browser

#106
post #45

Alternatives that allow you to still get your security and stability updates from Mozilla include two Gnu soft-forks. There's IceCat, which is the best-supported version and runs off of ESR. [1] There's also "abrowser" (that's literally what it's called) that is part of the Gnu Trisquel distribution, which is based on the most recent release. Both patch the browser to be more security and privacy friendly. [2] There…

The most recent version of IceCat at this time is 60.3.0, published on 2018-11-09 [1], 18 days after upstream [2]. Upstream is currently at 60.7.0, published on 2019-05-20 [3]. This puts IceCat more than half a year behind upstream. Waterfox published their version merging upstream 60.7.0 security fixes before upstream [4]. Using IceCat thus seems to a bad idea security-wise. I use upstream ESR ever since FF disabled…

I'm not sure what URL is technically supposed to be the correct one, but they do seem to have updated through at least 60.5: http://devel.trisquel.info/repos/packages/icecat/pool/main/i... Trisquel in general seems to be pretty dead, looking at their git.

While I'm not sure whether that includes any backported security fixes or not, you're right that this is concerning. Perhaps building it yourself is the way to go.

>I use upstream ESR ever since FF disabled add-ons since they let their cert expire [5]

Unless I'm mistaken that bug would have bitten you on ESR as well. The expired certificate was an intermediate used to sign most of the addons on AMO. If ESR wasn't using that certificate then it wouldn't have been able to validate those addons. Correct me if I'm wrong.

Re: Waterfox Browser

#108

Earlier quoted context omitted.

The most recent version of IceCat at this time is 60.3.0, published on 2018-11-09 [1], 18 days after upstream [2]. Upstream is currently at 60.7.0, published on 2019-05-20 [3]. This puts IceCat more than half a year behind upstream. Waterfox published their version merging upstream 60.7.0 security fixes before upstream [4]. Using IceCat thus seems to a bad idea security-wise. I use upstream ESR ever since FF disabled…

I'm not sure what URL is technically supposed to be the correct one, but they do seem to have updated through at least 60.5: http://devel.trisquel.info/repos/packages/icecat/pool/main/i... Trisquel in general seems to be pretty dead, looking at their git. While I'm not sure whether that includes any backported security fixes or not, you're right that this is concerning. Perhaps building it yourself is the way to go.…

Looking at their SCM, they updated to the newest upstream less than two days ago [1]. However, the change appears trivial, so it might be feasible to track upstream if building from source as long as their customization scripts remain compatible.

> that bug would have bitten you on ESR as well

Sorry, I didn't word that clearly. ESR was affected, but the signature check could be disabled from about:config. The release channel had that flag listed, but it had no effect.

[1] http://git.savannah.gnu.org/cgit/gnuzilla.git/log/

Re: Waterfox Browser

#109

Earlier quoted context omitted.

I'm not sure what URL is technically supposed to be the correct one, but they do seem to have updated through at least 60.5: http://devel.trisquel.info/repos/packages/icecat/pool/main/i... Trisquel in general seems to be pretty dead, looking at their git. While I'm not sure whether that includes any backported security fixes or not, you're right that this is concerning. Perhaps building it yourself is the way to go.…

Looking at their SCM, they updated to the newest upstream less than two days ago [1]. However, the change appears trivial, so it might be feasible to track upstream if building from source as long as their customization scripts remain compatible. > that bug would have bitten you on ESR as well Sorry, I didn't word that clearly. ESR was affected, but the signature check could be disabled from about:config. The release…

Ah, I didn't realize ESR did that. (And frankly I'm surprised it does.) One of the things I change when I build Firefox for myself is allowing the disabling of addon signings via about:config.

Re: Waterfox Browser

#110
Glad to see some coverage of this.

It's my default browser, since Firefox Quantum.

It still allows rich customisation, via classic XUL addons. I have a vertical tab bar, merged with a vertical bookmarks bar, which is flattened via another addon. I have a rich download manager with multi-streaming, resuming, and more.

When Firefox Quantum came out, 13 of my 17 add-ons stopped working. Several versions later, I can customise it a bit, but only in limited, clunky ways, requiring manual hacking of userChrome.css, and it's not very widescreen-friendly.

I don't care about privacy. Scott McNeally was right in 1999, and he's still right: "You have no privacy on the Internet. Get over it."

I don't like the new Firefox and I probably won't be back. Waterfox fills the need nicely.

Post reply on HN