Hi Brett, Thanks for the reply. The feeds I have tested with the system are the following: http://gdata.youtube.com/feeds/api/users/reindeerinspain/favorites?start-index=1&max-results=15&v=2 http://gdata.youtube.com/feeds/api/users/FPSRussia/favorites?start-index=1&max-results=15&v=2 http://gdata.youtube.com/feeds/api/users/FPSRussia/uploads?start-index=1&max-results=15&v=2
Reindeerinspain is my primary account. I originally retrieved a slightly different version of the above feed (different order of the query string, v=2 in front of start-index and max-results), but the link element rel='self' had a reordered query string, so I used that to establish the subscription (that is the URL seen above). Originally I had been retrieving the JSON version of the first feed, but finding that only the RSS included the hub element, just dropped the alt and callback parameters. Again, thanks for your time. On Mar 22, 8:38 pm, Brett Slatkin <[email protected]> wrote: > Hey Patrick, > > Could you provide some example feed URLs? How did you discover those > feed URLs? That'd really help me track down your issue. Thanks. > > -Brett > > On Sun, Mar 20, 2011 at 5:50 PM, Patrick Reilly > > > > > > > > <[email protected]> wrote: > > I'm the CTO of a web startup, and recently I have been trying to > > experimentally determine if there is a consistent format to update > > notifications being pushed to the subscriber from a multitude of > > different publishers. During this testing, I used a controlled feed > > from YouTube to attempt to capture at least one of these update > > notifications. I subscribed to my YouTube account's favorites, along > > with one other commonly updated feed afterwards because of my > > preliminary results, and the subscription process went flawlessly, but > > I have not gotten a single POST update notification despite having > > explicitly changed the feed after the subscription was made (multiple > > times). > > I have checked for the update using both a coded debugging mechanism > > in the callback page, and by visually checking the web server access > > logs, but nothing has shown up. > > > The subscriptions are considered valid by the subscription debugger at > > pubsubhubbub.appspot.com, so the error is isolated to either a > > publisher issue, or a hub update receiving/push issue. I'm wondering > > if anyone knows for sure which one of these issues it is. > > > Thank you for your time. > > (Same question as posed here:http://qr.ae/aZBu )
