Open philbudne opened 4 months ago
I like the tristate idea, is this how you would imagine system_enabled working? 0 (❌) - Explicitly set to disable the feed. Used in staging database to limit polls as you mentioned. 1 (✅) - The feed is working (or has not yet hit the failure threshold). 2 (💀/💩/🧟) - Feed failure threshold hit (such as the current points system); polling is significantly reduced.
Adding a little tooltip on hover for the zombie/skull feeds to say something like Unable to reach feed - polling has been reduced
might be helpful. (or a legend somewhere)
@NullPxl suggested that instead of auto-disabling feeds, we instead poll them very slowly.
One concern is how to signal this status to users looking at the web search "catalog" of sources & feeds.
The crudest way to do this would be to continue to set
system_enabled
to false, but to only use it to control the upper limit of poll interval (that is, select an alternateMAXIMUM_BACKOFF_MINS
value, perhapsMAXIMUM_ZOMBIE_BACKOFF_DAYS
?). The UI could just display zombie or poop emoji instead of a red X.However,
system_enabled
is used in the staging database to limit the number of feeds that are actually polled. Adding asystem_undead
column boolean column, or makingsystem_enabled
a tristate would allow explicit disabling of feeds.