feat: refactor pagination implementation

src/posts/2016/doj-takes-war-on-encryption-to-whatsapp.md

@@ -0,0 +1,14 @@
+---
+date: 2016-03-13
+draft: false
+title: DOJ takes war on encryption to WhatsApp
+tags: ['politics', 'security']
+---
+
+**[The EFF:](https://www.eff.org/deeplinks/2016/03/next-front-new-crypto-wars-whatsapp):**
+
+> The government's theory, that the All Writs Act gives it the power to compel American companies to write code and design products to ensure law enforcement access to encrypted content, is virtually without limits. No devices, and indeed no encrypted messaging services, would be safe from such backdoor orders. If the government wins in San Bernardino, it could even force companies to give it access to software update systems, and send their users government surveillance software disguised as security patches.<!-- excerpt -->
+
+The government is taking its war on encryption to WhatsApp's front door. This is, perhaps, even more terrifying than their effort to force Apple to hamstring its device security. It's one thing if the government can force its way in to devices but, oftentimes, services used on secured devices have their own, additional layers of security. This is the government attempting to compromise security further by making inroads in to security provided by messaging (and other) service providers.
+
+Chilling.

src/posts/2016/dutch-government-on-encryption.md

@@ -0,0 +1,12 @@
+---
+date: 2016-01-09
+draft: false
+title: Dutch government on encryption
+tags: ['politics', 'security']
+---
+
+**[Via Ars Technica](http://arstechnica.com/tech-policy/2016/01/dutch-government-encryption-good-backdoors-bad/):**
+
+> ...forcing companies to add backdoors to their products and services would have "undesirable consequences for the security of communicated and stored information," since "digital systems can become vulnerable to criminals, terrorists and foreign intelligence services."
+
+Exactly.<!-- excerpt -->

src/posts/2016/generating-responsive-css-grid-neat.md

@@ -1,7 +1,7 @@
 ---
-title: Generating a responsive CSS grid using Neat
 date: '2016-07-24'
 draft: false
+title: Generating a responsive CSS grid using Neat
 tags: ['development', 'css', 'sass']
 ---
 

src/posts/2016/javascript-topics-and-framworks-to-learn-in-2017.md

@@ -0,0 +1,16 @@
+---
+date: 2016-12-31
+draft: false
+title: Updating to the latest version of git on Ubuntu
+tags: ['Javascript', 'development']
+---
+
+[A fantastastic read](https://medium.com/javascript-scene/top-javascript-frameworks-topics-to-learn-in-2017-700a397b711#.2micvl2c8) by [Eric Elliott](https://ericelliottjs.com) on what to stay on top of in the ever-changing JavaScript ecosystem in 2017.<!-- excerpt -->
+
+Personally, I've been focusing in on [React](https://facebook.github.io/react), [Redux](https://github.com/reactjs/redux) and the tooling ecosystem surrounding both. I can't wait to see what else next year brings.
+
+I've been reading quite a bit this year as well and have particularly enjoyed:
+
+- _Functional JavaScript_ by Michael Fogus: [iTunes](https://geo.itunes.apple.com/us/book/functional-javascript/id657571134?mt=11&uo=4&at=11lvuD) | [Amazon](http://www.amazon.com/dp/1449360726/?tag=corydme-20)
+- _Learning JavaScript Design Patterns_ by Addy Osmani: [iTunes](https://geo.itunes.apple.com/us/book/learning-javascript-design/id552162547?mt=11&uo=4&at=11lvuD) | [Amazon](http://www.amazon.com/dp/1449331815/?tag=corydme-20)
+- _React: Up and Running_ by Stoyan Stefanov: [Amazon](http://www.amazon.com/dp/1491931825/?tag=corydme-20)

src/posts/2016/reuters-senate-push-for-encryption-legislation-falters.md

@@ -0,0 +1,12 @@
+---
+date: 2016-05-30
+draft: false
+title: Senate push for encryption legislation falters
+tags: ['politics', 'security']
+---
+
+**[Reuters:](http://www.reuters.com/article/us-usa-encryption-legislation-idUSKCN0YI0EM):**
+
+> Draft legislation that Senators Richard Burr and Dianne Feinstein, the Republican and Democratic leaders of the Intelligence Committee, had circulated weeks ago likely will not be introduced this year and, even if it were, would stand no chance of advancing, the sources said.
+
+Fantastic news. This bill (and the push behind it) was ill-conceived at best and would have caused untold damage were it to pass.<!-- excerpt -->

src/posts/2016/scriptable-backups-with-arq.md

@@ -0,0 +1,31 @@
+---
+date: 2016-04-24
+draft: false
+title: Scriptable Backups with Arq
+tags: ['Arq', 'backups']
+---
+
+I've been using Arq for my backups for several months now and have regular backups being pushed to both [Amazon Cloud Drive](https://www.amazon.com/clouddrive) and [AWS](https://aws.amazon.com). A big part of Arq's appeal is it's flexibility, configurability and the wide array of backup destinations it supports. In short, it allows you to own and control your backups.<!-- excerpt -->
+
+In addition to being a wonderfully designed app, Arq ships with a handy command line utility that lets you pause, resume and otherwise control your backups using simple commands named for the app. In order to use these commands, however, you need to include the executable in your shell's path variable.
+
+To accomplish this, I symlinked the Arq executable in to usr/local/bin. If /usr/local/bin isn't in your path, you can add it by adding the following to your .bashrc, .bash_profile or what have you:
+
+```bash
+export PATH=$PATH:/usr/local/bin
+```
+
+Next, symlink the Arq executable:
+
+```bash
+sudo ln -s /Applications/Arq.app/Contents/MacOS/Arq /usr/local/bin/Arq
+```
+
+Next, open up a new shell and try the following:
+
+```bash
+Arq pause 60
+Arq resume
+```
+
+Now you can easily control your backups from your CLI of choice or even script them from apps like [Alfred](https://www.alfredapp.com/) or [Control Plane](http://www.controlplaneapp.com/) (context sensitive backups anyone?).

src/posts/2016/throwing-together-a-blog.md

@@ -0,0 +1,17 @@
+---
+date: 2016-12-11
+draft: false
+title: Throwing together a blog
+tags: ['development', 'Statamic']
+---
+
+I've been working on this site for longer than I'd care to admit (years at this point). It's been through a few domains, two content management systems, multiple versions of those content management systems, countless designs and several different hosts. I'm really happy with where it's at and what I've learned putting it together.<!-- excerpt -->
+
+I started this site off running [Kirby](https://getkirby.com) on shared hosting. It's served as a design and development playground for me as I've learned and applied new things. It started off without being version and now the source for it is stored on [Github](https://github.com) and now runs on [Statamic](https://statamic.com).
+
+I started off writing the CSS and JS for the site
+manually, before generating a Grunt build process, breaking out the styles to be more modular and rewriting them in SCSS. Dependencies are now sourced from [npm](http://npmjs.com) and [Bower](https://bower.io).
+
+Instead of running the site on shared hosting, it now runs on a LAMP [Digital Ocean](https://m.do.co/c/3635bf99aee2) box using PHP7 and [mod_pagespeed](https://github.com/pagespeed/mod_pagespeed), both of which have made a tremendous difference in terms of site performance.
+
+As it stands now, I'm thrilled with where this site sits, but I'm curious to see how else I can continue improving it.

src/posts/2016/wired-the-year-encryption-won.md

@@ -0,0 +1,10 @@
+---
+date: 2016-12-30
+draft: false
+title: The year encryption won
+tags: ['security', 'privacy']
+---
+
+**[Wired:](https://www.wired.com/2016/12/year-encryption-won/)**
+
+> It's not a firm guarantee, and who knows what a Trump administration will bring. For now, though, it's enough to appreciate the gains encryption made in 2016, and be hopeful that 2017 will only build on them.<!-- excerpt -->