WeChat ID
aaronpk_tv
#PubSubHubbub
-
I did tell y'all about Mastodon last November, remember? https://youtu.be/UHunxMTRCJc?t=1h16m6s #indieweb #websub #PubSubHubbub
-
Naming things is hard. Help us out. We are considering a new name for https://www.w3.org/TR/pubsub/
• HubPub
• Hubbub
• HubCast
• PushCast -
PubSubHubbub is now known as PubSub, and has been adopted by the @W3C! https://www.w3.org/TR/pubsub/ Congrats @julien51!
-
Enabling Global Webmentions with Telegraph and Superfeedr
You can use Telegraph to receive Webmentions when your site is linked to by any website tracked by Superfeedr, even if that site doesn't send Webmentions itself!continue reading... -
Jᵾlien Genestoux
https://twitter.com/julien51
•
May 19
Spend years ignoring other people's work, then, change your mind, and tell them how they're wrong.
@julien51 I certainly didn't mean to come across that way! The reason I haven't contributed to PuSH until now is because I still had a lot of catching up to do myself, making better publishing and consuming tools for myself. Now that I'm actively publishing short notes on my site, and reading others' posts in my reader that supports PuSH, it's suddenly extremely relevant! I hope the takeaway would be that there is now a renewed interest in PuSH which should help make it better and be adopted by more people! -
This really is just pointing back to the question of what is the original goal of this spec. If the goal is to describe a way for consumers to subscribe to content, then yes, publisher->hub is not needed as part of the spec. Since that's what @julien51 described, then it sounds like the best course of action is to document the publisher->hub interaction separately, with the goal being to make it possible for publishers to use generic hubs.
-
There's no point in adopting a spec that doesn't actually tell you what to do, other than to have the official stamp of approval of that spec. Right now, any number of completely incompatible implementations of can call themselves OAuth 2.0, but is that really a success? Is that really what we're shooting for?
At a minimum, I would like the PuSH spec to define *one* way publishers can notify hubs, (`hub.mode=publish&hub.topic=x`) and in order for a hub to be PuSH-compliant it MUST support *at least* that way. Hubs should be welcome to support additional methods, such as the two ways already implemented by two different hubs. (multiple topic URLs https://indiewebcamp.com/how-to-push#Multiple_topic_URLs) by adding additional `hub.url` parameters, and wildcard topic URLs https://indiewebcamp.com/how-to-push#Wildcards) -
Frankly, not having the publisher->hub payload in the 0.4 spec feels like a failure of a spec, similar to how OAuth 2.0 core is considered a failure. Having a separate spec for the publisher->hub payload also points to a failure, which is exactly what OAuth 2.0 is doing now.
There's nothing wrong with allowing hubs to offer more functionality for publishers, but there absolutely needs to be a common payload. Being able to change hubs by simply changing the hub URL advertised in the link header is critical to a successful standard. -
superfeedr
https://twitter.com/superfeedr
•
Apr 26
@kylewmahan yes! Just make sure you urlencode each of them and use comas as "glue" :)
@superfeedr @kylewmahan Why not use array syntax like `hub.url[]=x&hub.url[]=y`? -
superfeedr
https://twitter.com/superfeedr
•
Mar 18
@aaronpk It's a WIP. but we'll add support. Hopefully by the end of next week. Sorry for the delay :(
@superfeedr awesome! I just added a clarifying note to the wiki, but will remove it when that's done! https://indiewebcamp.com/how-to-push#Link_to_your_PuSH_Hub
-
Suggestion: Change the text in Section 5.1.1 https://pubsubhubbub.googlecode.com/svn/trunk/pubsubhubbub-core-0.4.html#rfc.section.5.1.1 to say "The topic URL MUST be the one advertised by the publisher during the discovery phase."
Section 5.1.1 currently says "The topic URL MUST be the one advertised by the publisher in a Self Link Header during the discovery phase."
However, section 4 says that the topic URL can be specified in *either* the Link header or a tag in the document body, such as an HTML link tag. This change makes the sections consistent. -
[announcement] PubSubHubbub 0.4 - Google Groups (groups.google.com)
The specification no longer dictates a specific protocol between the Publisher and the Hub.
-
RSSCloud Vs. PubSubHubbub: Why The Fat Pings Win | TechCrunch (techcrunch.com)
With all of the debate lately between RSSCloud versus PubSubHubbub, we wanted to hear from a developer who could actually tell us which one might be better and why. The following guest post is written by Josh Fraser, the co-founder of EventVue, who is an active contributor to PubSubHubbub in his free time. He has contributed several client libraries for PubSubHubbub including a WordPress plugin. Guess which side of the debate he falls on.
