+1 to everything Julien wrote. Subscribers shouldn't rely on the hub doing automatic renewals.
I should also add that we are rolling out a new version of pubsubhubbub.appspot.com. It has quite a few bug fixes including correct handling of subscription expiration. That's why you may see many of your subscriptions suddenly expiring. Roman. On Tue, Feb 12, 2013 at 9:15 AM, Julien Genestoux < [email protected]> wrote: > David, > > As of 0.3, the best practice is to not rely on the hub to renew > susbcriptions pro-actively. > Some hubs (like Superfeedr) will just send confirmation again when the > renewal date approaches... and some other (like the Google Hub) > will rely only on the subscriber's renewal. > > For 0.4 we took the same approach: subscriptions belong to subscribers, so > they should make sure they're in order... It is relatively easy for > hubs to keep track of expiration and poke the subscribers too, but it's > also quite costly for "dead" feeds to which someone may stay subscribed. > > At Superfeedr, we're thinking about including a X-... header to > notifications as a way indicate when a subscription will expire. This will > be useful for subscribers to renew their subscriptions, while still > "garbage collect" dead feeds which will never trigger any notification. For > our paying customers, we also have an option to be notified on broken > feeds, and have a policy to never explicitly expire subscriptions... > > > I hope this helps! > > -- > Julien Genestoux > http://superfeedr.com > > > On Tue, Feb 12, 2013 at 12:12 AM, DCreemer <[email protected]> wrote: > >> Hi- >> >> I currently have several 10's of thousands of subscriptions active on >> pubsubhubbub.appspot.com, superfeedr, wordpress, and other hubs. >> Starting on Feb 6, I noticed that most of my subscriptions from >> pubsubhubbub.appspot.com stopped posting updates (other hubs continue >> just fine). Using the pubsubhubbub.appspot.com web ui, I noticed that >> many of the feeds I spot checked have an expiration time in the past (i.e. >> are expired). I see through recent messages on the group that the status of >> hub.lease_seconds is changing, and that it may not have been supported on >> the Google hub anyway. My endpoints currently see and correctly handle >> hub-initiated lease renewal requests. >> >> What is the current suggested best-practice for renewal (on both 0.3 and >> 0.4 spec hubs)? Should I always initiate re-subscriptions? >> >> Thanks, >> -- David >> >> -- >> >> --- >> You received this message because you are subscribed to the Google Groups >> "Pubsubhubbub" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > > -- > > --- > You received this message because you are subscribed to the Google Groups > "Pubsubhubbub" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- --- You received this message because you are subscribed to the Google Groups "Pubsubhubbub" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
