bernaferrari
commented
4 years ago Uh, that's a good idea! I'll keep that in mind when I start rewriting the app in close future (i.e. As soon as compose gets stable)
On Wed, Jun 3, 2020, 11:03 andreymal notifications@github.com wrote:
Some people practice a method of information publishing called warrant canary https://en.wikipedia.org/wiki/Warrant_canary: if some info is present and/or periodically updated, then everything is fine, but if it's not updating or even disappeared, it means that something bad happened.
Use case for websites:
-
website admin publishes a text file containing something like "2020-06-03 I'm alive, yay";
the admin updates this file everyday ("2020-06-04 I'm still alive");
if there are no updates for a few days (or the website has been simply disabled for non-payment), it means that something bad happened with the admin;
in this case, it would be good to be notified that something bad happened.
The Change Detection app has already implemented almost everything for this use case (it already checks files periodically); it remains only to add an option of the maximum permissible period of no change. Therefore, I leave this feature request here.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/bernaferrari/ChangeDetection/issues/41, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACVXFNI4GSAAKGCBTLUKPLRUZJ2HANCNFSM4NRWJVFA .
Some people practice a method of information publishing called warrant canary: if some info is present and/or periodically updated, then everything is fine, but if it's not updating or even disappeared, it means that something bad happened.
Use case for websites:
website admin publishes a text file containing something like "2020-06-03 I'm alive, yay";
the admin updates this file everyday ("2020-06-04 I'm still alive");
if there are no updates for a few days (or the website has been simply disabled for non-payment), it means that something bad happened to the admin;
in this case, it would be good to be notified that something bad happened.
The Change Detection app has already implemented almost everything for this use case (it already checks files periodically); it remains only to add an option of the maximum permissible period of no change. Therefore, I leave this feature request here.