Earlier quoted context omitted.
> Watching people move their mouse and click stuff on “your webpage” is fucking spying. It’s in my browser. On my machine. Not running on your hardware. Well, I was mainly talking about network requests, which are quite literally served by "my hardware" when your client reaches out to my servers, and they agree to serve your client. I do agree that it sucks that browser viewports now also are considered "mine" from t…
Yeah server logs don’t bother me. I’m requesting a resource, you unavoidably see that happen. The attitude that’s changed is that in the 90s and 00s a program that sent information about what you’re doing that wasn’t necessary and expected for how it operates would have been instantly, popularly, and unequivocally labeled spyware by a programmer crowd. Now it’s normal and you get a bunch of folks claiming it’s ok.
GitHub CLI now collects pseudoanonymous telemetry
361–368 of 368 posts
Re: GitHub CLI now collects pseudoanonymous telemetry
#362Earlier quoted context omitted.
You could survey a representative sample
Not really. (a) People hate responding to surveys and hate emails, you're more likely to lose users than to get data (b) there's no way you're surveying people's in a way that gets you information like "time spent on a page" or "time between commits" or whatever. This is just nonsense tbh. Surveys and customer outreach solve completely different problems from analytics.
Re: GitHub CLI now collects pseudoanonymous telemetry
#363Earlier quoted context omitted.
You can hire people to test your product and provide analytics. But not try to siphon the data for free.
I'm not taking a side on whether a product should add telemetry. I'm rejecting the absurd notion that these suggestions are at all giving the same information.
Re: GitHub CLI now collects pseudoanonymous telemetry
#364Earlier quoted context omitted.
You're only flying blind if you make decisions not looking and thinking. Analytics isn't the only way to figure out "what your users actually care about", you can also try the old school way, commonly referred to as "Talking with people", then after taking notes, you think about it, maybe discuss with others. Don't take what people say at face value, but think about it together with your knowledge and experience, and…
What people say, and what people do are different things. Especially when the people who agree to talk to you aren't representative of the whole user base.
Re: GitHub CLI now collects pseudoanonymous telemetry
#365Earlier quoted context omitted.
> The difference between what people tell you when asked directly and how they actually use your software is actually shocking. And the difference between what they do and what they want is equally shocking. If what they want isn’t in your app, they can’t do it and it won’t show up in your data. Quantitative data doesn’t tell you what your users want or care about. It tells you only what they are doing. You can get s…
> If what they want isn’t in your app, they can’t do it and it won’t show up in your data. Excellent point. > but if it’s not entirely opt-in, I think it is effectively spying no matter what you’re collecting, varying only along a dimension of invasiveness. Every web page visit is logged on the http server, and that's been the default since the mid 1990's. Is that spying?
Re: GitHub CLI now collects pseudoanonymous telemetry
#366Earlier quoted context omitted.
Wow, it really is sad how literally unthinkable it is to you and so much of the industry that you could actually talk to your users and customers like human beings instead of just data points. And you know what happens when you reach out to talk to your customers like human beings instead of spying on them like animals? They like you more and they raise issues that your telemetry would never even think to measure. It…
Get off your high horse. Talking to users when you have hundreds of customers does no more than give you an idea of what those specific people need. If you have hundreds of users or more, then data is the only thing that reliably tells you these things.
Re: GitHub CLI now collects pseudoanonymous telemetry
#367Earlier quoted context omitted.
I used to believe that it was not necessary until I started building my own startup. If you dont have analytics you are flying blind. You don't know what your users actually care about and how to optimize a successful user journey. The difference between what people tell you when asked directly and how they actually use your software is actually shocking.
Game developers benefit tremendously from streams where they get to see peoples webcams _and_ screens as they use their software. This would be _absolutely insane_ telemetry to request from a user for any other piece of software, but it would be fantastically useful in identifying where people get frustrated and why. That said, I do not trust Microsoft with any telemetry, I am not invested in helping them improve the…
Re: GitHub CLI now collects pseudoanonymous telemetry
#368Earlier quoted context omitted.
> never has written about If you don't want to look at what people write you can't say that they haven't written about it. > the supposed failure of design I don’t think people complain about the internals of git itself as much as the complexity of all the operations. If you want to read about complaints, you really don't have to look further than the myriad of git GUIs, TUIs and otherwise alternative/simplified inte…
> I don’t think people complain about the internals of git itself as much as the complexity of all the operations. The complexity is only there when you want to avoid learning what you’re doing. Just like find(1) is complex if you don’t know stuff about the file system or sed(1) is complex if you don’t know regex and line based addresing of a text file. A lot of people who are using git don’t want to know what a comm…