-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Blog Comments #98
Comments
Disqus is certainly the most popular system for hosting comments, but it's proprietary and bad for privacy. (See also #43, #91.) I found an alternative but someone would need to host it. |
FWIW, hosting comments on our own server seems silly, especially because if we do that, we might as well just host the webpage itself. (Although I guess its less bad if only the comments go down, rather than the whole webpage). Also I agree wrt. disqus. While it certainly is the most popular option...bleh. With that being said, I don't really care about blog comments anyway, as they don't seem super valuable to me, so I personally don't care too much what we end up using. |
Well the alternative to "people using disqus to comment" is "people using twitter to comment", and it's (1) just as proprietary, (2) just as bad for privacy, (3) not amenable to thought-out discussion, and (4) un-archivable and lost after a week. If we did add Disqus (or another alternative), some people would keep using Twitter for comments, but at least some content would stay close to the post and may encourage discussion. I setup Disqus for my PhD lab blog and we did occasionally receive valuable comments. Random example: Your first Coq plugin. |
That is 'an' alternative, but not 'the' alternative. For example, we could use github for comments. In fact, I actually think that is a better idea than disquss. Because: A) We can then export the comments should we choose to go to another platform. B) Uhh...it makes me irrationally happier? I guess that's always a plus. ;) |
Here is an example: http://hydroecology.net/using-github-to-host-blog-comments/ |
Oh, also, I tried it out on Video, and its actually not too bad: videolang/website@c62a1c4 Also also, just look at the overhead disqus has: http://donw.io/post/github-comments/ |
Sure, I'm fine with other solutions than Disqus if someone is willing to put the work in to deploy them. Here I guess that means creating a new github repo for those comments, and sending a PR with the HTML magic to make it happen. @LeifAndersen, are you volunteering? |
Nope. I still don't like blog comments in general. I have honestly never really seen them turn into a useful discussion. |
I just saw a solution I thought about before (when reading this thread the first time): on-demand loading of Disqus. See example (in the bottom, there is the "Show comments" link that fires a JS action called I still miss the comments section becuase I see many interesting comment threads in personal blogs like Bob Harper's or Neel Krishnaswami's ones. |
I think this is a reasonable compromise. |
I posted a preview here (due to paths messiness, my fork can't render Blog but this page I fixed manually). |
Oh, I like that preview! |
At @gasche's suggestion, we should probably add comments to the blog because otherwise all discussion is necessarily limited to Twitter. My opinion is that Disqus is a good option because the site is statically hosted, and we probably don't want to maintain our own comments back-end. It does, of course, have the disadvantage that it's proprietary and we don't really control it, but I've had positive experiences using it in the past.
The text was updated successfully, but these errors were encountered: