Problem: Sometimes, a package owner adds a package to anitya, but the pkgdb monitoring flag is False. Anitya finds a new version, broadcasts it, and the-new-hotness drops it, since the monitoring flag is false. Shortly thereafter, the package owner turns the monitoring flag on, but there is nothing to trigger the-new-hotness to do anything until the next release upstream happens.

the-new-hotness could listen for pkgdb messages indicating that monitoring was turned on at which point it could go and actively query anitya to see if it should file any bugs, etc.