31–40 of 68 posts
So this wouldn't work with a static blog generated by something like Hugo, right?
Earlier quoted context omitted.
You shouldn't if you are happy with Disqus. Isso is an open source, self hosted alternative.
Yes, but what advantages accrue to the person using it? It's become fashionable for people to identify which boxes they tick in a single sentence when describing their product, but this is basically preaching to the converted. For people who are not already exercised about always preferring an open-source option (ie potential new entrants to the OSS community), it's worthwhile to provide positive reasons to use it, b…
It is not a product.
And, as such: doesn't need to market itself.
Use it if you want to. Or not.
I wanted to use it, but couldn't make it run - I am not a Python guy, so I went for HashOver (PHP) instead. Not because HashOver is better, it's not, but because I need to be able to modify/fix the software, and I know PHP better than Python.
But I still believe that Isso is the best self-hosted and open source Disqus alternative in existence.
(about alternatives) "Juvia, written in Ruby (on Rails). No threaded comments, nice administration webinterface, but... yeah... Ruby." coming from a Python project...
Genuine question which I think should be on the site's FAQ: 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.
SQLite backend 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.
Because comments are not Big Data. 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?
SQLite backend 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.
Because comments are not Big Data. 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.
SQLite backend 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 strongly dislike realname policies in this day and time where a single remark can cost you your job. 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.