-
-
Notifications
You must be signed in to change notification settings - Fork 132
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
api key donations #125
Comments
I've sent the first key! Let's keep this running. If we get enough keys, please consider implementing per-key rate limit (lower than GitHub's) on the client side (maybe using redis that you already have) so that the other 3rd party GitHub apps and personal access tokens people installed are not disrupted due to donating a key to Starchart.cc. |
sent a new one 👍🏼 |
i sent a key |
just send one |
One from me too :) |
one from me |
👍 |
one from me 👍🏻 |
Just sent a new 🔑 |
Have shot an email. Guess I'm num.10 :) |
Thanks everyone! Should be enough to start... I have metrics so I'll keep an eye and see how it goes. FWIW, here's the round robin impl: #126 |
Signed-off-by: Carlos Alexandro Becker <[email protected]>
👍 |
Hey, as a feedback, we are much more stable now! and token usage is pretty low after I started failing-fast repos with more than 40k stars (which github does not let scan all pages anyway): So I think we should be good for now! If someone wants to help writing a new frontend, let me know and let's work together 🙏 |
Ah, and thanks again for everyone that jumped in to help on this 🤘 |
hey @santiesque, sure thing, thanks for the help 🙏 |
Thanks @santiesque 🙏 |
I think this can be closed now. Thanks again everyone! |
Ok, since rate limit is always hitting, even after the recent efforts using etag and more redis memory for caching... @ahmetb come with an idea of having a pool of api keys.
So, this is issue is where we're going to do so.
The API key needs no permissions, and if you want to help, you can share yours via email at
carlos <at> becker.software
I'll implement the code to round-robin and mark keys as "bad" in the following days.
We can also come up with some way of saying "thanks" to the key donors either here in the repo or in the website, so if you want your name to show up, please let me know in the email as well.
If you are good with frontends, I really need some help doing a "makeover" of our current frontend as well :) #124
The text was updated successfully, but these errors were encountered: