Retiring Disqus

Turns out Disqus just got bought, and considering I know bothing about Zeta Global (sounds sinister though), and since I was already kind of on edge about Disqus’ privacy stuff, I’m killing the comments on this site.

Credit to Philipp Hansch who saw this before me, and made the same move.

I’ve tried this before, but now I think I’m really going to pull the trigger on setting up Staticman for comments. It lives in GH issues, which is ace for me.

It’s also prompted me to get automated publishing happening here again–all I have to do now is push or merge to my production branch, and Codeship pushes everything to AWS now (which should make getting scheduled publishing back easier!)

For those who want to save their comments (like me, with my, like, 3 or 4 comments total), Disqus have an export guide. No idea how long that will be working though. Do it soon?


Edits

2017-12-15

This post now has a bunch of dumb comments I made while I was working on setting up Staticman. I’ll probably update and move them over to an explainer post for the process in the future.


10 Comments

Sean

I’m adding this comment because I just changed the format to JSON and I have no idea what will explode. Also, I should really be packing now.


Sean

This is a reply to an existing comment.


Sean

This is a reply from a mobile device


Sean

This should be a reply to comment ‘12a33’ (fake ID).


Sean

This should be the second level comment; also, it should indicate the comment author is the page author.


Sean

This should be a top level comment, and flagged as written by the page author.


Sean

This comment should come after comment ‘0edc92e0-e343-11e7-8a6a-f508145427bd’ if the Liquid date sorting is working on the comments array.


Sean

This should be a reply, and the MD5 of the author ID secret should match what I expect.


Sean (author)

It was a reply, but the hashes did not match. Rerunning the hash to get new reliable value.


Sean (author)

OK, last time to check for consistency.


Leave a comment