- 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.
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.
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. (?)
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.
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.
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.
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.
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.
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.
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?
It's hard as hell working on a startup for 10 years, and their team's consistent commitment is so impressive.
My first startup was YC W08, Tipjoy. We were just two people, my wife and I. I feel lucky to have shared an office with Disqus way back in 2008. Besides the founders, they and an engineer and an engineering intern. It was a great vibe in the office.
In that time since, I've shut down a startup, worked at two unicorns, started my 2nd startup, and just sold it. Time is voracious. This really highlights the marathon sprint Disqus has been through.
An acquisition was pretty much an expected outcome since there was no way a company with $10.5 million in VC funding over 10 years could go public. IMO the comments as a service space is a terrible fit for the VC model. It's easy to get to scale by offering a free service, but very very hard to monetize. You can force ads on your users, but you end up being at the receiving end of users' wrath, as was the case with Disqus.
I've tried talking to VCs with the idea for a Disqus alternative [0] and many of them shared the same concern : market size. It's tiny. A back of the envelope calculation gives me a number between $100 million and $200 million in ARR potential with most of the revenue being generated via ads instead of paid subscriptions. Disqus serves 17 billion monthly pageviews which translates to roughly $1.7 million in MRR. So yeah, I guess this space is more suited for the artisanal variety (bootstrapped companies) than the VC model. Another guy who's been working on an alternative for 3 years is `foxhop with Remarkbox [1].
I just spoke with someone that works with Zeta (former XL Media). She said its not about the data they have but rather how they can run their existing AI over keyboard's of millions of users. 30% of US based browsers have some sort of zeta cookie on their PC.. knowing what they type about is priceless.
For a marketing and ads company, any script that's embedded on multiple websites is an attractive target for acquisition.
There's nothing terribly special about Disqus in this regard: they just have a decent install base. Some lip service fluff about AI/ML mining the comments for sentiment, likely to give the impression for ad sellers that they can target specific demographics, but this is something they can fake -- grouping user cohorts solely by the overlap of sites they visit is an adequate proxy.
It does, however, show that Disqus' business model was the usual fantasy: burn cash to acquire users, coast by waiting for an acqui-hire until you're desperate, then introduce ads, hemorrhage users, then firesale cash out. This is a tried-and-true strategy for many web properties, from image hosts to chat services, but it truly doesn't make sense here, because you'd figure that their subscription plans should've been priced high enough to pay the bills. They badly misjudged their market.
>Disqus gives these marketers the ability to target users based on their interests. You can infer quite a bit about people simply based on which sites they comment on, after all.
So we can expect more targeted ads in Disqus embeds from mining user patterns. The platform is a already a mess; between making 105 network requests to 20+ domains associated with tracking, malware, ad platforms, and shady fingerprinting services, and the fact that adding Disqus costs you upwards of 6 seconds [0], this announcement is making things more user-hostile.
Disclosure: I created an open-source, privacy-focused alternative called Commento [1] so my views on Disqus might be somewhat biased :)
I will also be offering it as a subscription-based service very soon as many people have asked me for one (the open source version will stay free software forever). It'll have near feature-parity with Disqus and you'll have the option to import all your Disqus comments. If you're interested in beta-testing, please let me know (email in profile). Apologies if I'm breaking HN etiquette.
Neat ! I wanted to add a comment section on my personal blog but I didn't want to use Disqus for privacy reason. I tried using Isso[1] but installing it on my server is really a PITA (I don't know the Python ecosystem, is it always such a mess ?). I was on the verge of developing my own commenting system in Rust, so I can have a stand-alone binary for ease of installation, but Go has the same property, which makes your system really attractive, thanks !
About the docker part: I should edit that. I wasn't making point releases back when I wrote it and docker was the easiest way to get it running back then.
Nit: I think you mean "disclosure", not "disclaimer". I don't usually correct this, but to me the poster seems less legitimate saying disclaim when they mean to disclose a conflict of interest.
Series F?! Heh. It's amazing that Disqus is worth anything at all. Standard Wordpress spam filtering takes care of bots on low-traffic sites, and the friction of yet another pile of tracking junk seems high enough to dissuade people from commenting, or "engaging with your brand," or whatever it's called.
>Disqus gives these marketers the ability to target users based on their interests. You can infer quite a bit about people simply based on which sites they comment on, after all.
Not only that but also they will get a partial browsing history (on subset of websites with embedded Disqus comments) of users which have third-party cookies allowed.
Mozilla, NY Times, Washington Post & others have contributed to creating the Coral Project which looks like it has a much better comment system for websites to use. It's no where near as easy to use but you can get it up & running with Docker pretty quick if you know how to use Docker. If you have a larger audience, the engagement features really seem worth the effort.
A source close to the two companies tells us that the acquisition price was close to $90 million. This marks Zeta’s eleventh acquisition since it was founded in 2007.
Apparears adding ads worked out well for them. However distasteful most of us think they are, obviously they were able to get some non trivial monetization from them.
There are a lot of competing services and projects around, it's a mystery to me why none of them have gotten any traction yet. It's also fairly trivial to self host an opensource comment system, or roll your own. Does anyone here have any insight into why this isn't a more popular option?
I think this is mostly due to services like Disqus targeting the CMS space like WordPress or Squarespace heavily, while at the same time making deals with established online presences like online newspapers, etc. Essentially, while it may seem trivial to you or me, we aren't their target user, they want low hanging user fruit. Eg, copypasta this one line and it all works!
All comments now sold?! Somebody/we need to focus on self hosting JS comment system like isso but more user friendly and less paranoia (Gravatar and social media support and email notifications). Still have not seen any good comment system self hosted... the best is maybe Wordpress but even with Jetpack it's not as good as Disqus IMHO. Talk by Mozilla looked promising (but I did not liked the UI design too much) but it requires registering/sign in. Any alternatives?
Idea: Send comments as e-mail plus save it in cookie, so when the commenter reads the comments he sees his/her comment. Then a moderator or blog owner hooks his CMS or static site generator into the e-mail program/service and he/she can also reply to comments by replying to the e-mail! Or delete the comment by deleting the e-mail. He/she could use a dedicated e-mail box like comments@yourdomain.com. It would even work without JavaScript (form action mailto)! And no server required except a e-mail service.
I've been doing something like this, but cruder (no cookie) on my personal site for some years: https://lee-phillips.org/. I like to be able to decide if a comment is useful for my readers before including it on the page.
How will commenters submit their comments? Would they be required to enter their email? Or are you implying an email address would be generated for them to associate with their activity/comment chain?
<form action="mailto:comments@yourdomain.com">
<input type="hidden" name="subject" value="A new comment on the thingy" />
<textarea name="body" rows="10" cols="41"></textarea><br>
<button type="submit">Submit comment</button>
</form>
When the form is submitted the default mail program will be started, subject will be the subject and body will be the body. Now assuming the user does have a e-mail client, all he/she has to do is to click send.
You can then read, delete, and reply to comments, and even send private replies, all via your e-mail client. Then you add the comments to your web-site either manually, or have a script do it automatically.
Effective Discussions (ED) is an open source & track free & ad free alternative to Disqus. There's €2 per month hosting too, if you don't want to maintain your own server.
I deleted my disqus after they installed ads a few months back. I am not anti-ads but these ads were very distasteful (ie shady stuff like weight loss products)
It's a pity since they provided nice commenting platform, much lesser evil than Facebook comments.
Was seriously gaining traction on politics sites since all trolling will reliably drown, and you could ban annoying people on per person basis. If only they also solve how to drown undesirable downthread comments...
Yes, I hold no such illusions. It was more intended as a indication that I am no longer interested in their services after the news of this acquisition.
Unfortunately the "Other" option when deleting the account did not give opportunity to comment on why the account was closed.
Hopefully they will see a large number of users jumping ship now in the coming days.
- 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.