# HG changeset patch # User Dirk Olmes # Date 1452094998 -3600 # Node ID 21fd842091259deb80165132346e3e2ec7456296 # Parent 7aa5f064106e90c5b2603471862badf35174e407 Blog post about switching to the pelican comment system diff -r 7aa5f064106e -r 21fd84209125 content/pelican_comment_system.md --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/content/pelican_comment_system.md Wed Jan 06 16:43:18 2016 +0100 @@ -0,0 +1,9 @@ +Title: Comments for this blog use pelican's comment system +Date: 2016-01-06 +Lang: en + +One thing that annoyed me while [switching my blog to pelican](|filename|./blog-switched-to-pelican.md) was the lack of a good comment option. My motivation for self-hosting the blog is to have control over my data and that includes comments! The use of a cloud service like Disqus obviously defeats this purpose. + +I sat down and did my own [pelican plugin for comments](https://github.com/dirk-olmes/simple_comments) back then. It was fun to learn how to write pelican plugins but I only ever finished a very basic implementation. + +Recently, I stumbled over the [official pelican plugin for static comments](https://github.com/getpelican/pelican-plugins/tree/master/pelican_comment_system) and decided to give it a try. It turns out to be very similar in what I did but it's far more feature rich. So I ditched my plugin and switched over - that was easy.