Sound of a Dog Eating Grass

In an unembargoed presentation sent to press this morning, Netvibes said that it would be adding support to its next version for both Pubsubhubbub and RSS Cloud protocols. When those technologies are used to tell Netvibes that new items are available, the items will be pushed automatically to the browsers of subscribers - with no browser refresh required.

Code named Wasabi, the version will go into private beta later this week and will launch to the public at December's Le Web conference in Paris, where the theme of the event is the real-time web.

Support for real-time feeds has so far been much stronger on the publisher side than the consumer technology side. With blog publishing services WordPress, Blogger and Typepad all adding Pubsubhubbub or RSSCloud feeds to their offerings, there are now hundreds of millions of real-time feeds available in those two formats. So far only a few small feed readers have begun consuming these feeds; RSSCloud developer Dave Winer's own River2, a complex but customizable desktop feed reader, and LazyFeed, a simple but enjoyable feed-powered discovery engine, have turned on full support for real-time feeds. Real time didn't come up in interviews this week with the creators of NetNewsWire and FeedDemon.

Google Reader implemented very limited support for PubSubHubbub in August, just pushing a Hubbub feed of "shared items" from Reader to the now-Facebook owned FriendFeed. In that case Google Reader was playing the part of the publisher and FriendFeed was the reader. Google's Brad Fitzpatrick has told us that when PubSubHubbub support allowed FriendFeed to wait for updates from Reader, instead of polling regularly to check for updates, traffic between the two services was cut by 85%.

From decreased server costs to an improved experience for users to increased time-on-site, the benefits of real-time feeds can be many. Can Netvibes pull off integration of real-time feeds into its existing dashboard product? Some developers experimenting with these new real-time feeds elsewhere have reported stumbling blocks in the process, and Netvibes hasn't had a perfect record of service for users in all locations around the world, either. Long caching of feeds has been an issue for Netvibes, though, and this update will cut down substantially on the delays that users see after feeds of interest have published new content.

Invitations to the private beta will roll out later this week, giving a few hundred users an opportunity to see the new Netvibes for themselves.

Google's Document Viewer lets you preview PDF files, PowerPoint presentations and TIFF files without installing additional software. It's great for linking to documents available online and for embedding them in a site.

If you want to link to a certain page from your document, adjust the URL. This is the link generated by Google for a PDF file:

http://docs.google.com/viewer?url=http%3A%2F%2Finfolab.stanford.edu%2Fpub%2Fpapers%2Fgoogle.pdf

To load a specific page in the document, you need to add a hash to the end of the URL. Page IDs are numbered sequentially like this: :0.page.0, :0.page.2, :0.page.3...

So to load page #15 of the document, use this link:

http://docs.google.com/viewer?url=http%3A%2F%2Finfolab.stanford.edu%2Fpub%2Fpapers%2Fgoogle.pdf#:0.page.14

The same trick works for the embedded viewer:

http://docs.google.com/viewer?url=http%3A%2F%2Finfolab.stanford.edu%2Fpub%2Fpapers%2Fgoogle.pdf&embedded=true#:0.page.14

{ Thanks, Andy. }

Labels: Google Docs, Tips