Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

This is likely because Google had such a large userbase that they were able to update more people's feeds at the same time than a lot of other places like newsblur and feedly can right now.

I also imagine it's because google was requesting the feeds more often than others, or leveraging the feedburner system to know when they were updated and other such things.



Google Reader implemented PuSH:Pubsubhubbub (worst protocol name ever!). Most blog platforms ping using PuSH, so the update needs no polling and is thus almost instantaneous.


If anyone is looking to play around with PuSH, http://superfeedr.com/ has been a joy to work with. There's also a reference implementation available at https://pubsubhubbub.appspot.com/.

It handles all the "dirty" parts of feed reading (checking for new items, normalizing fields) and adds near instant updates for sites that ping hubs.

When I finally get around to writing my own feed reader, I definitely plan on using it.


Does anyone know which of the new replacement readers, feebly etc. support pubsubhubbub?


This is a question I have been wanting an answer myself for a while. Especially I am interested if Feedly, Newsblur, Inoreader, is using PUSH method


Neat. I had no idea that such a protocol existed let alone that it'd have such a ... colorful ... name that makes it hard to find :)

I wonder how hard this would be to get it implemented in some of the other readers.


Some protocol developer had a sick sense of humor


You're welcome. :)




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: