When speaking of web analytics and privacy, its not something I typically think of going hand-in-hand.
I mean, conventional wisdom may argue that we want to know as much as possible about those visiting our sites so we can ensure we’re writing content properly, building features out properly, and targeting all of the necessary metrics to make sure our site is successful.
And there’s truth to that, sure. But there’s still a level of privacy around what the user is sharing (and perhaps how it’s managed, who stores it, for how long, etc.).
Last month, I spent time thinking about why I’d want to do so versus just letting them sit. Though there are multiple reasons for doing so, there’s one reason to which I kept returning (and plenty of others I’ll outline in moment).
But first, the TL;DR is this: There’s a single side project I want to work on without any distractions.
That’s it. Nothing elaborate, fancy, or groundbreaking. The thing about having a variety of other repositories available, though, is that there are occasional emails about bugs, feature requests, etc., all of which are appreciated but most of which I don’t have time on which to focus at the moment.
Instead, I think my time can be better spent on other work. And I think I want to spend my time on other things.
Earlier this year, I talked about the move from Pressware to WebDevStudios but I didn’t go into much detail. However, last week, I had the ability to do a deep dive into what it’s like to work to work with an agency again.
But one problem that comes with using these as my main DNS servers (and maybe others, I don’t know as I’ve not tried them) is that when I’m using cURL to make requests to a third-party server, it will often result in an a 404.
But remember that this series was motivated by an email from someone who thought that I could do a better job of explaining how transients and caching work in WordPress and why it’s important to understand how everything works in tandem with each other.
So in this post, I’m aiming to bring it all together and talk about how the Transients API works in conjunction with MySQL, why it’s important to understand the relationship, and how to handle this moving forward.