Hacker News Reader

How would you correlate that with anything to produce useful data? GitHub already knows what repos an SSH key has access to, and usually read-only access to a public repo for which you don’t have write permission is done with HTTPS.

>and usually read-only access to a public repo for which you don’t have write permission is done with HTTPS.

I don't know if this is the case. I always clone with `github.com:owner/repo` remotes, because it's shorter and saves me the effort of doing things differently based on whether it's my repo or not.

What's the line of thinking that led you to believing a change like this would be for user tracking?

(Seriously asking by the way, this isn't a put-down. MS isn't in the ad business, let alone Github, and these changes primarily affect people who are logged in, so … no idea how you can make the leap)

They already know everything you do on the site...

They aren't removing https cloning.