21–30 of 120 posts
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.
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.
Here is the translation including audio: https://dict.leo.org/englisch-deutsch/schnack
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.
And I don’t think software projects with inscrutable names are a new thing. I still have no idea how to pronounce “PostgreSQL”, for instance.
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.
I assume it’s like snack, but with an initial sh sound. And I don’t think software projects with inscrutable names are a new thing. I still have no idea how to pronounce “PostgreSQL”, for instance.
I haven't looked at the repo yet, but I wonder if it would be possible to make the datastore pluggable so that you could replace SQLite with, say, DynamoDB. It seems like at that point you could potentially keep everything serverless.
Barring that, would it be possible to separate out the frontend code and define an API such that a lambda function and serverless backend could be produced for this?
Disclaimer: I work for this company.
5-10 years ago I used to get 2-3 digit views on my posts. And I used to use Wordpress / Blogger and the like.
Then, when it became fashionable, I spent a lot of time (at least 20-30 hrs, and mind you this was not the geeky kind of work, it was like refactoring code using just grep) converting the blog to one of those static generators, and I suspect that I spent more time migrating all posts than the TOTAL TIME all readers combined have spent on my blog since then.
Now I am almost regretting migrating and definitely have no interest whatsoever in spending any more time doing DevOps for the blog.
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 a…
That seems like an unusually low number of comments per user, best case 99:1.
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 are interested in an alternative to Disqus, take a look at Graphcomment, there is a free plan as well, plus we dont resell your data. https://graphcomment.com Disclaimer: I work for this company.
Build distinctly better moderation tools, and the experience will be enjoyable, too.