API-Status: Uptime status of many public web APIs
The open Home Automation Bus (openHAB) project aims at providing a universal integration platform for all things around home automation.
It is designed to be absolutely vendor-neutral as well as hardware/protocol-agnostic. openHAB brings together different bus systems, hardware devices and interface protocols by dedicated bindings. These bindings send and receive commands and status updates on the openHAB event bus. This concept allows designing user interfaces with a unique look&feel, but with the possibility to operate devices based on a big number of different technologies. Besides the user interfaces, it also brings the power of automation logics across different system boundaries.
openHAB is a pure Java solution, fully based on OSGi. The Equinox OSGi runtime and Jetty as a web server build the core foundation of the runtime.
The openHAB Designer, which is the configuration tool for the openHAB Runtime, is an Eclipse RCP application with Xtext-based editors to offer a highly user-friendly way of editing configuration files, UI definitions and automation rules. For the automation rules, JBoss Drools builds the backbone.
If you are a fan of Java/OSGi/Eclipse, openHAB should be the perfect match for you. If you are not, you might want to consider other tools like Misterhouse, which aim at almost the same thing and are very mature already.
As the OSGi platform allows a highly modular architecture, the bindings are realized as different bundles, which can be dynamically plugged to openHAB, so that every user can decide on the bindings he is interested in.
Here are some examples for bindings (but please be aware that most are not yet implemented):
Currently, there is only one user interface available for openHAB, a web-based UI, which can be used from many different devices. Nonetheless, openHAB is designed in a way that there can easily be added further user interfaces; be it a remote terminal or a native iPad application.
http://code.google.com/p/openhab/
OSGi services can be easily configured using the ConfigurationAdmin service. If you add metadata to your services, they can be configured with a nice user interface such as the Apache Web Console. This tutorial will walk you through the steps to create the metadata, set up the web console, and configure your services.
The JavaScript InfoVis Toolkit provides tools for creating Interactive Data Visualizations for the Web.
spirit20 consists of almost 500 transparent PNGs at 20×20 pixels, and is completely free to use for both personal and commercial projects. No attribution is required.

source: http://www.webresourcesdepot.com/450-free-web-application-icons-spirit20/
Video JS is a javascript-based video player that uses the HTML5 video functionality built into advanced browsers. In general, the benefit of using an HTML5 player is a consistent look between browsers.

SproutCore is an HTML5 application framework for building responsive, desktop-caliber apps in any modern web browser, without plugins.
SproutCore works by doing the only thing that can truly eliminate the latency problem: it moves your business logic to the client. SproutCore applications are full-fledged programs, written in JavaScript. That JavaScript executes in your user’s browser, freeing up your servers (and server engineers) to focus on what’s most important in a cloud application: delivering users’ data as quickly and reliably as possible. But SproutCore isn’t your mama’s JavaScript library. It isn’t meant to augment existing web pages. It isn’t meant to add animation to documents. SproutCore is a tool for building applications. It has more in common with Cocoa or .NET than jQuery or MooTools. Because of that, SproutCore will change the way you think about building web apps. SproutCore is server-agnostic and will plug into your existing backend. http://www.sproutcore.com/