Implement a backoff strategy for stream status queries to offline instances. #3

New Issue

2025-04-03T13:28:45-04:00

LogalDeveloper commented

2025-04-03 13:28:45 -04:00

Currently, the bot queries stream status every minute without any variation. This routine does not account for situations where an instance goes offline for an extended period of time. A backoff strategy should be implemented which gradually increases the query interval when an instance is consistently detected as offline.

The maximum query interval needs to be selected carefully. Some streamers only run their instances during active streaming sessions and intentionally take it offline after. The maximum query interval needs to balance reducing unnecessary network traffic and ensuring instances with regular long downtime aren't missed. A value of 15 minutes may be sufficient.

Finally within this topic, it may be worth properly handling code 429 HTTP responses. Owncast does not implement rate limiting on its own and I have not seen this code in the wild, but instances can always be hosted behind reverse proxies which enforce their own policies.

Currently, the bot queries stream status every minute without any variation. This routine does not account for situations where an instance goes offline for an extended period of time. A backoff strategy should be implemented which gradually increases the query interval when an instance is consistently detected as offline. The maximum query interval needs to be selected carefully. Some streamers only run their instances during active streaming sessions and intentionally take it offline after. The maximum query interval needs to balance reducing unnecessary network traffic and ensuring instances with regular long downtime aren't missed. A value of 15 minutes may be sufficient. Finally within this topic, it may be worth properly handling code 429 HTTP responses. Owncast does not implement rate limiting on its own and I have not seen this code in the wild, but instances can always be hosted behind reverse proxies which enforce their own policies.

LogalDeveloper added the Enhancement label 2025-04-03 13:28:45 -04:00

LogalDeveloper referenced this issue from a commit

2026-01-06 18:15:58 -05:00

Added progressive backoff and auto-cleanup for unreachable Owncast instances. (Closes #2 and #3)

LogalDeveloper referenced this issue from a commit

2026-01-06 18:16:49 -05:00

Added progressive backoff and auto-cleanup for unreachable Owncast instances. (Closes #2 and closes #3)

LogalDeveloper closed this issue

2026-01-06 18:16:49 -05:00

Sign in to join this conversation.