Because comments are not Big Data.
Yep, you got it.
Also MIT licensed.
Please go ahead and kill Facebook comments.
I strongly dislike realname policies in this day and time where a single remark can cost you your job.
I'd like to understand the significance of this. I'm extremely interested in comments as big data (to try to understand social networking patterns better from studying the structure of nested comments) and I'd like to get a handle on the opposite point of view - what is it that you prefer about this approach?
While this might be interesting to you it is in the best interest of the site owners and commenters worldwide that not everything they write is instantly correlatable to anyone who happens to work for Facebook or be in a position where they can somehow buy or otherwise demand this data from them.
https://github.com/skx/e-comments/
Mine uses Redis or SQLite for storage, and uses markdown. The biggest difference is mine is flat. I keep thinking I should rework it to allow nested comments, and avatars, but at the same time it is nice and simple as-is..
Can it though? Because I see some vile comments made by people who appear to be using their real name, photo, location information on their profile.
Big data is mostly used when you want to monetize those comments.
When I first set up isso, I had a hell of a time getting it configured and running, following the pretty poor official documentation. So I visited the Github repo to ask for help but, after seeing the dev's condescending attitude to other people in difficulties, I thought better of it and [fortunately] managed to muddle through by myself.
Isso looks nice, especially like the code blocks and backtick support. However, social login is a must have. The ability for anybody to put a name and email is bound to be a spammers delight.
Why should I use Isso over Disqus?
It is that simple. :)
Your server, your data.
Disqus is offering you a free service for a reason: they want to make good use of the data that your site comments contains.
They also want to hi-jack the community that you have built around your site - or rather: what Disqus has fooled you into believing that you have.
They've had the program in place for years (~2012) and it is opt-in. Author didn't seem to contact Disqus to see if this was a mistake or intentional, and doesn't mention if the domain had the Revenue option enabled. He just says 'I remember once clicking an unrelated option about showing inline ads, that should have been good enough'.
Seems like a senseless ragequit.
I looked into using Discourse to do something like this, but they refuse to reduce their memory usage (2GB minimum required, I think)
coming from a Python project...
The documentation doesn't mention much there, so I'm afraid I'm stuck. Has anyone managed to set this up? I'll open an issue with them to improve the docs.
Regardless, it works quite well now, thank you!
