Of course, PubSubHubbub needs to support any kind of content, including JSON. However, I find it quite worrysome that people rewrite feeds completely in JSON.
JSON is NOT the equivalent of a RSS or Atom. JSON is the equivalent of XML : a language that cna be used to represent any data. RSS and Atom go much deeper into this, because they can represent _every_ data. The JSON that instagram uses has nothing to do with the JSON that Github uses and that Facebook uses. The world will not be better when you can subscribe to any web resources but have to write specific parsers for each feed to which you subscribe. As much as I understand the developer's love for JSON, they should probably focus on creating a feed-like format in JSON and agree to use all the same before they decide to ditch RSS/Atom feeds altogether. I believe that's what AS is trying to do with their new move to JSON, but that obviously excludes non-social data. On Fri, Feb 25, 2011 at 4:04 AM, Alexis Richardson <[email protected]>wrote: > +1 to json support in v4 > > I think we are running into an issue we have discussed before. Is > PSHB a tool for federating event notifications to HTTP subscribers, > for web content, or is it a way to bootstrap the incumbent feeds > universe into some sort of publishing network? Or both? > > alexis > > > > On Fri, Feb 25, 2011 at 7:49 AM, Jeff Lindsay <[email protected]> wrote: > > JSON (or arbitrary payloads) and "fat pings". The point of my remark > > is that as long as feeds are a first-class citizen of PubSubHubbub, it > > will remain within the limited subset of people interested in both > > feeds and realtime/webhooks -- which *is* limited because most people > > interested in feeds are fine with feeds as they are, and those > > interested in webhooks don't want anything to do with feeds. > > > > I've heard of a lot of people turn to PubSubHubbub looking for > > something to help with webhooks, and then end up ignoring it or using > > pieces of it, a la Facebook and Instagram (and GitHub is considering > > doing the same). This is also the reason I started losing interest in > > it -- feeds have nothing to do with the problem I wanted it to solve. > > > > I'd love to talk about this at the next Evented Web meetup next month. > > You're all invited. My remark was partly inspired by Instagram, and > > partly from the discussion at tonight's meeting. > > > > -jeff > > > > > > On Thu, Feb 24, 2011 at 11:37 PM, Brett Slatkin <[email protected]> > wrote: > >> Yeah definitely cool stuff! > >> > >> For starters, this highlights the need for formalized JSON support in > >> the Hubbub spec. I think this is something we need to get ironed out > >> by May 1st (and publish v4 of the spec). How does that sound to you > >> folks? > >> > >> The other shortcomings they've worked around (or left out) are like > >> what Facebook did for their API. Namely, putting extra parameters in > >> the subscription request as additional search of filter requirements. > >> After almost a year since Facebook launched their API that uses a > >> subset of PubSubHubbub > >> (http://developers.facebook.com/docs/api/realtime/), it's safe to say > >> that this too is a common idiom we should merge as well. > >> > >> > >> > >> Related, I believe Instagram's release precipitated Jeff's comment > >> (http://twitter.com/progrium/statuses/41010799010910208): > >> > >> "PubSubHubbub will fail because most people are fine with feeds and > >> everybody else into webhooks will skip feeds entirely." > >> > >> > >> I think this misses the point. The community at large creates > >> standards and embraces de facto standards because they vastly simplify > >> our lives. Feeds (ie, XML-based formats) have been helpful to that > >> end, but they're showing their age. JSON is simpler in a whole bunch > >> of ways. There are important parts of Feeds (eg, idempotent IDs) that > >> could be carried over to the JSON formats and help everyone. > >> Similarly, these JSON webhook APIs have reused the registration style > >> of PubSubHubbub because it's a common idiom that's beneficial to > >> developers and solves common problems in a familiar way. > >> > >> > >> So I think the useful take-away is we should get down to business soon > >> and formalize PubSubHubbub for JSON and alternative content types. > >> > >> -Brett > >> > >> > >> > >> On Thu, Feb 24, 2011 at 2:25 PM, John Panzer <[email protected]> > wrote: > >>> +100! > >>> -- > >>> John Panzer / Google > >>> [email protected] / abstractioneer.org / @jpanzer > >>> > >>> > >>> On Thu, Feb 24, 2011 at 2:05 PM, Julien Genestoux > >>> <[email protected]> wrote: > >>>> > >>>> Great news! > >>>> Instagram launched its realtime API and it's based on PubSubHubbub :) > >>>> Cheers! > >>>> Ju > >>> > >> > > > > > > > > -- > > Jeff Lindsay > > http://progrium.com > > >
