3 ms·
I actually think it would be OK if the telemetry were opt-in. At this point, I'd even settle for just having the software actually warn you about the data colle
by JohnFen 4y ago
I actually think it would be OK if the telemetry were opt-in. At this point, I'd even settle for just having the software actually warn you about the data collection on first use.
- ikiris 4y agoyou opt in by using the product. especially if its open source.
- teej 4y agoTracking my usage was never part of the social contract of OSS. This post is a reminder of that.
- martypitt 4y agoWhat social contract is that? As far as I'm aware, the contract of OSS is "you can fork this to change it, if you don't like it" (license permitting). A big part of the reason people advocate for OSS is so they can read the source code to understand what's going on, and change the parts they don't like. Telemtry sits squarely under that usecase. I agree that it's good manners for projects made users aware of telemetry, but there's no "contract" that implies they have to.
- JohnFen 4y agoHe was talking about the social contract, not the license. OSS is a community that has mores, expectations, and social contracts like any other community. Spying is very much in opposition to that social contract.
- JohnFen 4y agoIf you haven't provided informed consent, you haven't opted in.
- ikiris 4y agoAhh fair, I was under the impression this was disclosed telemetry.
- barnabee 4y agoI agree opt in telemetry (with no dark patterns, nagging, etc.) is fine. We do this (even then, strictly for non personaly identifiable crash/error reporting only), and I would encourage everyone who isn't a friend/family of the team, close community member, investor, etc. not to opt in. It isn't necessary. (Though having a small number of tens of people from those groups who do opt in is reasonably useful.)