| ▲ | yjftsjthsd-h 15 hours ago | ||||||||||||||||
On the contrary, OSS is precisely where this kind of spying on your users is least useful, since there's already a culture of them telling you, sometimes with code, what they need. | |||||||||||||||||
| ▲ | simonw 14 hours ago | parent | next [-] | ||||||||||||||||
That's not been my experience at all. The default response to open source code is stone cold silence - getting any feedback at all takes real effort. Those PyPI download numbers are one of the most useful hints as to whether my stuff is being used by anyone. | |||||||||||||||||
| ▲ | Ygg2 11 hours ago | parent | prev [-] | ||||||||||||||||
If that's the issue, that's a problem. They are telling you X. People, if they tell you, don't give their honest feedback. Or they might be a loud minority. If you ask people what coffee they want, they will all tell you low-sugar, very bitter black coffee. Then you see what they buy, and they keep buying sugary and creamy coffee that contains almost no caffeine. Telemetry isn't spying. At least when done properly. How do you figure out rare OOM crashes without some telemetry data? What if the reporter doesn't know how to figure out their OS and installed software that's required for debugging? I'm NOT saying telemetry should capture everything and sell that data to info brokers. I'm saying, done properly it give you valuable feedback. And you should be transparent about it. | |||||||||||||||||
| |||||||||||||||||