Remove the protocol from absolute references to respect the current protocol

By default, all popular Web browsers assume the HTTP protocol. In doing so, the software prepends the 'http://' onto the requested URL and automatically connect to the HTTP server on port 80. Why then do many pages explictly set http on all hypertext links? Surely it is easier to type "domain.com" than "http://domain.com". HTTP is also deprecated due to the ever-evolving web: The HyperText Transfer Protocol is no longer used to transfer hypertext. It is increasingly becoming used a means to transfer any content over port 80. Thus the definition "http" no longer means anything in the context of a URL since you are unlikely to be requesting hypertext. As the web evolves, next generation protocols will begin to replace http. By explicitly using "http://domain.com" in your links you are forcing your viewers of the future into using an obsolete protocol. By using "//domain.com" you will guarantee the protocol of tomorrow will work with your pages of today. Succinctly, use of the http protocol is redundant and time consuming to communicate. The internet, media, and society are all better off without it.

very flexible jQuery plugin for quickly creating an Ajaxed star rating system

Cross-platform mobile apps JS framework

A new version of the Web Farm Framework

- Free & Open Source - Lightweight. NO IMAGES USED - 100% skinnable using CSS - Library independent - Easy to use - Easy to understand & extend - Consistent look between browsers - Full Screen & Full Window Modes - Volume Control - Forced fallback to Flash (even when there is an unsupported source)

Hosted SVN, including free personal option

goo.gl API

a graph visualization library using web workers and jQuery

DHTMLX Touch is an HTML5-based JavaScript library for building mobile web applications. It's not just a set of UI widgets, but a complete framework that allows you to create eye-catching, cross-platform web applications for mobile and touch-screen devices.