Live data from Hacker News

GitHub CLI now collects pseudoanonymous telemetry

cli.github.com

331–340 of 368 posts

Re: GitHub CLI now collects pseudoanonymous telemetry

#331
post #320
post #228

Earlier quoted context omitted.

Hey, please don't blindly paste/post from LLMs, please.

I appreciate the "please", but this comes across as presumptive. First, you don't know the effort level I put in. Second, you haven't seen the end result. Third, why do you think I would "blindly paste" from an LLM? If you take a look at my profile or other comments, I hope that is clear. I appreciate feedback in general, and I am glad when people care about making HN a nice place for discussion and community. Someti…

Where is the gist? I assumed LLM/bot because of the disconnect between "here's a gist" and "still cookin"

Re: GitHub CLI now collects pseudoanonymous telemetry

#333
post #331
post #320

Earlier quoted context omitted.

I appreciate the "please", but this comes across as presumptive. First, you don't know the effort level I put in. Second, you haven't seen the end result. Third, why do you think I would "blindly paste" from an LLM? If you take a look at my profile or other comments, I hope that is clear. I appreciate feedback in general, and I am glad when people care about making HN a nice place for discussion and community. Someti…

Where is the gist? I assumed LLM/bot because of the disconnect between "here's a gist" and "still cookin"

I ask everyone to be a bit more careful about the "assume LLM/bot" thing. That hair-trigger is often counterproductive.

Anyhow, the Claude research took 36 minutes to run, so I put it to the side and didn't link it originally. I'm still thinking through it -- there is a lot to cover : https://gist.github.com/xpe/654af2731d40a145e1d0b8b694fe8fd3

Re: GitHub CLI now collects pseudoanonymous telemetry

#334
post #14

Why we collect telemetry ...our team needs visibility into how features are being used in practice. We use this data to prioritize our work and evaluate whether features are meeting real user needs. I'm curious why corporate development teams always feel the need to spy on their users? Is it not sufficient to employ good engineering and design practices? Git has served us well for 20+ years without detailed analytics…

Come on, do you actually think "corporate engineers" care about what you are doing individually? Do you think they look specifically for you and make fun at your individual usage pattern? Do you think it gives them interesting information about your private life?

No one cares, there are millions of users, no one is going to look at your data, and even less be able to actually know which person a given user is.

We legit just want to know aggregated and objective information about how people use our products so we can make it better for you.

"Why do all corporate try to spy on our usage patterns?" Because the ones who don't have a crap product and all died long ago.

Re: GitHub CLI now collects pseudoanonymous telemetry

#335
post #14

Why we collect telemetry ...our team needs visibility into how features are being used in practice. We use this data to prioritize our work and evaluate whether features are meeting real user needs. I'm curious why corporate development teams always feel the need to spy on their users? Is it not sufficient to employ good engineering and design practices? Git has served us well for 20+ years without detailed analytics…

Especially true because it has also been proved that these telemetry tools often picture a distorted reality.

My "telemetry" check is Windows. I does the same, forced it on users and it certainly didn't get better from it. The correlation with quality decline might be independent, but I would wager some shitty manager put up a shitty metric, everything got optimized towards that and leadership has lost the bigger picture because these numbers cannot transport general understanding.

Re: GitHub CLI now collects pseudoanonymous telemetry

#336
I would very much recommend Gitea here. It is just a better GitHub. Can be integrated in corpo networks just fine, you can have ci/deployment pipeline you completely control.

Sure, if you want your repos to be public, you need a host. But honestly they aren't too pricey for offering code, even if prices are currently very high.

Re: GitHub CLI now collects pseudoanonymous telemetry

#338

Earlier quoted context omitted.

Man if I had a nickle for every time a PM asked me to violate user privacy for the purposes of making a slide that will be shown to their boss for 2.5 seconds I'd probably make enough to actually retire someday.

There's obviously misuse and abuse in the world, but telemetry from production systems out in the wild is incredibly useful for all kinds of decision-making. It's silly to dismiss it outright.

Some of it, yes. But not the kind that's put in place so the clueless Joe who used to do copy-writing 3 years ago can keep their high salary because they decided to join the proverbial "IT".

Re: GitHub CLI now collects pseudoanonymous telemetry

#339
post #262
post #103

Earlier quoted context omitted.

Sure, you can spend the weeks to months of expensive and time consuming work it takes to get a fuzzy, half accurate and biased picture of what your users workflows look like through user interviews and surveys. Or you can look at the analytics, which tell you everything you need to know immediately, always up to date, with perfect precision. Sometimes HN drives me crazy. From this thread you’d think telemetry is scre…

Many products would be much better if they listened to what people are saying on public forums instead of using telemetry. For example, Google Maps has a longstanding bug where it auto-translates all reviews even if they are in a language you speak. If Google cared about user feedback, they could’ve easily fixed it, but no amount of telemetry will tell them this.

What you're saying is exactly wrong. What people say on public forums is a very biased sample, the proverbial vocal minority

Re: GitHub CLI now collects pseudoanonymous telemetry

#340
post #61
post #14

Why we collect telemetry ...our team needs visibility into how features are being used in practice. We use this data to prioritize our work and evaluate whether features are meeting real user needs. I'm curious why corporate development teams always feel the need to spy on their users? Is it not sufficient to employ good engineering and design practices? Git has served us well for 20+ years without detailed analytics…

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.

They could well use the data from their own developers, couldn't that be enough?
Post reply on HN