Oh my goodness, I've been looking for this (mocky) for weeks! Thank you. There really isn't much by way of this particular service, and I found it immensely valuable when I used it last.
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 think this is really cool! have you seen the recently announced http://browserver.org/? it puts a http server in the browser using a proxy.
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
are you stuck in 1999.? no, it's not that awesome. there are a lot of sites that "personalize" based on visitor location and guessing that location is also not awesome.
Didn't know about it, you've got some cool features there.
Since you shared the GitHub repo, I first thought you have to install that yourself, but apparently you also host it on AppEngine: http://urlreq.appspot.com/req
The content of the presentation is much the same, albeit pitched at a different audience. To get straight to the discussion at the end (which is impossible effectively to summarise for you and well worth the time) skip to about 26:00 in the video.
"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."
