Love this!! Is there a reason why you chose to not display repository information like the language breakdown or tags? Messing with the sidebar might also be an opportunity to expand the capabilities of the interface, like including a star-chart or LOC.
And there's a number of alternative front-end lists out there that I would submit to if you all are serious about it, and make instructions easy on self-hosting.
This was a hackathon project so we prioritized core features. We're going to add more features soon.
I looked at the gothub, I'm not fully sure their approach but if they're just scraping the data you hit rate limits pretty fast and you'd have to use proxies. They also don't seem to have full feature parity with Github which is our end goal.
In terms of self-hosting we will add instruction but our vision is mostly people using our hosted version. A lot of the optimization comes from the caching.
This was made for a hackathon, we were going to have pr resolving features which requires write access. At current state you're right the write access is not required but we're adding features that require write access very soon.
Love this!! Is there a reason why you chose to not display repository information like the language breakdown or tags? Messing with the sidebar might also be an opportunity to expand the capabilities of the interface, like including a star-chart or LOC.
Thank you for the awesome project! I wonder if you have seen Gothub? https://codeberg.org/gothub/gothub
And there's a number of alternative front-end lists out there that I would submit to if you all are serious about it, and make instructions easy on self-hosting.
This was a hackathon project so we prioritized core features. We're going to add more features soon.
I looked at the gothub, I'm not fully sure their approach but if they're just scraping the data you hit rate limits pretty fast and you'd have to use proxies. They also don't seem to have full feature parity with Github which is our end goal.
In terms of self-hosting we will add instruction but our vision is mostly people using our hosted version. A lot of the optimization comes from the caching.
You can check out the source code — on gitfaster: https://gitfaster.dev/Krish120003/gitfaster
also change any github link to githubf and you can view it in our app.
Why do I need to share my GitHub info -- with write access! -- to view the source?
This was made for a hackathon, we were going to have pr resolving features which requires write access. At current state you're right the write access is not required but we're adding features that require write access very soon.
Do your site need me to sign in, to use. Cause if it does, I could just use github.dev
yes because this was made for a hackathon, but we're working on adding no sign in viewing for public repos as well.