7 ms·
Congratulations on creating the one billionth repository on GitHub
- bitpush 1y agocurl -s https://api.github.com/repositories/1000000000 https://api.github.com/repositories/1000000000 { "id": 1000000000, "node_id": "R_kgDOO5rKAA", "name": "shit", "full_name": "AasishPokhrel/shit" }
- deleted 1y ago[deleted]
- samgranieri 1y agoWell shit!
- mistersquid 1y agoIs this what folks mean by enshittification?
- arcanemachiner 1y agoFor anyone wondering, the name of the repo is literally "shit".
- Cyphase 1y agoI'm wondering if AasishPokhrel created this repo for the purpose of being the billionth.
- joshdavham 1y agoI highly doubt it, but that does sound possible.
- paxys 1y agoIt's pretty easy to game this. Just keep creating repos till you hit # one billion and remove the old ones. Their API makes it trivial. The only issue will be rate limits, and other people simultaneously creating repos, so it's a matter of luck.
- recursive 1y agoI don't believe they will renumber the old ones. Also, it can't be trivial, since two people can try this, and only one can win.
- handfuloflight 1y agoThere is always one trillion to look forward to!
- hu3 1y agobogus aí agents stuck in loops will get us there soon enough
- deleted 1y ago[deleted]
- Macha 1y agoThe one who lost doesn't get discussed in this thread.
- recursive 1y agoYes, but that doesn't make it trivial.
- GodelNumbering 1y agoThere was a guy who got fired from Meta for creating excessive automated diffs in pursuit of a certain magic number
- paxys 1y agoI hope PR #80085 was worth it.
- fancyswimtime 1y ago69 doesn't seem excessive
- maniacalhack0r 1y agoAasishPokhrel made 2 repos yday - shit and yep. no activity between may 17th and june 10th. i have no idea if its possible to calculate the rate at which repos are being created and time your repo creation to hit vanity numbers
- kylehotchkiss 1y agoI think he’s in university for software development in Nepal, and it’s really touching that a milestone could go so deeply into the world. Hopefully he has a big spot for this on his resume and can find a great career in development!
- netsharc 1y agoI don't get why this needs a big spot in his resume, and why it should lead to a great career. A company/hiring manager that thinks being lucky to hit a magic number on some system has any relevance to work, I'd rate as very insane...
- mkagenius 1y agoI will be really sus of someone's intelligence if they mentioned this as an achievement. It's fine as a joke, though.
- notfed 1y agoI find a bit of humor in the fact that this is completely unrequited attention. There's even a chance the guy is oblivious.
- deadbabe 1y ago[flagged]
- PenguinRevolver 1y agohttps://api.github.com/repositories/999999999 https://api.github.com/repositories/999999999 Which leads to https://github.com/sameepabadhuge/fork1 https://github.com/sameepabadhuge/fork1
- deadbabe 1y agoThat repo is substantially more fascinating, and could have used the attention. What a shame. Who was the next repo, 1,000,000,001?
- KTibow 1y agoIt doesn't exist. Turns out GitHub has a lot of private and deleted repos. (Then there's 1000000002, https://github.com/minseon-01/flaskapp https://github.com/minseon-01/flaskapp, similar to 999999999 in that it's a fork)
- ihuman 1y agoRight now it 404s. 1000000002 is https://github.com/minseon-01/flaskapp https://github.com/minseon-01/flaskapp
- levocardia 1y ago>Repo 999999999: pushing forward the cutting edge of protein folding research >Repo 1000000000: shit
- TZubiri 1y agoThe duality of programming
- SalariedSlave 1y agoSo the count includes forks? Would be interesting to know the billionth non-fork source repo.
- fHr 1y agorepo named shit LMFAO nice
- joshdavham 1y agoThis is actually incredible.
- School-Cotton 1y agoOn a serious note, I'm a bit surprised that GitHub makes it trivial to compute the rate at which new repositories are created. Isn't that kind of information usually a corporate secret?
- raincole 1y agoIs there any reason for GitHub to hide this information though? How could it be used against them? (I understand many companies default to not expose any information unless forced otherwise.)
- toast0 1y agoThe rate of creation is like meh, but being able to enumerate all of the repos might be problematic, following new repos and scanning them for leaked credentials could be a negative... but github may have a feed of new repos anyway? Also, having a sequence implies at least a global lock on that sequence during repo creation. Repo creation could otherwise be a scoped lock. OTOH, it's not necessarily handled that way --- they could hand out ranges of sequences to different servers/regions and the repo id may not be actually sequential.
- colechristensen 1y ago>following new repos and scanning them for leaked credentials could be a negative People do this. GitHub started doing it too so now you get a nice email from them first instead of another kind of surprise.
- mdaniel 1y agoEmail, bleh, I'm sure I'm not the only one who basically /dev/null's emails from github about pearl-clutching "security" but I wanted to point out that for quite a few providers they actually have an integration to revoke them if found in a public repo, which I think is way more handy https://docs.github.com/en/code-security/secret-scanning/secret-scanning-partnership-program/secret-scanning-partner-program#the-secret-scanning-process https://docs.github.com/en/code-security/secret-scanning/sec... and the list is way bigger than I recalled: https://docs.github.com/en/code-security/secret-scanning/introduction/supported-secret-scanning-patterns#default-patterns https://docs.github.com/en/code-security/secret-scanning/int...
- jaynate 1y agoThe repo three comma club
- 9dev 1y agoSigh. You can't make that shit up. I'm sure there's a witty metaphor in there, somewhere…
- 8organicbits 1y agoWhile we are doing cool GitHub repo IDs, the first is here: https://api.github.com/repositories/1 https://api.github.com/repositories/1 https://github.com/mojombo/grit https://github.com/mojombo/grit
- deleted 1y ago[deleted]
- Aachen 1y agoMakes me wonder how many repositories exist in general, from all the local Forgejo and Gitlab servers. Heck, include Subversion and Mercurial and git's other friends (and foes!) Did anyone make a search engine for these yet, so we'd be able to get an estimate by searching for the word "a" or so? (This always seemed like the big upside of centralised GitHub to me: people can actually find your code. I've been thinking of making a search since MS bought GH but didn't think I could do the marketing aspects and so it would be a waste of effort and I never did it. Recently I was considering whether this would be worth revisiting, with the various projects I'm putting on Codeberg, but maybe someone beat me to the punch)
- mdaniel 1y agoWell, based on the API enumeration mentioned in sibling comments, surely one doesn't have to estimate https://docs.gitlab.com/api/projects/#list-all-projects https://docs.gitlab.com/api/projects/#list-all-projects (for dumb reasons it seems GL calls them Projects, not Repositories) https://codeberg.org/api/swagger#/repository/repoGetByID https://codeberg.org/api/swagger#/repository/repoGetByID (that was linked to by the Forgejo.org site, so presumably it's the same for it and Codeberg) and its friend https://gitea.com/api/swagger#/repository/repoGetByID https://gitea.com/api/swagger#/repository/repoGetByID Heptapod is a "friendly fork" of GitLab CE so its API works the same: https://heptapod.net/pages/faq#api-hgrc https://heptapod.net/pages/faq#api-hgrc and then I'd guess one would need to index the per-project GitLab instances: Gnome, GNU (if they ever open theirs back up), whatever's going on with Savannah, probably Sourceforge, maybe sourcehut (assuming he doesn't have some political reason to block you), etc If I won the lottery, I'd probably bankroll a sourcegraph instance (from back when they were Apache) across everything I could get my hands upon, and donate snapshots of it to the Internet Archive
- progval 1y agoAt Software Heritage, we listed 380M public repositories, 280M of which are on Github: https://archive.softwareheritage.org/ https://archive.softwareheritage.org/ Repository search is pretty limited so far: only full-text search on URLs or in a small list of metadata files like package.json.
- 90s_dev 1y agoThis is either staged, or incredible commentary on most github repos, having no purpose, never being realized, and even having given up dreaming.
- kristopolous 1y agoHonestly I think the plurality are by students, maybe even the majority. When I was a student I had to manually set up CVS pserver and CVSWeb to collaborate with other students on assignments. This is a bit easier by at least a few orders of magnitude.
- MindTheAbstract 1y agoI really hope it's the latter, that would be quite brilliant
- 90s_dev 1y agoI don't mean intentionally. I mean maybe he made that repo because he'd given up on his coding dreams. Almost. That would be some interesting accidental meta commentary on the state of things.
- deleted 1y ago[deleted]
- extraduder_ire 1y agoI think, by design, every commit in git is staged.
- 90s_dev 1y agoWow.
- caleblloyd 1y agoAwesome! Only a little over a billion more to go before GitHub’s very own OpenAPI Spec can start overflowing int32 on repositories too, just like it already does for workflows run IDs! https://github.com/github/rest-api-description/issues/4511 https://github.com/github/rest-api-description/issues/4511
- bartread 1y agoThe company where I did my stint as CTO I turned up, noticed they were using 32-bit integers as primary keys on one of their key tables that already had 1.3 billion rows and, at the rate they were adding them, would overflow on primary key values within months… so we ran a fairly urgent project to upgrade the IDs to 64-bit to avoid the total meltdown that would have ensued otherwise.
- hobs 1y agoheh, that's happened at at least 5 companies I have worked at - go to check the database, find - currency as floats, hilarious indexes, integers gonna overflow, gigantic types with nothing in them.
- rudasn 1y agoI bet you haven't seen indeces on decimals though! Fun times :)
- azophy_2 1y agoJust curious as someone with limited experience on this. Whats wrong with it? decimal is consistent & predictable (compared than float), so it shouldn't be that big of a deal right? CMIIW
- rudasn 1y agoYeah, not a big deal but completely useless nonetheless as you would never really query your table for just the one decimal column (eg the price) but a couple more (eg the category and the price) so you'd have a multi-column index on those columns. The index on just the price column never gets used.
- Drblessing 1y agoImagine if this was private. We would've lost out on this glorious moment.
- jonplackett 1y agoHoly shit, that’s amazing.
- Aachen 1y agoReminds me of the 100 millionth OpenStreetMap changeset (commit). A few people, myself included, were casually trying for it but in the end it went to someone who wasn't trying and just busy mapping Africa! Much more wholesome, seeing it with hindsight. This person was also previously nominated for an OSM award. I guess it helps that openstreetmap doesn't really allow for creating crap, because it's all live in production, and that's how the Nth commit is way more likely to be someone's random whim? Either way, a fun achievement for Github :) In case anyone cares to read more about the OSM milestone, the official blog entry: https://blog.openstreetmap.org/2021/02/25/100-million-edits-to-openstreetmap/ https://blog.openstreetmap.org/2021/02/25/100-million-edits-... My write-up of changeset activity around the event: https://www.openstreetmap.org/user/LucGommans/diary/395954 https://www.openstreetmap.org/user/LucGommans/diary/395954
- chneu 1y agoYour kind of comment is exactly why HN still rules. What a fun story. Thanks for sharing
- Aachen 1y agoAww, thanks! I wasn't sure if I should go off-topic this much so I'm happy to hear this!
- ash_091 1y agoA friend of mine spent an entire workday figuring out how to ensure he created the millionth ticket in our help desk. Not sure how he cracked it in the end but we had a little team party to celebrate the achievement. This was probably fifteen years ago. I feel like working in tech was more fun back then.
- lbeckman314 1y ago> https://ohshitgit.com https://ohshitgit.com
- hyperhopper 1y agohttps://stevelosh.com/blog/2013/04/git-koans/ https://stevelosh.com/blog/2013/04/git-koans/
- deleted 1y ago[deleted]
- zaps 1y agoRespect to GitHub for committing to the bit
- Lammy 1y agocheck 'em https://knowyourmeme.com/memes/dubs-guy-check-em https://knowyourmeme.com/memes/dubs-guy-check-em
- mstridder1 1y ago[flagged]
- CGamesPlay 1y agoProbably created via a script that just repeatedly checked https://api.github.com/repositories/999999999 https://api.github.com/repositories/999999999 until it showed up, and then created a new repository. Since repositories can be modified, could have even given it some buffer and created a bunch of repos, just delete the ones that don't get the right number. [append] Looking at the author's other repo created yesterday, I'm betting "yep" was supposed to be the magic number, and "shit" was an admission of missing the mark. Does anyone remember D666666 from Facebook? It was a massive codemod; the author used a technique similar to this one to get that particular number.
- topherPedersen 1y agoYou solved the mystery!
- notfed 1y agoOr...not. Why are you assuming this guy purposely grabbed the repo?
- CGamesPlay 1y agoMostly just to share an approach to solving the "problem" of getting memorable numbers from a pool of sequential IDs. But given that this user doesn't have activity very often, and created two repositories as the number was getting close, it feels likely that it was deliberate. I could be wrong!
- ramon156 1y agoEmpty repo, so yes
- JKCalhoun 1y agoI wish I were still at Apple. Probably most people here know that Apple uses an internal tool called "Radar" since, forever. Each "Radar" has an ID (bug #) associated with it. Radars that were bug #1,000,000, etc. were kind of special. Unless someone screwed up (and let down the whole team) they were usually faux-Radars with lots of inside jokes, etc. Pulling up one was enough since the Radar could reference other Radars ... and generally you would go down the rabbit hole at that point enjoying the ride. I was a dumbass not to capture (heck, even print) a few of those when I had the opportunity.
- xmprt 1y ago> I was a dumbass not to capture (heck, even print) a few of those when I had the opportunity. On the other hand, given how Apple deals with confidential data, you probably wouldn't want to be caught exfiltrating internal documents however benign they are.
- msarnoff 1y ago#SnakesOnARadar
- bjackman 1y agoAt Google, the monorepo VCS has monotonic IDs like this for changes. Unfortunately a few years ago when approaching some round number, the system was DOS'd by people running scripts trying to snag the ID. So now it skips IDs in the vicinity of big round numbers :( I think there's probably a lesson in there about schema design...
- almosthere 1y agofacepalm
- bigbuppo 1y agoAww, he renamed it from shit to historic-repo.
- Sohcahtoa82 1y agoThe repo seems to have gotten renamed and now redirects to https://github.com/AasishPokhrel/repository/ https://github.com/AasishPokhrel/repository/ Lame. :-(
- Sohcahtoa82 1y agoIt was renamed back! :-D
- nojs 1y agoHaha, he’s renamed it from “shit” to “repository” which makes the comments less funny
- lillecarl 1y agoReadme still has shit in it
- jonasdegendt 1y agoCheck 'em! Sick dubs :^)
- ChoGGi 1y agoThat's a perfect one billion repo.
- hoppp 1y agoNerd humor is funny as shit