Show HN: Commento: Lightweight, open source, tracking-free alternative to Disqus
github.com
github.com
Edit: sorry, I had to purge the comment list because of an update. From now on, your comment will only be alive for 30 minutes. It'll be deleted after that. This is, of course, only for the demo.
I am on FireFox 53.0 on a decent Windows 10 laptop.
Recommended alternatives to Commento (Golang):
· https://posativ.org/isso/ (Python)
· https://github.com/jimpick/lambda-comments (Node.js, AWS)
Github-based alternatives:
· https://staticman.net for Github comments
· Github Issues for comments ( http://donw.io/post/github-comments/ )
> https://github.com/shurcooL/issuesapp
> http://ebarnouflant.com/posts/4-turn-your-github-issues-into...
· Github Wiki for blogging: https://github.com/stickfigure/blog/wiki/GitHub%27s-wiki-mak...
· remove comments and use Pull Requests and Issues for substantive discussion
Other options:
· Reddit, Facebook, Discourse for comments
· Privacy via Disqus comments on demand when pressing a button
· Google Wave via Sandstorm
And you get Google, Twitter, GitHub, etc sign on for free.
An endorsement from Mr Berners-Lee means little, having caved on the DRM issue.
If the sites that use Disqus today were willing to pay for an alternative, I would personally offer hosting of such, with fast load times and no tracking. However, I don't believe such willingness exists, and people are getting conditioned to accept sluggish load times and tracking. Too bad. Self hosted Open Source solutions are the second best alternative - management gets the illusion that the thing is free, and you actually get fast load times and no tracking.
* In 5 years time, large organizations (e.g. NY Times) will look far more into self-hosted, often open sourced alternatives. Maybe now, they post to twitter, soon they'll refer users to their own mastodon instance. Now, orgs host comments on disqus, in the future self-hosted platforms like Commento will be used. In some ways, it will go back to the independent way in which things operated back in the late 90s/early 2000s; though hopefully better in other ways. That's my prediction.
On the other hand, a repo history is normally immutable (with force pushes on rare occasions), and comment spam is way to common. Do you really a repo with all the usual link spam in its commit history? In case of public hosting it may trigger some spam filtering automation and block the repo/account. While perfectly possible, I'm not sure a DVCS repository is a well-matching concept for storage here.
I find it very hard to get worked up about 200k and 3 seconds of nonblocking load.
The tracking is of more immediate concern, but you also have to make a choice as a site owner:
1. Host your own comments. Nobody does this anymore because nobody likes registering for every site out there. You can have anonymous commenting, but ++ abuse. Either way, spam concerns are completely on your shoulders, and you still have to moderate.
2. Shell out to Disqus or similar. People get to log in with the credentials they already have (and don't have to log in at all if they have cookies from using another Disqus site), moderation is still a thing, but spam is much less of a problem.
3. Not have comments at all. An increasingly popular option.
That's a lot. Because Disqus doesn't generally load when the page does.
You have the time the user is reading to load it, but generally Disqus doesn't load till it comes into view.
[1] http://pablojuan.com (https underway)
[2] https://dev.to
Are you planning on also offering a paid hosted version?
Edit: I know that if I create a SaaS out of this, you'll have me as a direct competition. But can I know more about how you got yours running, what the range the net revenue is in (like, is it over $100/month? Over $1000?)?
Disqus is also paid or supported by ads: https://disqus.com/pricing/
Are you considering to add support to other databases?
I'm afraid I'm not very familiar with how go-sqlite3 handles that. I just started learning golang a month ago, so it's all quite new to me.
Maybe someone else will have a better answer.
>Are you considering to add support to other databases?
At the moment, no. Comments aren't exactly big data ;)
Just curious - which databases would you like to see and why (what do they offer over sqlite)?
I would guess most use cases for this relatively simple comment software wouldn't be expecting that many comments anyway.
An agnostic data layer should probably go on your list, but I imagine other stuff would be higher on the list...like a captcha. Spam will likely be the top issue long before performance.
I'd been using Juvia a lot over the year's, built by the people at Phusion. It's worked really well, but seems to be unmaintained now.
The killer feature needed in any project like this is spam filtering, which Juvia accomplished by just integrating with Akismet, which works mostly, but not completely.
Some of their proposals, taken together, could enable people to emulate what Facebook offers, from their own servers.
I'm not 100% onboard with all their ideas, and a few just seem wrong, but all in all I think that they're exciting and important.
I <3 open source.