Going Cookieless

Going Cookieless

Going cookieless has been harder than you think.

Here is the back story, I’ve been wanting to get back into blogging for a while and was encouraged to do so by a YouTuber that I watch regarding Linux who mentioned Hugo the static site generator. This did help quite a bit as I have been using WordPress for some years and while it does the job it does feel quite big and clunky for what I use it for.

So while playing in a virtual machine I started to like the way Hugo did things and wondered if I could rebuild my blog using it and looking into the new laws around data protection and cookies in the EU I started to think this is never worth it. The problem is for a hobbyist it’s just too many hoops to jump through. So as I had very little comments on my Wordpress I decided I didn’t need them, while that was my overall goal to spark conversations about the movies I watch or the books I read the wasn’t a huge need so there was one data point I no longer needed to worry about, so on to cookies.

Now I was quite surprised about cookies because I had to removed Google Analytics and Adsense years ago as it became apparent that I wasn’t going to make it big or make any money off the blog. However, I was still using Cookies even from Cloudflare my CDN. This surprised me for some reason as they were injecting the cookies for security measures which I thought was valid but it hadn’t crossed my mind that they would be me doing that when I installed it. While considering my options I decided to remove Cloudflare as well.

Overall I am happy with my move to go Cookieless and not have to worry about GPDR and EU Cookie Laws because there are none but what that means and whether it withstands the test of time is still to be tested. To achieve this cookieless dream it also means no embedding YouTube videos and being careful what widgets you add to your site as they might still add cookies so we will see. The major advantage I have with my current setup is that everything is in HTML and there are no database calls to add security risks.