Github API rate limiting issue

[metrue]

Github REST API enables the rate limit, in the current implementation, tinymind will fetch the content via GitHub API for each blog browsing, and it will easily reach the rate limit threshold.

There're two major options to fetch content from GitHub: Webhook or Fetch Queue. It'd better to investigate and improve the fetching logic.

https://docs.github.com/en/rest/using-the-rest-api/rate-limits-for-the-rest-api?apiVersion=2022-11-28
https://docs.github.com/en/rest/using-the-rest-api/best-practices-for-using-the-rest-api?apiVersion=2022-11-28

[mazzzystar]

I understand that it seems like:

• For public repositories, the rate limit counts against the browser's IP address as the basis for API rate limit, meaning each user has 60 access attempts per hour.
• For private repositories, using auth key allows for a limit of 5,000 requests per hour, which I feel might be barely sufficient when the number of users is not high.

[metrue]

For public repositories, the rate limit counts against the browser's IP address as the basis for API rate limit, meaning each user has 60 access attempts per hour.

I frequently get blocked by the rate limiting quota during the development, I think it's because there're too much hot reloading and fetching data too frequently, especially I have some client data request added to my version codes.

For private repositories, using auth key allows for a limit of 5,000 requests per hour, which I feel might be barely sufficient when the number of users is not high.

Fetching with auth key is enough but it's for the login visitors (basically they are the bloggers), for the blog visitors most of them are not random anonymous without the auth key so when a site become popular, the rate limiting will be a issue I think.