Huff, I understand your concern and I see 2 things you could do to aboid the problem easily: - support PubSubHubbub on the original feed - plug the original feed on The Old Reader directly.
That said, I understand the frustration. I hope this helps. Thanks -- *Got a blog? Make following it simple: https://www.subtome.com/ <https://www.subtome.com/>* Julien Genestoux, http://twitter.com/julien51 +1 (415) 830 6574 +33 (0)9 70 44 76 29 On Thu, Apr 10, 2014 at 5:56 PM, John Huffaker <[email protected]> wrote: > Thanks for all of your help and clear explanations! > > FeedBurner seems to auto-add a pubsubhubbub link to all feeds even if the > underlying one would rather rely on the polling model. If you look at the > differences in XML between the original feed ( > http://jmillerinc.com/newsyc100.xml) and the feedburner one (http://feeds. > feedburner.com/newsyc100) you can see that feedburner automatically adds > a <atom10:link xmlns:atom10="http://www.w3.org/2005/Atom"; rel="hub" href=" > http://pubsubhubbub.appspot.com/"; />. Which my feed reader > (theoldreader) then respects and waits for the notification and only > refreshes every 6 or so hours. I assume this is probably happening with > other burned feeds as well. > > It feels like a feedburner is the one that is making the mis-step in the > chain (or my expectation that a feed shouldn't have to implement > notifications and should be allowed to rely on polling). You guys know of > a different group/list that I can post this to for feedburner? > > Regards, > Huff > > > > On Wednesday, April 9, 2014 8:36:13 AM UTC-7, Roman Perepelitsa wrote: >> >> On Wed, Apr 9, 2014 at 5:00 PM, Julien Genestoux >> <[email protected]>wrote: >> >>> John, you should make that original feed PubsubHubbub first if you want >>> feedburner to propagate the updates too. >>> >> >> +1. >> >> Here's how FeedBurner works. >> >> Definition: source feed is a feed that publisher hosts. >> http://jmillerinc.com/newsyc100.xml is a source feed. >> Definition: burned feed is a feed that FeedBurner hosts. http://feeds. >> feedburner.com/newsyc100 is a burned feed corresponding to >> http://jmillerinc.com/newsyc100.xml. >> >> When a burned feed is requested from FeedBurner (usually by an RSS >> reader), it checks the age of the cached source feed. If it never >> downloaded the source feed or it's too old, FeedBurner downloads the source >> feed. Then FeedBurner serves the requested burned feed, which is >> essentially a transformed source feed (the set of transformations is >> specified by the owner of the burned feed in the FeedBurner UI). >> >> I believe by default FeedBurner will download the source feed if it's >> older than 30 minutes, but don't quote me on that. >> >> All burned feeds support PubSubHubbub with https://pubsubhubbub.appspot. >> com/ as the hub end-point, regardless of the source feed. Whenever the >> burned feed changes (that happens when FeedBurner detects changes in the >> source feed), it notifies https://pubsubhubbub.appspot.com/, which in >> turns notifies all subscribers of the burned feed. >> >> If the source feed supports PubSubHubbub (it can be any hub, no >> necessarily https://pubsubhubbub.appspot.com/), FeedBurner subscribes to >> changes. When the publisher notifies its hub about changes to the source >> feed, FeedBurner receives those notifications from the hub and instantly >> recomputes the burned feed. >> >> Summary: >> >> 1. If the source feed doesn't support PubSubHubbub, the burned feed >> will be up to 30 minutes behind the source feed. >> 2. If the source feed does support PubSubHubbub, the burned feed will >> always be up to date and FeedBurner will not have to poll it. >> >> HTH, >> Roman. >> >> >>> >>> >>> >>> -- >>> >>> *Got a blog? Make following it simple: https://www.subtome.com/ >>> <https://www.subtome.com/>* >>> >>> Julien Genestoux, >>> http://twitter.com/julien51 >>> >>> +1 (415) 830 6574 >>> +33 (0)9 70 44 76 29 >>> >>> >>> On Tue, Apr 8, 2014 at 8:30 AM, John Huffaker <[email protected]> wrote: >>> >>>> Thanks for looking into it! >>>> >>>> If it helps, the primary feed is: >>>> http://jmillerinc.com/newsyc100.xml >>>> >>>> On Monday, April 7, 2014 1:41:56 AM UTC-7, Roman Perepelitsa wrote: >>>> >>>>> Hi John, >>>>> >>>>> On Mon, Apr 7, 2014 at 9:23 AM, Julien Genestoux < >>>>> [email protected]> wrote: >>>>> >>>>>> John, >>>>>> >>>>>> The order of items does not create problem that I know of with most >>>>>> hubs. Diffing for RSS/Atom should be done using <guid>/<id> and hence the >>>>>> publication time/order should not matter. This is what Superfeedr does >>>>>> with >>>>>> the hubs it hosts, I'll let Roman explain exatcly how Google does its >>>>>> diffs. >>>>>> >>>>> >>>>> It's the same with Google hub: the order of items doesn't matter. >>>>> >>>>> Now, I Fedburner cannot ping the hub itself if it is not pinged itself >>>>>> about an update. So, it would probably be useful to know if the "burnt" >>>>>> feed itself uses pubSubHubbub. >>>>>> >>>>> >>>>> I have verified that the hub is receiving pings for this feed from >>>>> Feedburner every 6 hours. Let me find out what happens within Feedburner. >>>>> I'll get back to you. >>>>> >>>>> Roman. >>>>> >>>>> >>>>>> >>>>>> Thanks, >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> >>>>>> *Got a blog? Make following it simple: https://www.subtome.com/ >>>>>> <https://www.subtome.com/> * >>>>>> >>>>>> Julien Genestoux, >>>>>> http://twitter.com/julien51 >>>>>> >>>>>> +1 (415) 830 6574 >>>>>> +33 (0)9 70 44 76 29 >>>>>> >>>>>> >>>>>> On Sun, Apr 6, 2014 at 10:10 PM, John Huffaker <[email protected]>wrote: >>>>>> >>>>>>> Hi All, >>>>>>> >>>>>>> I use an RSS feed for ycombinator that only posts stories that >>>>>>> stories that reach 100 points (described here: http://talkfast.org/ >>>>>>> 2010/07/23/a-cure-for-hacker-news-overload/). I used to get a >>>>>>> fairly snappy steady stream of posts throughout the day but I've >>>>>>> noticed in >>>>>>> the past month or so that it would tend to burst in every 6 hours or >>>>>>> so. I >>>>>>> talked to my RSS reader place (theoldreader) and they said that they >>>>>>> rely >>>>>>> on pubsubhubbub for feeds that support it and do full refreshes on a >>>>>>> much >>>>>>> slower cycle. They also mentioned that the order in which the items are >>>>>>> coming (oldest first, newest last) may be causing problems for >>>>>>> pubsubhubbub. All of my searching around made me think that you guys >>>>>>> do a >>>>>>> plain diff and should be fine with order differences. I'm not 100% sure >>>>>>> what is happening with this feed. I've attached the pubsubhubbub status >>>>>>> page image and the feedburner output at a snapshot in time. Any help >>>>>>> you >>>>>>> guys can give me would be very welcome. >>>>>>> >>>>>>> PS: I'm in contact with both the RSS reader people and the feed >>>>>>> author so I can get more info if needed. >>>>>>> >>>>>>> Regards, >>>>>>> John Huffaker >>>>>>> >>>>>>> -- >>>>>>> >>>>>>> --- >>>>>>> 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/d/optout. >>>>>>> >>>>>> >>>>>> -- >>>>>> >>>>>> --- >>>>>> 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/d/optout. >>>>>> >>>>> >>>>> -- >>>> >>>> --- >>>> 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/d/optout. >>>> >>> >>> -- >>> >>> --- >>> 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/d/optout. >>> >> >> -- > > --- > 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/d/optout. > -- --- 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/d/optout.
