5 ms·
This is where the vocal minority of HN posters who are in a snit about telemetry are wrong. This is the kind of issue you can discover at global scale, but only
by jeffbee 3y ago
This is where the vocal minority of HN posters who are in a snit about telemetry are wrong. This is the kind of issue you can discover at global scale, but only if you collect the data.
- n4r9 3y agoIt looks like this could have been discovered by simply having (anonymised) crash report telemetry? I don't know about others, but that sort of telemetry doesn't sound so bad.
- Nextgrid 3y agoIt's very hard to have useful anonymized telemetry. In this case, you actually need at least a partial memory or register dump to understand what's going on, but those can contain sensitive data that the failing code was processing. Telemetry doesn't have to be 100% anonymized - it can (and in some cases needs) to contain PII, just needs to be collected respectfully and transparently. Ask the user before sending something, and let the user review it. The user can then make their own decision.
- bpye 3y ago> Ask the user before sending something, and let the user review it. The user can then make their own decision. I under The sentiment, but say you were sending a memory dump as part of your crash reporting. How is a user going to review that?
- mixedbit 3y agoSuch crash data can be collected with an old fashion 'Firefox has crashed, send a problem report to Mozilla [OK] [Cancel]' dialog, which is much less privacy-intrusive than telemetry.
- ksenzee 3y agoRight, and Firefox for Android does in fact collect its crash data like this.
- burkaman 3y agoPersonally I don't have a problem with automatically sending the type of telemetry that makes detecting this possible, but Mozilla could also discover this issue by in-house testing on a wide variety of devices, and/or prompting users to submit telemetry after a crash. It's not feasible for a smaller developer, but it wouldn't be unreasonable for Mozilla to have a big lab bench with like 100 different devices on it that are just constantly running a script to start Firefox and load a suite of test sites.
- sjsdaiuasgdia 3y agoI don't think you could really approach the kind of coverage automatic crash telemetry can give with a bunch of test devices. You will absolutely find a non-zero number of issues with the test devices, but it's not really the same. Without substantially increasing the cost and work to maintain the test pool, you'll be testing exactly one combination of OS version/patch level/settings, one internet connection medium/carrier, one set of browser config options, etc for each device in the pool. The investigation into any fault isolated to a single device in the test pool has to start with suspicion of the health of the specific device. The test S20 crashing doesn't tell you that every S20 will crash in the same way, it could be an isolated local fault. Yes you can throw more devices but that's further increasing the cost and effort of maintaining the test pool.
- jfk13 3y agoIt's not remotely feasible to test more than a tiny fraction of the variety of devices, configurations, and sites that a product like Firefox is going to encounter in the real world.
- burkaman 3y agoI agree you'd never catch everything, but if it's crashing on the latest Samsung flagship phone you could probably catch that.
- toast0 3y agoUser volunteered crash telemetry is better than nothing, but automatic crash telemetry is going to have a more representative sample. A compromise would be to grab just a stack trace and phone model / firmware version etc automatically, and a full dump with user affirmative consent; but if that's not compatible with your privacy stance, asking everybody for everything is reasonable but limiting. Android has an immense variety of devices. Without a representative sample, you wouldn't know which devices to buy. Regional variants sometimes have a huge difference and sometimes not; this bug seems to be tied to non-US Samsung flagships, which you might not buy if you're US based and don't know what people are using.
- vardump 3y agoIndeed. Telemetry is often used for good purposes, like improving features that cause trouble to end users and to fix crashes. I'm not saying bad actors don't exist, just that telemetry is often used for good, with no nefarious goals.
- helf 3y ago[dead]
- rollcat 3y agoWe've had crash reports for about as long as we've had computer programs. The problem is not in the mechanism itself, but in its abuse for (overwhelmingly, non-consensual) behavioral profiling or spying. Even when not abused to violate our privacy, the end result is often highly questionable. In place of good design, common sense, and user studies, companies try to extrapolate trends/patterns from data where there are none, resulting in mediocre decisions at best, and self-feeding cycles of devolution. ("Users are clicking this button a lot, let's make it larger" - users are actually clicking the button by accident.)
- always2slow 3y ago[flagged]
- jfk13 3y agoIrrelevant. Collecting telemetry such as Mozilla does isn't remotely like having remote root access to people's phones.
- jeffbee 3y agoThat's exactly the kind of derangement I am talking about. One gets the impression that the typical HN commenter has never worked on a software project of any consequence at all.
- mcronce 3y agoOne often gets the impression that large swathes of people (even on here) don't realize that software today is more complex than software from 1993
- anderskaseorg 3y agoTelemetry is not remote access, much less root access, which does not even exist on typical phones. Phone apps are sandboxed by the OS and can only collect information that the OS allows them to collect. It may of course be possible to abuse this limited information for tracking (and that abuse should absolutely be called out when it occurs), but it’s not the same thing.
- SanderNL 3y agoThis minor issue that also is not Firefox’s fault is not enough to sacrifice anything let alone privacy.
- Nextgrid 3y agoEven if telemetry is useful (this is a rare example - the vast majority of telemetry is either useless or actively works against the users), it's still a breach of privacy and confidentiality (crash dumps - which are necessary to investigate/reproduce such bugs - can contain highly confidential data including passwords or session cookies). > but only if you collect the data. If the problem is impacting the user and they want it fixed they'll happily tell you. This bug (which causes crashes) would've been investigated just as well by asking users "Firefox has crashed - send bug report?", while giving the user the choice to decline if they had sensitive data in the browser's state. Obviously nobody in their right mind should opt-in to generic telemetry because all the "product improvements" excuses never panned out - in the last decade software has only become worse, more annoying, and less feature-full, so people are making the rational decision and are not opting into something that's not actually benefiting them. But opt-in telemetry in specific cases where the user actually has a problem like this occurrence can work just fine.
- ptx 3y agoYou're wrong about them being wrong. Nobody is arguing that telemetry could not possibly have any upsides (primarily for the developer), only that the downsides (primarily for users) make the tradeoff unacceptable.
- dspillett 3y agoYour point would be correct if that was the only telemetry being collected. The pile of stuff most things are sending back home contains much that would not be useful here but is potentially privacy breaking (or just purely for marketing purposes with no intention of being useful to the user). Similarly, in either case telemetry is fine if it is opt-in, and if extra is collected the opt-in is repeated (i.e. no stalking via the back door by changing what is collected and sent home after consent is given).
- temac 3y agoBullshit, CPU bugs have been found before wide usage of telemetry and will continue to be found in various context, number of them not doing it even if they could. Telemetry is probably just one more excuse to ship crap in the first place.
- nottorp 3y ago> but only if you collect the data You spelled 'send crash dumps with the user's permission' wrong.
- msla 3y agoNormal software testing (remember that?) can catch bugs without invasions of privacy.
- howinteresting 3y agoHave you ever worked on a large-scale software product used by millions of people across thousands of kinds of devices? Telemetry is always going to be useful.
- Nextgrid 3y ago> Telemetry is always going to be useful. Useful for what? We've had an explosion of telemetry and "analytics" the past decade and software quality and functionality has only gone downhill. In some fields we've outright regressed compared to early 2000s tooling. A simple example is that despite all the telemetry, manpower and tech innovation, every single mainstream communications product out there is inferior to pre-Microsoft Skype (despite the latter being built with much less manpower and running on much more primitive hardware & bandwidth). Of course, not all of this devolution is to blame on telemetry alone, but I disagree that telemetry is some sort of requirement or game-changer when it comes to software quality. We've successfully built good quality software before it and within reasonable budgets.
- terribleperson 3y agoI find Discord more usable than pre-Microsoft Skype, though I still miss the peer-to-peer capability and built in file transfer. Skype admittedly had a better UI in some ways and didn't demand nearly as many resources. I do agree that it seems that despite increased capabilities across the board and piles and piles of newer and better ways to do things, the quality of consumer software has dropped somewhat.
- botanical 3y agoI allow telemetry to Mozilla but no one else