Live data from Hacker News

Moving from Disqus to Schnack

blog.webkid.io

11–20 of 120 posts

Re: Moving from Disqus to Schnack

#11
post #2

So in order to use this, you need to host a new Node app and SQLite database on your server. Also, things like spam control are now back on you. So why not just use a CMS or blog engine which supports traditional server-side comments? I suppose there is a case if you're hosting static HTML pages but still want them to be commentable, but how many people are doing that? I don't get the use case for this.

If you want some dynamic comments why not just use hypothes.is, which is about as minimal as you can get?

Re: Moving from Disqus to Schnack

#12
I thought the whole advantage of Disqus was that you can keep your static blog static w/o hosting the server machinery for handling comments a la Wordpress?

Schnack takes you back to square one? At that point why not throw up a wordpress install?

Re: Moving from Disqus to Schnack

#15

I thought the whole advantage of Disqus was that you can keep your static blog static w/o hosting the server machinery for handling comments a la Wordpress? Schnack takes you back to square one? At that point why not throw up a wordpress install?

One advantage of not using WordPress is not having to spend a couple hours every week restoring the latest backup you have because you got hacked again.

Re: Moving from Disqus to Schnack

#16

I thought the whole advantage of Disqus was that you can keep your static blog static w/o hosting the server machinery for handling comments a la Wordpress? Schnack takes you back to square one? At that point why not throw up a wordpress install?

One advantage of not using WordPress is not having to spend a couple hours every week restoring the latest backup you have because you got hacked again.

Been running WordPress with WordFence, Akismet antispam, and CloudFlare on a site that gets a sizable amount of traffic. No hacks yet - it's not the same insecure mess it was a decade ago.

Re: Moving from Disqus to Schnack

#17

I understand the sentiment to move away from Disqus. How does this project compare to Mozilla's Coral Project[0]? [0]: https://coralproject.net/products/talk.html

Developer with The Coral Project here.

Schnack seems to provide a simple solution to the "let us put some comments on the site" in a very simple and pleasantly small package. (Like seriously small, we're jealous of those numbers :))

Talk on the other hand provides a full admin panel for moderators, a robust plugin system for configuring every part of the experience.

Admittedly, not every small blog is going to need all of our features. If you want comments to work on your small site, Schnack seems to suit that role fine. Talk on the other hand is currently supporting millions of users and tens of millions of comments. It's a matter of scale really, both are great solutions that take the data out of a marketers hands.

Re: Moving from Disqus to Schnack

#18
post #7

Earlier quoted context omitted.

Nothing's stopping you from running a self-hosted solution on a different domain.

Sure, but then you have to run a self hosted solution on another domain. It's far easier if someone else is willing to do it for you at a low cost (or even free).

According to the article, this "free" service comes at the cost of their readers privacy, not being in control of your whole blog (comments) and increased loading time because of the size/requests needed.

Re: Moving from Disqus to Schnack

#19
I make this type of comment a lot, but what's up with naming nowadays?

How is Schnack pronounced? How easy do you think it would be to tell somebody to try it out and how high are the chances that they'll misspell it and give up finding the site?

I don't get it.

Post reply on HN