pakidesigner.com

ver wish your RSS reader worked more like a Twitter client? Or even FriendFeed, where updates just appear in real-time? Well, that idea has been gaining ground for some time, and it just got a whole lot more appealing now that WordPress has announced support for RSS Cloud.

RSS Cloud takes advantage of the cloud element in the RSS 2.0 specification. Actually cloud has been there since RSS 0.92, but no one paid much attention to it until Twitter and others ushered in the idea of a real-time web. The cloud element is used to deliver push notifications to your feed reader.

That’s essentially the reverse of how RSS readers work right now. At the moment, most popular RSS readers poll sites to see when they have new content. Another, slightly better method is to wait for a ping from your blog to let the RSS reader know when new content is available. But as WordPress creator Matt Mullenweg notes in the announcement, “getting every ping in the world is a lot of work… RSS Cloud effectively allows any client to register to get pings for only the stuff they’re interested in.”

The result is that new posts from your favorite blogs arrive much faster using the RSS Cloud method. As Marshall Kirkpatrick writes over at ReadWriteWeb, the difference in wait times is like “the difference between checking your e-mail every once in awhile and using a Blackberry to get new e-mails pushed to you as soon as they arrive.”

Sounds good, no? More news, delivered faster. Well, the bad news is that there’s really only one feed reader that currently supports RSS Cloud — Dave Winer’s River2. However, with WordPress now implementing the cloud element in its feeds, some 50 million posts a week are potentially accessible to cloud-enabled feed readers, which should be more than enough to tip the balance in RSS Cloud’s favor.

Of course there are some competing specifications, like pubsubhubbub or FriendFeed’s SUP proposal, which both do something similar to enable push updates.

WordPress has already said that its working on other ways of pushing notifications to news reader, including pubsubhubbub, so while you may have to wait a while before your favorite reader enables support for RSS Cloud and others, the WordPress announcement has certainly added incentive. And, hopefully, it will give RSS readers a much needed kick in butt — let’s face it, RSS readers aren’t exactly hotbeds of innovation right now.

Indeed Dave Winer is trying to get popular Twitter clients to support RSS Cloud. If they do, they could well end up supplanting RSS readers as the way most people get their news.

We’ll just have to stop calling them Twitter clients and start calling them what they should be referred to as: news clients.

While HTML5 has been getting most of the attention lately, CSS 3, the other half of the web developer’s toolkit for next-generation web pages has been progressing as well.

Although the CSS Working Group has taken a fair amount of flack from the development community over the years, despite the Working Group’s lack of transparency and refusal to engage the community, the actual implementers — Apple, Mozilla, Opera and Google — continue to push CSS 3 toward the mainstream.

One of the more interesting aspects of CSS 3 is the new Flexible Box model spec which essentially allows you to define how unused portions of block level elements are handled. Sound confusing? Well, initially it can be. Fortunately, Alex Russell of Dojo fame has put up a nice guide to using the new flexible box model.

Essentially, two new CSS 3 selectors, hbox and vbox, allow you to easily center an element within its parent element. Then, as the spec says, “unused space can be assigned to a particular child or distributed among the children by assignment of ‘flex’ to the children that should expand.” In other words, you can make some child elements flexible and others fixed, which makes for considerably more complex layouts using only a fraction of the code you’d need to do that using pure CSS 2.

One thing to keep in mind: selectors like hbox and vbox are not universally supported yet, so if you need everything to work in IE, this method is off limits. However, hbox and vbox do work in Gecko and Webkit, which means these tricks will work just fine for Safari, Firefox and Chrome. Opera is only progressive browser missing from the list.

As Russell points out in his write-up, while universal support is still a ways away, these techniques could be used in mobile interfaces where Safari and Chrome are prevalent.