spanglelabs / gif_pipeline Goto Github PK

Subscriptions are more unreliable than I initially thought, and deleting unreliable subscriptions seems suboptimal, as we will lose the information on which subscriptions did exist, and where subscriptions were up to.

As an example, tiktok subscription checks (using yt-dlp) are unreliable, but work once a day or so, which is fine.
Instagram subscriptions are completely broken, as bibliogram has been discontinued now. But I would rather keep them in the database in case a new solution appears some day.

It would be better if subscriptions just counted up the number of consecutive failures, and said that when listing subscriptions, and zeroed it out when a subscription check works.

I pondered whether it should say when a check fails the first time, or fails the 10th or 100th time, but it's not that important, that seems like a tuning issue I would rather avoid