Show HN: Ghuser.io – Complete GitHub profiles(github.com) |
Show HN: Ghuser.io – Complete GitHub profiles(github.com) |
- I can't see all your code contributions since the beginning of time at a glance.
- For each of your pinned repos, I can't tell at the first glance whether you just fixed a typo or you wrote 90% of it.
ghuser.io tries to close this gap. You can show off with your entire GitHub "portfolio" and it gets refreshed every day.
And hopefully this is temporary. The best for the community would be to have all this directly on GitHub. The sooner ghuser.io can be switched off, the better ;)
I didn't expect to reach this point so fast (thanks!). I'll work on improving this right after this wave of new users. For now, just making sure that you all get your profile.
I'm still optimistic that Microsoft will be keen to make some quality-of-life improvements when they take the wheel, as a show of good faith.
Taking a few minutes now to display a temporary message that we're a bit overloaded.
It would also be really cool if we could pull out basic private repo info as well (with the user's permission). E.g. Worked on X private repos covering 60% Go, 20% Javascript etc.
I am also a bit confused as to why you would build this if you don't work at github?
Yes totally. Although we currently think that the best for the community is GitHub improving their GitHub profiles making ghuser.io obsolete. Right now we'd rather do this with GitHub and not against GitHub. But we don't know how much GitHub is willing to help us. (We need changes to the GitHub APIs for ghuser.io to be scalable.)
> private repo
Yea we could do that as well. Give permission to our public key and we're good to go.
> why you would build this if you don't work at github?
Because Aurelien (OP) wanted/needed that so he just built it.
To the both of us it's basically a fun experiment.
Also for me it's cool because we use the web framework Reframe (https://github.com/reframejs/reframe) which I'm currently building.
Many many thanks!
We talked with GitHub already. They think that what we are doing is cool and we agreed to tell them our roadmap and they tell us theirs.
We would be glad if GitHub copies us.
If you have user requests in the logs, you should queue them up.
(And can I cancel my request so you can move on to others for now?)
What is your username? I'll cancel your request, thanks!
For better control over the throttle and concurrency you can leverage dynamodb... I love it for controlling lambdas but not for storage.
If you need more power than a lambda then you can do a similar process with EC2. Populate the SQS Trigger the aws lambda to turn on EC2 machine. Consider spot instances to save a ton of money.
If you need ideas I’m sure HN readers would be glad to help solution for afar.
grafana/.github/CONTRIBUTING.mdDetails at https://github.com/AurelienLourot/github-contribs#how-does-i...
We are in talks with GitHub and they know that we are crawling GitHub.
It uses a very slow non-official GitHub API and so it takes several hours to do the initial crawling of one single profile, and is limited by IP so you need several machines/instances in order to parallelize. We plan to use AWS Fargate for the future. (We thought this future would be much farther away)
https://cloud.google.com/blog/products/gcp/introducing-headl...
E.g. https://api.github.com/repos/aurelienlourot/ghuser.io/contri...
I'm surprised to hear that you're bottlenecking on CPU time. Could you verify that my understanding is correct? I would've thought your bottleneck would be networking and connectivity as you have to wait for GitHub to process all of the requests.
The GitHub's unofficial API we are using is slow and per IP rate limited. We spin up several servers to have several IPs to circumvent the rate limit.
(GitHub knows that we do that and we are in contact with them.)
Surely a rate-limit exception could be in order, then?
And perhaps you could help them alpha-test a new API endpoint that just so happens to include all the info rolled up as one URL :D
(Hmmmmm.... GraphQL....)