I wrote it mainly because I found Disqus and IntenseDebate too limiting, not because of concerns about hosting or data ownership. I'm trying to implement per-section commenting for the Phusion Passenger manual similar to how it's done in the Django book (http://www.djangobook.com/). However after a week of trying it became painfully clear that Disqus was only designed for one use case in mind: a single comment box per page, e.g. blogs. Comment topics in Disqus are tied to the URL, which doesn't work in my case because I want each section on the same page to have a different comment topic. The Disqus developer documentation says that they support AJAX but I did things exactly as documented and all I got was vague undebuggable JavaScript errors.

IntenseDebate was the almost exactly same. I gave up after two days.

I finished the most important parts of Juvia today. I got Juvia commenting in the manual working in about 15 minutes.

Have you made a final decision on no-nested comments/replying? There are some comments related to adding nesting as a feature, as you can even see with your own comment reply here- it's useful and pretty much a necessity these days to make sense of conversation.

No it's not a final decision, but I'm not going to write support for it so feel free to contribute. That said I did add a 'Reply to comment' button a few minutes ago by popular demand.

I agree with loceng. Nested comments are really valuable with any sort of active conversation. If you are only thinking of 2 people in a conversation as your test case, then it's fine as it is.

Btw, really good work with Juvia so far. Been going through your github source and might even play with it next weekend.

Did you successfully use this for per-section commenting somewhere? Can that be viewed? I've been looking for a good way to do this for a long time.

Yes. Still working on it though: https://github.com/FooBarWidget/mizuho It's not finished yet. The Juvia site key and URL are currently hardcoded in the source.

I do seem to recall there being some way to override the thread identifier for Disqus, though I'll admit that I never bothered to try it.

The thread identifier is not the problem. I'm only displaying one comment topic at a time by using a lightbox. However once I have loaded a Disqus comment topic, switching to another one seems to fail randomly even if I call their documented DISQUS.reset API.

Perhaps you could give each section/paragraph it's own URL and link the 'per-page/resource' comments to that?

The sections are really short. Giving each section its own URL will make the reading experience horrible. Most of my users told me that they actually prefer a one-page manual because it makes searching easier.