WeChat ID
aaronpk_tv
Friday, February 27, 2015
| bicycle |
56 min
|
|
8.8 miles
|
bicycle |
-
-
Jᵾlien Genestoux
https://twitter.com/julien51
•
Feb 27
@aaronpk that wouldn't be "compliant" per protocol, but I think *we* can implement it. Please add issue https://github.com/superfeedr/documentation/
@julien51 From what I understood, it was optional for hubs to support, but explicitly called out in the spec: https://pubsubhubbub.googlecode.com/svn/trunk/pubsubhubbub-core-0.4.html#discovery "In the absence of HTTP [RFC2616] Link headers ... it MAY use embedded link elements..."
I will add an issue on Github, thanks! -
@julien51 no it actually says HTML! "Similarly, for HTML pages, it MAY use embedded link elements..."
-
Jᵾlien Genestoux
https://twitter.com/julien51
•
Feb 27
@aaronpk Wow! I wrote that and complete forgot it!
@julien51 You were clearly thinking ahead!
-
Support discovery of hub+self in HTML <link> tags
The PuSH 0.4 spec says hubs may support <link> tags on HTML pages. It would be great if Superfeedr supported this, to allow more sites to use it. Some web frameworks and hosting environments make it difficult or impossible to set HTTP Link headers, so HTML tags would be the only way to do this.
> In the absence of HTTP [RFC2616] Link headers, subscribers MAY fall back to other methods to discover the hub(s) and the canonical URI of the topic. If the topic is an XML based feed, it MAY use embedded link elements as described in Appendix B of Web Linking [RFC5988]. Similarly, for HTML pages, it MAY use embedded link elements...
