Use a time based cache on the frontend, so the API doesn't need to respond all of the time.
Yes, I'm aware that you could just extract the API URL and just hammer it with a custom program, but most users would probably not do that. This is just one line of defense. There are other measures in place on the API-level and on the VPS-level.
Use a time based cache on the frontend, so the API doesn't need to respond all of the time.
Yes, I'm aware that you could just extract the API URL and just hammer it with a custom program, but most users would probably not do that. This is just one line of defense. There are other measures in place on the API-level and on the VPS-level.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Use a time based cache on the frontend, so the API doesn't need to respond all of the time.
Yes, I'm aware that you could just extract the API URL and just hammer it with a custom program, but most users would probably not do that. This is just one line of defense. There are other measures in place on the API-level and on the VPS-level.
Done in this issue