-
Notifications
You must be signed in to change notification settings - Fork 128
502 on homepage on long streak #370
Comments
😞 Why always mess with the system in the first place? (Rhetorical question, needs no answer.) I apologize in advance, but... Don't misinterpret my comment as me not liking you personally or whatnot, you're probably a nice guy when you're not faking commits. 😉 |
BTW since I don't know if you knew:
Edit:
|
@bwin my goals are:
They are all purely for the lolz, non important, and will likely not be furthered by my actions 😉
Yup, I always do: #182 But I bet at least one GitHubber reads this repo. |
😉 |
That's a unique way to hide your identity by slaying unicorns. And according to Github, it isn't a bug, but feature:
Deal with it! |
@NARKOZ GitHub's definition of "bug" is quite strict if they don't consider 502 as bugs 😄 I could also make it 1000 years in the past if they like 😉 Can you point to where did you got the quote from just for reference? Or was it a support request that you've made? |
@cirosantilli excerpt from a support ticket. |
Assuming they calculate the streak by walking backwards from the current date, I'd say they could probably fix this by bailing out once it reaches February 29, 2008 (the date CrunchBase lists as the founding of GitHub). |
And it definitely should be fixed. Isn't something that triggers 502 errors a vector for Denial-of-Service attacks (as it indicates that the server has crashed)? |
@stuartpb you're a genious! I think that in the past this might haven been usable to DoS other people because commits are only considered by email and are perfectly falsifieable! @github: sorry, I hadn't noticed that this had DoS potential against others Right now, GitHub seems to have pushed a hotfix for that already? https://github.com/cirosantilli-puppet is maxing out at 1000 days: https://github.com/cirosantilli-puppet on a streak from 1990 to 2020 Not sure why 1000, maybe a random maximum number? Also note that there are two empty days before the green days: hovering on them does not say no activity like the others. But this introduced the bug that commits in the future appear as "authored just now": GitHub shouldn't modify commit data like that, it's confusing: The real solution is to consider the timestamp of when the commit was pushed for the streak, cache things properly as they are pushed / process things asynchronously and show whatever data is in the repo on the commits. |
That's true, but I was thinking in terms of DDoSing all of GitHub by making every server spin and crash doing this instead of handling requests. That's a crazy idea, though: destroy the contribution graph for any user by pushing a fake repository with fake commits. (Maybe GitHub should start only counting signed commits as contributions, for repos the user isn't marked as a contributor to?) |
Indeed, it would appear GitHub already doesn't track contributions on repos you don't own: I just pushed 10000+ commits by cirosantilli-puppet to https://github.com/stuartpb/test-streak and they haven't moved the needle on https://github.com/cirosantilli-puppet. |
The same reason why @GoogleCodeExporter's contributions don't count. |
Streak is dead. Long live streak: https://github.com/blog/2173-more-contributions-on-your-profile |
https://github.com/cirosantilli unicorns most of the times http://i.imgur.com/y2v7N11.png (not always) because of my huge 100 year long computationally generated streak: https://github.com/cirosantilli/test-streak
Inspired by http://stackoverflow.com/questions/20099235/who-is-the-user-with-the-longest-streak-on-github
EDIT: I have pushed a 1000 year streak later: https://github.com/cirosantilli/test-streak-1000
The text was updated successfully, but these errors were encountered: