Ok, so if I understand this correctly, in order to be certain I'm not tracked, I need to host my own back-end server? And the server stores the comments? And if I'm hosting my own server, I'm likely to end up talking mostly with those that sign up with "my" version of this? And if I want it to work in eg: Firefox I'd have to port it? Finally, wrt. tracking -- if the comments are stored on the server (and that's a REST service or something like it) -- wouldn't it be trivial to log activity at the routing level (eg: ha-proxy/nginx/other front-facing web server)?

This isn't meant as negative criticism, just trying to figure out if I've understood how it works correctly? (Note, I appreciate that the source is available, but obviously I can't know that the source you share is the source you run on your back-end. So we're back to trust, which is fine in my book).

[edit: re other clients -- the most straightforward thing to do would be to make an iframe(or js)-based proxy service (a la stumble upon) in order to enable any browser, I suppose?

I've thought about something similar, and I wonder if an XMPP back-end with one "room" pr url and the server-side log-extension might work? That should then make it trivial (unnecessary!) to enable better clients than web-only -- ie use a command line xmpp client to participate in the discussion, rather than forcing the use of the web browser. I realise many people think using the web browser is an advantage -- I generally find GUIs built on top of browsers to be slow and not very efficient. Extensions less so -- but the problem is of course that you'd have to port to Firefox, Opera, Webkit and IE (along with mobile variants) -- to achieve parity with systems like disqus etc]