i've been meaning to implement telemetry in pretty much all my software, because
* I have more projects than time
* I want to know what platforms I should prioritize testing and supporting on
* Seeing my stuff get used gives me a fuzzy feeling
@ChlorideCull I mean, implementing telemetry is just gonna make *less* people use your apps so that last point us gonna backfire lol
@hazelnot You overestimate how much of my software audience cares about telemetry, especially privacy conscious telemetry
@ChlorideCull Sorry for assuming your audience cares about their privacy, I guess 🤷♀️
@hazelnot plenty care who gets their hands on the telemetry, not nearly as many care about it as a concept
@ChlorideCull I guess that's fine if all of your audience is also programmers, cause they can analyze the source code and see where the data is sent (although even then I wouldn't really want the developer of an app I'm using to be able to track me because how am I supposed to know what they're gonna do with that data) but most people can't really do that so it's safe to assume the worst
@hazelnot When you run something someone else has programmed or compiled you have to put a level of trust in them, if you assume the worst you might as well not run it at all, because if someone is dishonest about personal data, why wouldn't they just put all kinds of garbage in the software anyways? Drive-by installs are much more lucrative to someone dishonest than extra telemetry.
@ChlorideCull ...well now I just wanna throw all my computers in the trash and never use software ever again thanks 🙃
This would be a once a calendar month ping (controlled client side) with the project name, project version, OS/Distro, and OS/Distro major version
The server, upon receipt, stores those four fields, and discards the rest