366 karma · joined January 17, 2010
http://www.mocky.io/, http://ivanzuzak.info/urlecho/, and in some cases: http://hang.nodester.com/
Running smooth in Chrome Canary.
The only difference is that I don't require users to log-in via OAuth, rather I point them to the issue page with the comments and they enter their comments there (which are then displayed on my blog). Less OAuth fuss (both for me and for users) with same functionality.
i've actually done the same things myself, only 2 years ago -- a HTTP server and WebSocket server in the browser via a nodejs proxy server, see: https://github.com/izuzak/node-revhttpws
The Royal Society - "Augmented intelligence: the Web and human computation" (Louis von Ahn) http://royalsociety.tv/dpx_royalsociety/dpx.php?cmd=autoplay...
+ has excellent discussion at the end.
"This document specifies Metalink/HTTP: Mirrors and Cryptographic Hashes in HTTP Headers, a different way to get information that is usually contained in the Metalink XML-based download description format. Metalink/HTTP describes multiple download locations (mirrors), Peer-to-Peer, cryptographic hashes, digital signatures, and other information using existing standards for HTTP headers. Clients can transparently use this information to make file transfers more robust and reliable."