Google released Chrome 13 into its stable channel this morning with over 5200 revisions including Instant Pages. If your webpages are not already differentiating between attended and unattended pageviews using the Page Visibility API for site analytics (and other functions assuming live eyeballs and the opportunity for interaction with page elements) your pageview numbers are now likely inflated.
The Google Chrome team released new statistics and implementation details on their proposed “False Start” abbreviated TLS handshake. Google claims the new handshake, introduced in version 9 of the Chrome browser in February, shaves an average of 120 milliseconds from a typical four-flight TLS handshake by accepting application data before both sides have communicated a “Finished” status.
This blog is now powered by WordPress multisite.
H.264 is not a single video codec; it is a family of codecs with some shared shortcuts grouped into 17 sets of profiles and 16 levels of constraints. Video creators and playback software share a mutual understanding of these shortcuts, which are often accelerated by specialized chipsets. This post examines a few of the many flavors of H.264 video and their application in mobile, desktop, and Flash Player environments.
The emerging HTML5 specification lifts video playback out of the generic object element and into specialized video handlers. Explicit markup for audio and video places elevates moving pictures to a similar native rendering capacity as img markup we are used to but with more fine-grained details about underlying formats and compression available before loading. In this post I will dive into implementation details of HTML5 video based on currently available consuming agents and outline some of the nuances of preparing media for playback.
Google will roll out a change to its search results pages later this week designed to better capture outbound clicks. Google search result pages will link to a gateway URL before delivering the visitor to his final destination. These gateway URLs will replace search result URLs exposed via the Referer HTTP header.
This week Facebook will complete its roll-out of a new photo storage system designed to reduce the social network’s reliance on expensive proprietary solutions from NetApp and Akamai. The new large blob storage system, named Haystack, is a custom-built file system solution for the over 850 million photos uploaded to the site each month. Jason Sobel, a former NetApp engineer, led Facebook’s effort to design a more cost-effective and high-performance storage system for their unique needs.
On Thursday BusinessWeek reported Facebook is seeking new financing for its data center operation growth in 2009. Facebook continues to add new members and their associated content at an extremely fast pace, with most new growth coming from international markets. Facebook needs to expand its abilities to serve these markets by bolstering current infrastructure offerings and cutting latency to its members through new international points of presence. In this post I will take a deeper look at Facebook’s current computing infrastructure and related expenses and examine likely new areas of investment in 2009.
Yahoo! announced support for enhanced search results last week based on Facebook Share and RDFa markup. Website owners can add a few meta tags to their pages to boost click-throughs from a more visual Yahoo! Search result and east the process of sharing a link on Facebook at the same time. In this post I will cover the major categories of enhanced share types — audio, images, video, news, blogs, games, documents, and multimedia — and walk through how site owners can stand out on shareable platforms.