I'm doing this same "anti-aliasing" of feed URLs by using //atom:feed/id elements. The "self" link (which is in the 0.2 spec) doesn't work right in practice, methinks. Not sure how well we'll define this for 0.3 though.
-Brett On Mon, Oct 19, 2009 at 4:18 PM, Pádraic Brady <[email protected]> wrote: > Hi Tim, > > Not sure if its relevant in terms of the reference hub, but my Subscriber > has trouble with your feed. What it's doing is accepting your Atom feed URI > "http://www.tbray.org/ongoing/ongoing.atom"; and then attempting to verify > the location of the feed, i.e. to rule out redirects etc. To do this, it > parses the feed for an atom link with a rel attribute of "self". In the case > of your feed, however, the href attribute seems to be empty - so my > Subscriber passes back an exception stating that the feed's final location > could not be verified. > > I'd expect the Hub to be making a similar check in verifying the > subscription details. It's a total stretch, but since this seems to breach > the Atom specification it's possibly related. See > http://tools.ietf.org/html/rfc4287#section-4.2.7 > > Paddy > > Pádraic Brady > > http://blog.astrumfutura.com > http://www.survivethedeepend.com > OpenID Europe Foundation Irish Representative > > > ________________________________ > From: Tim Bray <[email protected]> > To: [email protected] > Sent: Mon, October 19, 2009 8:06:45 PM > Subject: [pubsubhubbub] How to check what pubsubhubbub.appspot.com is doing? > > > I *think* I'm pinging appspot when I update (it goes into the code > that does so and doesn't report any errors) but I look into my > logfiles and don't see any accesses from appspot since about 7PM last > night. Is there a way to find out when appspot thinks I've pinged it? > > Hey, my publishing system is 2500 lines of Perl in one file that I > wrote in a few days in 2002, what could possibly go wrong... > > -Tim >
