31–40 of 113 posts
Earlier quoted context omitted.
I agree, but I think such information should be available to all people. Some people will be doing this anyway, and they can hide this by using a transparent pixel.
What benefits do you feel you get from this over the view counting Github already does for you?
Which exact headers are being leaked by GitHub? Depending on what they leak, this could be something only useful for counting hits (if all they leak is the implicit time of the request), or for fully tracking users (if they leak Etags, original IPs, etc). It's too bad the author removed the badge from their Github profile. It would be interesting to see the effect of this post on profile views.
"GET /counter.svg HTTP/1.1" 200 565 "-" "github-camo (62249a1c)"
You could also simply click on the "Insights" tab of the repository you created to host the README.md page.
> According to my tests, profile views do not count as repo views, and I hope, in the future, we will be able to see traffic stats in the repository that hosts the README file.
First I heard about a readme for your profile page. So the facebook-ification of GitHub progresses? At what point is LinkedIn going to be merged into GitHub? (Only partially /s)
Personally I don't see much reason for this to be implemented via a git repository (rather than a text field in a database, like the existing Bio text), other than "we're GitHub, everything's a git repository, so why not".
At the moment, it's a single-file repository. Perhaps they have some ideas for other things that could be served from there too.
Weirdly at the moment it's required to be a public repository. This seems counterproductive: if it's my personal information blurb I don't much want other people looking at its history and I certainly don't want them forking it. (Are there any non-malicious reasons for doing that?)
You could also simply click on the "Insights" tab of the repository you created to host the README.md page.
From TFA: > According to my tests, profile views do not count as repo views, and I hope, in the future, we will be able to see traffic stats in the repository that hosts the README file.
Unrelated badge ideas: 1. Write a watcher that periodically reports whether you’re actively using a coding-related app (Terminal, VS Code, etc.) to a server you control, and serve a “coding”/“not coding” badge on your profile page; (could even detect which project you’re working on, and display that;) 2. Write an Apple Watch app that periodically reports whether you’re asleep, and serve a “sleeping”/“awake”/“unknown”…
Unrelated badge ideas: 1. Write a watcher that periodically reports whether you’re actively using a coding-related app (Terminal, VS Code, etc.) to a server you control, and serve a “coding”/“not coding” badge on your profile page; (could even detect which project you’re working on, and display that;) 2. Write an Apple Watch app that periodically reports whether you’re asleep, and serve a “sleeping”/“awake”/“unknown”…
Sounds like Discord.
Unrelated badge ideas: 1. Write a watcher that periodically reports whether you’re actively using a coding-related app (Terminal, VS Code, etc.) to a server you control, and serve a “coding”/“not coding” badge on your profile page; (could even detect which project you’re working on, and display that;) 2. Write an Apple Watch app that periodically reports whether you’re asleep, and serve a “sleeping”/“awake”/“unknown”…
Everything old is new again. I used this same technique on MySpace 15 years ago. I wonder if Github will try to filter that out the same way MySpace did back in the day.
I did some research before writing an article. GitHub started proxying images in 2014, and there are a lot of repositories that use this technique to keep their stats. I think GitHub is OK with that.
>Unlike GitHub, most of them don't even bother proxying the image to hide IP, referrer, and browser agent. If you want to allow external images on your site, you must proxy them and hide everything about a person who requested it. > A person with bad intentions can trick a victim into opening your profile that looks completely legit and detect his IP and a browser.
Can you explain this in more detail? Given a profile host that doesn't proxy, how does that attack work?
Which exact headers are being leaked by GitHub? Depending on what they leak, this could be something only useful for counting hits (if all they leak is the implicit time of the request), or for fully tracking users (if they leak Etags, original IPs, etc). It's too bad the author removed the badge from their Github profile. It would be interesting to see the effect of this post on profile views.