Hacker News Reader

Comment by krono | Hacker News Reader

It makes these connections even when all the things mentioned in the official "How to stop Firefox from making automatic connections"[1] are disabled. This includes the captive portal detection you allude to.

Regardless:

The browser asks me if I allow it to make these connections.

I tell it in unmistakable and irrevocable terms that I do not.

The browser makes these connections anyway.

The problem was never the connections or the contents of the data stream. You were aware of this before posting your comment, and yet you commented anyway. You are a troll.

1: https://support.mozilla.org/en-US/kb/how-stop-firefox-making...

View on HN

Am I really the troll, or those who bring down the only remaining truly libre, open-source browser engine over stupid nitpicky bullshits, while not contributing anything positive to improve on the status?

Just as a courtesy I'll let you know that I won't bite here. This is entirely pointless.

The point is, if you provide an option to turn off telemetry, it should be off. No exception. In this case of an airport connection requiring a registration page intranetwork, this occurs via first request through their proxy with header redirect.

The point is, don’t lie about saying you respect privacy with half-baked options and telemetry for me but not for thee bs. If I turn off telemetry, you aren’t allowed to send telemetry. Of any kind. Not a crash log. Not an install token. Not a call home to see if maybe possibly your on an airport wifi and make-our-app-work-edge-case()

There is a distinct difference between telemetry and the captive portal requests Firefox makes. The captive portal checks have nothing to do with telemetry and contain no payload, which is why they are not covered by that setting.

Captive portal detection was only brought up by the non-constructive commenter and isn't part of the problem.

When the setting labelled "Allow Firefox to send technical and interaction data to Mozilla" is unchecked, the browser still sends out technical and interaction data through parameters added to various browser-provided/generated URLs (e.g. search results pages from built-in search providers, Firefox documentation links provided by the browser, DevTools compatibility panel links to MDN, etc.), by sending out pings when hovering over or clicking interactive browser-native interface elements, and in several other ways.

In summary: that setting is non-functional and should either be fixed, re-labelled, or removed entirely.

Reply on news.ycombinator.com