4 ms·
> this is ultimately placing the convenience of the developers ahead of the privacy and autonomy of the users this is a biased framing of the problem. first of
by swyx 4y ago
> this is ultimately placing the convenience of the developers ahead of the privacy and autonomy of the users
this is a biased framing of the problem. first of all, the telemetry is often more useful for PMs (not developers) to make decisions on what efforts to prioritize vs not, and to assess relative success of launches. less of a convenience thing, but an industry standard way to get some meager signal from all your users, not just the ones that fill out surveys (and i'm sure theres plenty of complaints about surveys being unrepresentative too).
second of all, the work that developers and PMs do with this anonymized data is usually intended to help users.
pitting developer vs user is a false binary.
- RodgerTheGreat 4y agoIf usage information is so valuable, why not ask for it instead of simply taking it?
- JohnFen 4y agoThe answer I've gotten to this question from multiple sources is: because if we ask, not enough users say yes. Which speaks volumes.
- swyx 4y agobecause 80% of users dont opt in, dont opt out, they roll with the defaults, and when asked dont mind that youre getting anonymized telemetry back. most users are not privacy maxis like those motivated to comment 3 threads down on hn posts like these. they want to get their stuff done and expect the product to improve and understand that we have evolved these practices as pragmatic tradeoffs.
- chrisweekly 4y agoNot to mention it's usually possible to opt out (as it is with Next.js/Vercel).
- SanderNL 4y agoThey trust us and we are eroding that trust by invading their privacy for bs reasons. They do not understand, they just shrug “I guess devs need this”. They expect us to know, to care, because it is our job. We don’t and it’s sad.
- deafpolygon 4y agoAnd because of this erosion, more people are pushing back on telemetry. Imagine if everyone decided to get together, detail what telemetry they needed and why and outline how users can help - protect their privacy and actually Do The Right Thing(tm) that more people would be willing to care, and maybe contribute.
- thrashh 4y agoThe type of people who volunteer are different from the general population. That’s why things like public opinion surveys have to be random and why jury duty selection isn’t volunteer.
- Nicksil 4y ago>first of all, the telemetry is often more useful for PMs to make decisions on what efforts to prioritize vs not, and to assess relative success of launches. second of all, the work that developers and PMs do with this anonymized data is usually intended to help users. OK, then it places the developers and PMs convenience ahead of the users privacy and autonomy.
- chaps 4y agoYou're missing the point by focusing on "developer". "Developer team and related teams" might be a better phrase because it includes the PMs.
- JohnFen 4y agoThis. When I use the term "developer" in these sorts of contexts, I'm referring to the company as a whole, not just programmers working on the product.
- hashstring 4y agoExactly, both are developing a product.
- fhd2 4y agoIn 18 years, I've yet to see someone use telemetry in the interest of the user. I've seen it be used to save money, earn more money, and quite a bit for mental masturbation. What I've seen actually work in the interest of users is qualitative user research, e.g. user testing, and actively engaging with users. Sure, one can make the argument that if booking.com upsells rental cars more effectively they earn more money and provide a better service and experience for users. Haven't seen this happen once though.
- bin_bash 4y agoIt's super useful in big companies. If you want head count, you gotta show numbers. Otherwise projects get canned. This is especially true for projects like the ones shown. Organizations want to know if people are actually using this stuff. I disagree with the practice, but it's definitely the way it is.
- Yoric 4y agoFormer Firefox dev here. I was part of the Firefox performance team, which introduced Telemetry in Firefox. We used Telemetry to measure the performance of many operations, to determine, among other things: - which operations were running slowly on real user's computers (and how commonly they ran slowly), so that we could fix these; - whether users were faced with out of memory errors, or timeouts, etc.; - whether users had abnormally large database, preferences, etc. files, which suggested that we should optimize for such cases; - in some cases, whether some features were used at all because if they weren't, it wasn't worth optimizing them. I'd qualify these as definitely in the interest of the user. I know that not everybody enjoys having Telemetry collected on their usage, but without this, Firefox would never have been able to catch up with Chrome on user-visible performance.
- type0 4y ago> - in some cases, whether some features were used at all because if they weren't, it wasn't worth optimizing them. Terrible conclusion, by that reasoning a drunkard should only seek for his keys under the streetlight https://en.wikipedia.org/wiki/Streetlight_effect https://en.wikipedia.org/wiki/Streetlight_effect
- AlexandrB 4y ago> pitting developer vs user is a false binary. Not in the modern software ecosystem it's not. How often is telemetry used to make a product better vs. helping to add more dark patterns to increase "engagement"? No amount of telemetry seems to stop Microsoft from shoving more user hostile garbage into Windows 11.
- deleted 4y ago[deleted]
- SanderNL 4y ago“help us help you”? If that is so, just ask and explain and be more specific than “this helps improve things”. How hard is it to say how exactly this vague ball of data is helping The Users?