You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As an Invidious instance maintainer, it is hard to know whether my instance is really working. The invidious software might run just fine and return 200 responses even though it has been blocked by Youtube. It often takes some time to be aware that the instance is not loading Youtube videos.
This could be fixed by implementing an API endpoint that tells if Youtube has blocked the instance. This endpoint could be used then by an external uptime monitoring software like Uptime Kuma or Gatus. To achieve compatibility with different kinds of software, I wish the endpoint had a clear status code informing the blockage state (for example 503 - service unavailable).
The existing /api/v1/stats endpoint could be used for this. In my opinion the endpoint should also return some json data for other software indicating is the instance blocked, without needing to look into status codes.
{
"blocked": <boolean>
}
The text was updated successfully, but these errors were encountered:
If/when this is implemented, I would love to see it used on https://api.invidious.io/ too. It would help new users to find out that a specific instance is blocked currently.
As an Invidious instance maintainer, it is hard to know whether my instance is really working. The invidious software might run just fine and return 200 responses even though it has been blocked by Youtube. It often takes some time to be aware that the instance is not loading Youtube videos.
This could be fixed by implementing an API endpoint that tells if Youtube has blocked the instance. This endpoint could be used then by an external uptime monitoring software like Uptime Kuma or Gatus. To achieve compatibility with different kinds of software, I wish the endpoint had a clear status code informing the blockage state (for example 503 - service unavailable).
The existing
/api/v1/stats
endpoint could be used for this. In my opinion the endpoint should also return some json data for other software indicating is the instance blocked, without needing to look into status codes.The text was updated successfully, but these errors were encountered: