Anurag Hazra

> some kind of lightweight cache could be a solution thinking We already have caching, it's not the issue since the initial data wont even load because vercel would timeout.

> Just [bought @anuraghazra a coffee](https://www.buymeacoffee.com/anuraghazra) in the name of this issue (and as a general "thank you" for making this wonderful piece of software). Maybe if more people chip...

Hi @arthurlogilab yeah we do have some plans on supporting teams/orgs you can see #1 for more info.

@nthnchu Yeah i think it would be nicer to have a JSON API. What i was thinking is that instead of creating separate routes we can also use query param...

This is actually a brilliant idea & solves a lot of problems with data inaccuracies. But I'm just worried about the cost of the GraphQL query, since we are fetching...

> If we aren't a collaborator or member of team, the stars doesn't count. Only for repositories where I'm the owner. This IMO should be as is, I know this...

> What do you think adding a Cache layer? Once we get someone data, we prevent another calls and could contribute to not get again from GraphQL. We actually do...

We might do it.

We can probably explore that, the reason we choose our current design for the card is because we wanted to make it match the design of github's native language cards.

Okay I don't think this is from our end. Something is really messed up from github's side. It's returning error/HTML content on graphql api request  Note that it's only...