Hacker News new | past | comments | ask | show | jobs | submit login

All (?) upcoming alternatves to Disqus: (my own listed last)

- Mozilla's Talk, https://github.com/coralproject/talk. Open source, install yourself.

- Discourse, https://www.discourse.org/. One needs to navigate to a separate page, to post a comment. Not threaded. Min $20/month. Open source. Facebook and Gmail login.

- Isso: https://posativ.org/isso/. Open source, install on your own server.

- Commento, https://github.com/adtac/commento. Open source. Moderation, spam-protection and hosting is under development.

- Schnack, https://www.vis4.net/blog/2017/10/hello-schnack/. Open source, install yourself. Has GitHub and Facebook login.

- HostedComments, https://www.hostedcomments.com/. Proprietory. Min $10/month

- Remarbox, https://www.remarkbox.com/. Proprietory. Min $4/month

- Gitalk. https://github.com/gitalk/gitalk. Open source, install yourself. Comments stored as GitHub issues.

- https://github.com/skx/e-comments. Open source, install yourself.

- And my own: EffectiveDiscussions: https://www.effectivediscussions.org/blog-comments. Open source, or $2 per month. Has Facebook and Gmail login.

As a blogger of 15 years, the issue to me now is that comments almost always take place in Facebook or Twitter, not on my blog.

I blog. Then post the link to social media. I'll get tens or hundreds of comments on social media, but maybe 3 on the blog itself.

Do any of these commenting systems have a way to say, "Any comments that happen on [Facebook/Twitter] should be added to the blog comment thread"?

Well, the technology is there already, with Webmention support.


I have these enabled on my own blog via the WordPress Bridgy plugin, which can report back on links to your article from Facebook, Twitter, Google+, Instagram and Flickr.


I doubt any of these "Disqus-like" services support this, because it sounds like it's solving a different problem. (Although it'd be useful if they did support it, the way earlier blogging systems display "pingbacks" as if they were comments.

Webmention is quite a cool tech, though it seems to have a very low adoption outside the indieweb community. The validation tool seems to be broken too [0] [1] and a lack of compliance [2] in the community. It's probably also not good that there is only one test suite, I'd feel more comfy if I could validate against more independent suites.

[0] https://github.com/aaronpk/webmention.rocks/issues/26

[1] https://github.com/aaronpk/webmention.rocks/issues/32

[2] https://github.com/aaronpk/webmention.rocks/issues/27

This was interesting :- )

Doesn't seem to work so well with Facebook to me? If I write a blog post and use Brid.gy: I'm getting the impression Brid.gy (https://brid.gy/) only lets me see [mentions about the blog post] that my Facebook account can see? If there's a public discussion about the blog post, somewhere at Facebook in a group of people I'm not connected with — then Brid.gy won't find it?

Is that how it works in general? I mean, the blog & web-mentions tech, will find web-mentions, only about things the blog author can see, via his/her own social media accounts? I'm then getting the feeling that ... if a blog gets popular, shared and discussed a lot at Facebook etc, 99% of all discussions & shares etc, won't be found, because the blog author isn't connected to those people on the relevant social media places. (?)

What's troublesome about systems like that is they invariably end up pulling FB's tracking code onto your blog.

Right, we don't want that.

I think it's technically possible to do the following:

1. I, as the blog owner, authorize this Facebook app to access my Facebook page.

2. I tell the Facebook app the URL of my blog.

3. That Facebook app watches my Facebook page for any posts linking to my blog.

4. When it detects a post on my page linking to my blog, it scans the comments of that post and automatically re-posts those comment to my blog's native comment system, outside the FB walled garden.

Ditto for a Twitter-authorized app.

This way, all the comments about my original content stick with the original content, rather than bound up in walled gardens.

While this all is technically possible, it probably breaks Facebook's terms of service.

What if I want to reply to a comment that was made on Facebook? How would the user be notified?

The Facebook app should sync comments on Facebook with those on the blog.

So, you could just reply on Facebook, which would then automatically get posted to the blog.

As for the other way around, when a reply is posted on the blog to a comment that was imported from Facebook, I think the FB app could handle that too, and post a reply to the Facebook thread: "Joe Foobar posted a reply to you here: [link to comment on blog]"

I don't think any commenting system has that feature. You're thinking about something that automatically integrated with FB/Twitter/etc? So if someone posts a comment about your blog post at FB, it appears on your blog too? (I saw your reply & clarification to someone else below.) I suppose if there was a way to do that, FB and Twitter would dedicate some time to stop & prevent & break that feature, because they want the discussion to happen at their place instead :- (

Maybe a text message asking the user to please cross post, could do some good? (but not much I suppose)

I've been thinking about if FB, Twitter, etc could be used as notification systems, so, if someone, X, posted a comment at the blog, and someone replied a few days later — then X got a notification via Facebook or Twitter. I had a quick look but didn't find a way to do that via FB. (Because then higher likelihood that people go back to the blog, reply, and continue discussing with each other.)

I was going to ask what blog commenting system you use, and say that if you added Facebook or Gmail login, maybe more people would post comments, since they wouldn't need to sign up and create an account, just to post a comment. — But now I had a look at a blog linked via your profile, and I see you already have FB and Gmail login.

There is an API of sorts that pings your blog if it gets published to eg; Hacker News but I can't remember the name currently.

It's opt in and I think Lobsters uses it? Anyway, it's not exactly what you're after as it wouldn't ping you about individual comments, just threads in general

That's not it. I don't want Facebook comments embedded in my blog. I want comments that were made on Facebook to appear on my blog's native comment system. Outside the walled garden.

what's the average facebook user/friend's incentive to leave a comment on your blog rather than on facebook?

if they leave a comment for you, sure I would put it on the blog. but if people are discussing the article, isn't it easier to do on facebook?

I believe they're imagining a system where any comments on Facebook/Twitter etc would be essentially mirrored.

Perhaps a webhook of sorts that pushes comments discussing a link to the link itself and would then be imported into their own comments database.

Of course, I doubt Facebook would do this seeing as there's no tangible benefit to them

just for completion's sake:

most people that use a service such as disqus use it in tandem with a static blog hosted on maybe github, gitlab or whatnot and these have a really neat alternative to this setup, and that's actually committing the comments automatically instead of serving them through js.

there is a FOSS appliance for just that, and it even offers a free hosted service


Interesting :- ) That one should have been in the list too yes. — I'd be worried about Denial-of-Service attacks & moderation. What if the blog gets popular? And "angry people" posts 9999 spammy comments. Even if one deletes them from the blog, they'd sill be in the commit history? (but I want a somewhat clean commit history that is readable to me)

And what if someone illegally post personally-identifiable-info (PII), even if one deletes it, it'd still be in the commit log, which I think would be illegal? Maybe StaticMan could rewrite the Git history to delete flagged & deleted comments (e.g. comments with PII)... But if it does that, the rebased history will cause problems when you try to push your next blog post to the repo.

Maybe if blog comments were in a separate repository whose history could be rewritten, without interfering with the main repo to which one pushes one's new blog comments.

Staticman supports GitHub PRs so you can vet/flag/delete comments as a PR and they don't end up in main branch commit history if you don't merge the PR. If you delete the PR branch eventually git gc in sync with GitHub's branch cleanup process will cleanup the dead commits, so there's a window when where that PII will be available, but it would eventually get tossed.

Ok, that seems like a lot safer, thanks for explaining

A better alternative is to have no comments at all (not joking). If the 'activation energy' of replying is higher, more thought will go into the reply.

I've started emailing people if I like what they've written.

Leads to much better discussions and relationships

Interestingly enough, it seems like a lot of blogs these days have entirely disabled comments. I'm not clear on all the reasons why, but definitely noticeable.

Sometimes this is just to avoid spam. I setup a simple API for testing for comment-spam in real-time here:


Likewise I have noticed higher end consumer products out of luxury boutiques do not show reviews.

Comments are often more interesting than the post itself. Pretty much all of Reddit is based on that notion.

Maybe. There's something like a conservation of interest. The best posts often have very tedious comments. The best comments are often corrections to incorrect articles.

And so is HN, I dare say.

Perhaps that's why we seem to be separating comments out into dedicated sites like Reddit and HN, rather than continuing to host comments directly on blogs?

I can recommend Isso, it's rather easy to install and use.

It also seems like the project is working on a moderation UI, I'm waiting on that.

isso hasn't seen releases in a while https://github.com/posativ/isso/releases

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact