4 ms·
On 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 us
by School-Cotton 1y ago
On 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...
- colechristensen 1y agoYou can turn those GitHub security warnings off if you don't want them. >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 Yes I've also gotten an email from Amazon saying they revoked a key someone inadvertently leaked (but so long ago I only remember that it happened). I read my AWS emails at least.
- 4hg4ufxhy 1y agoWhat would be the issue with global lock? I think repo creation is a very rare event when measured in computer time.
- progval 1y ago> but github may have a feed of new repos anyway? Yes: https://docs.github.com/en/rest/repos/repos?apiVersion=2022-11-28#list-public-repositories https://docs.github.com/en/rest/repos/repos?apiVersion=2022-... (you can filter to only show repositories created since a given date).
- tough 1y agoand using their obscure graphql api, you can do the same for -new commits- across any repos. they have some secret leaking infra for enterprise
- xboxnolifes 1y agoCompanies usually hide this type of information so competitors have a harder time determining if they are growing/shrinking/neutral.
- cheschire 1y agoWhen your moat is a billion wide, you tend to walk around in your underwear a bit more I guess.
- 90s_dev 1y agoExcellent Diogenes quote reference.
- sebastiennight 1y agoDo you mean a specific quote here? I couldn't find the reference.
- 90s_dev 1y agoThe answer to that question is in the eye of the beholder or something idk
- sebastiennight 1y agoI'd have thought Diogene's moat was mostly personal-fragrance-based
- NooneAtAll3 1y agounless you're youtube?
- paulddraper 1y agoYou can see the rate of creation of new users too. Which is arguably even more interesting…
- beaugunderson 1y agoand you can find the latest ID incredibly quickly using binary search! (I used to track a bunch of websites' growth this way)