11–20 of 52 posts
To make public the comments, you can use a public mailing list or rebuild the commented static page upon reception of a comment (email). Of course you have to take care of security threats (HTML injection, ...)
I'm more of the opinion that if you're sharing something, especially in a blog, then you should never add a comment section. People don't comment unless they have a point that they want to put across, which in 99% of the cases will be something negative. Just look at HN and (ugh) Twitter -- almost every discussion revolves around people trying to find things to complain about. I instead share a contact e-mail. This w…
I'm more of the opinion that if you're sharing something, especially in a blog, then you should never add a comment section. People don't comment unless they have a point that they want to put across, which in 99% of the cases will be something negative. Just look at HN and (ugh) Twitter -- almost every discussion revolves around people trying to find things to complain about. I instead share a contact e-mail. This w…
When a user submits a comment, echochamber.js will save the comment to the user's LocalStorage, so when they return to the page, they can be confident that their voice is being heard, and feel engaged with your very engaging content. It does not make any HTTP requests. Since LocalStorage is only local, you and your database need not be burdened with other people's opinions.
I'm more of the opinion that if you're sharing something, especially in a blog, then you should never add a comment section. People don't comment unless they have a point that they want to put across, which in 99% of the cases will be something negative. Just look at HN and (ugh) Twitter -- almost every discussion revolves around people trying to find things to complain about. I instead share a contact e-mail. This w…
that's a really overly negative view. You can be part of a healthy (small?) community and have normal interaction with your commenters or with the writer, as a commenter. Maybe the trick is to not get to real success numbers, but I could think of dozens of blogs I read with 0-10 comments per post and no discernible amount of trolling, spamming (well, automated tools help ofc) and so on.
There's the occasional lucid, intelligent comment that truly elevates a post or inspires someone, but they are by far the rarity.
On the other hand, I'm speaking of comments on larger sites, not small blogs.
I have no interest in allowing comments on my personal blog. If people want to engage me, they will do so directly.
Earlier quoted context omitted.
that's a really overly negative view. You can be part of a healthy (small?) community and have normal interaction with your commenters or with the writer, as a commenter. Maybe the trick is to not get to real success numbers, but I could think of dozens of blogs I read with 0-10 comments per post and no discernible amount of trolling, spamming (well, automated tools help ofc) and so on.
Comments, in my opinion, add nothing to a site. Most of the time they're just noise. Often, they're a distraction. There's the occasional lucid, intelligent comment that truly elevates a post or inspires someone, but they are by far the rarity. On the other hand, I'm speaking of comments on larger sites, not small blogs. I have no interest in allowing comments on my personal blog. If people want to engage me, they wi…
It's a really competitive space... but it's been fun.
I'm more of the opinion that if you're sharing something, especially in a blog, then you should never add a comment section. People don't comment unless they have a point that they want to put across, which in 99% of the cases will be something negative. Just look at HN and (ugh) Twitter -- almost every discussion revolves around people trying to find things to complain about. I instead share a contact e-mail. This w…
Could it be that your site topics draw in negative folks? Some topics can evoke emotional feedback. In that case you might consider EchoChamber [1] javascript that stores comments in the browser. This is not my project. When a user submits a comment, echochamber.js will save the comment to the user's LocalStorage, so when they return to the page, they can be confident that their voice is being heard, and feel engaged…
Back when I set it up, I couldn't find a ready-made solution that looked good enough, so I chose to roll my own (basically an email form plus a hack to extract the json comment data from the message and rebuild the site). Since I'm dealing with a low volume of feedback, I don't have an issue with moderating/approving each comment beforehand, and spam isn't a problem... but this article could sure be helpful if that ever changes.
I'm more of the opinion that if you're sharing something, especially in a blog, then you should never add a comment section. People don't comment unless they have a point that they want to put across, which in 99% of the cases will be something negative. Just look at HN and (ugh) Twitter -- almost every discussion revolves around people trying to find things to complain about. I instead share a contact e-mail. This w…
The comment field medium isn't particularly conducive to meaningful and interesting conversations, which is ultimately what I want to promote if I put something on the Internet. At best you get posturing.
Emails (or blog posts) require more thought to be put into what's written, and they also even the playing field. It feels a lot more like a conversation compared to the blogger-commenter relation.