Some client configurations (Browsers with tracking-blocking enabled, or
networks with [Pi-holes](https://pi-hole.net/)) will block any calls
to `www.google-analytics.com`. This makes me sad! I'd like to know
how many folks are reading my blog!
This commit represents a workaround. Instead of telling the client to
send data directly to Google (which would trigger Tracking-blockers), I
instead tell the client to send it to the `/analytics` endpoint on my
domain, which will then get forwarded to Google. Neat!
But! If a reader has blocked tracking, we should respect that! So I'm
not actually enabling this in my blog until I have also built an
"opt-in" mechanism, where readers can decide if they want to send me
tracking information or not.
"Why didn't you make tracking opt-in to begin with, Jack?" - well, I
kinda addressed that
[here](https://blog.scubbo.org/posts/commenting-enabled/), but you're
right that that would have been a little more ethical. Still - enabling
Google Analytics didn't feel _too_ bad (since anyone who cared about
detecting and blocking it would still be able to with standard methods -
and I assume that anyone reading my blog will know how to), whereas this
new approach feels like a circumvention of their agency.
CodeBuild was getting an error:
```
Error: Error building site: TOCSS: failed to transform "ananke/css/main.css" (text/css): resource "css/ananke/css/main.css_af7eae7717e76be05924f27bac629e80" not found in file cache
```
I suspect this is because an earlier version of the Ananke CSS file was
being cached, but the submodule pulled in a new Ananke commit that
requires a new version. Perhaps? Who knows. I cannot replicate the
problem locally, so I need to push-to-test the behaviour in CodeBuild :(
