Hello everyone, I've noticed that some PubSubHubbub users are not implementing the "Automatic Subscription Refreshing" as we expect and do not echo the challenge again once a subscription has been confirmed for a long time. They may even not keep track of the past subscriptions on their end... or even return 404 in case of downtime. Unfortunately, that's not their intent.
A simple fix (that we implemented) is to actually check the subscription first, and in case of non-confirmation, check that the callback wants to unsubscribe. If subscribe is not confirmed and unsubscribe is confirmed, then, the hub can safely delete the subscription. If not, it should keep checking both. What do you guys think? Julien
