This blog post is a follow-up to It’s Time to Ditch Gmail. It began as a review of Fastmail, and my experience of moving to it from Gmail, but I quickly found myself going on a tangent. Since privacy was the main driver in my decision to move to Fastmail, and using a custom domain is one of the ways that I protect my privacy, I figured it was important enough to warrant its own post.
One of the factors that made it easier to move away from Gmail is my use of a custom domain for most of my mail. Before moving to Fastmail, this domain was tied to a GSuite account which forwarded everything to my standard Gmail account. This made switching in anger much easier, as I had fewer accounts to log in to and update my email address, and those that were still pointing directly at Gmail tended to be older low-value accounts that I no longer use anyway.
In this article though, I want to take a detour to explain why I use a custom domain, and how it can aid your privacy. Continue reading →
I haven’t written much about privacy on this blog, despite often behaving, by some people’s standards, like a paranoid schizophrenic where my data is concerned. Until fairly recently I used to run a rooted phone with XPrivacy installed, which is about as private as you can get without ditching smartphones altogether. These days I’ve gone back to a stock un-rooted phone, partly because Android permissions have improved (although you do have to be careful with apps targeting older APIs), and partly because rooting is more risk and burden to me as a user. Also, some apps actively attempt to block rooted devices for quite legitimate (if, I would argue, misguided) reasons.
Anyway, I could go on for hours about Android privacy, but the subject of this post is Gmail. We all know that Google mines your personal data for targeted advertising purposes. But when giving data to companies, there’s a balance between functionality that is useful to you, and commercialising your data for purposes that, often, are not in your best interest.
While Gmail was once an innovative service, I’d argue that the scales have long been tipped in favour of commercialisation, and that today the data cost of Gmail outweighs its value as a service. Continue reading →
However there are a few problems with the approach, some of which are noted in the original post.
The main one is that if we remove a policy from the configuration, applying it again will not remove the objects from Vault. Essentially it is additive only, and while it will modify existing objects and create new ones, removing objects that are no longer declared is arguably just as important.
Another problem is that shell scripts inevitably have dependencies, which you may not want to install on your shell servers. Curl, in particular, is extremely useful for hackers, and we don’t want to have it available in production (in our environment, access to the vault API from outside the network is not allowed).
Finally, shell scripts aren’t easy to test, and don’t scale particularly well as complexity grows. You can do some amazing things in bash, but once it gets beyond a few hundred lines it’s time to break out into a proper language.
So that’s what I did.
The result is a tool called vaultsmith, and it’s designed to do one thing – take a directory of json files and apply them to your vault server.
This is a blog post I originally wrote more than two years ago, in reaction to “spirited debates” I was having with developers. I didn’t post it, but perhaps I should have! Anyway the ideas within are as true to me now as they were then, so I thought I’d post it today after a bit of revision.
How many times have you had a developer shrug their shoulders at you and say “it’s an upstream bug”?
I heard it today, and it is so, so wrong, that it is practically an admission of guilt.
Do you say that to your customers when their personal data is leaked from your database? When your app crashes their device? No? Good, because it’s your problem.
It’s great that you can use third party libraries to do your job more efficiently, but doing so does not absolve you of responsibility if the product breaks. You made the decision on what library to use, and you are ultimately responsible for delivering functionality. Continue reading →
If you’re reading this and don’t know me personally, you’re probably aware that Crashplan decided to “sunset” their Crashplan Home offering on August 22nd last year. No new subscriptions are being taken, and it will cease to exist from August 2018. Unfortunately, my subscription expired in December.
I was hugely satisfied with Crashplan, and thought it was by far the best online cloud backup solution in the market for the average home user.
It offered free peer-to-peer backups which meant I could backup my devices to my own server, or even trade encrypted backups with friends.
The client to backup to your own devices was free, and the cost for online cloud backups was a very-reasonable $150 USD for 12-months of unlimited backup storage.
By virtue of being written in Java, the client was available for Windows, Mac and Linux (I have all 3).
It supported headless operation, albeit with a bit of jiggery-pokery, i.e. editing the client config file to point to another agent via an SSH tunnel. This meant I could run it on my home NAS device, which naturally stores my important data (Photos mainly).
No limits on the number of devices that were backed up, or charges per-device.
Naturally, I was disappointed when they announced they were discontinuing it. “No worries!” I thought, there must be something else out there. As it turns out, Crashplan Home was almost too good to be true. Continue reading →
Some of the links in this article are Amazon affiliate links, which pay me a commission if you make a purchase.
I could have brought a plain old Ryzen, a Core i7 or even another Core i5. But with Intel sitting on its hands the past 5 years in the face of no competition, I decided it was time to splash out and reward AMD for not only investing in CPUs again, but making an interesting high-end desktop product while not nickel & diming its customers over PCI-E lanes.
I don’t really need 12 cores. Other than general browsing, my PC is used for work, (coding) plus a bit of gaming, and a gaming CPU this is not. Running multiple VMs and M.2 devices without slowing down will be nice, but this build is mostly overkill for my needs. And that’s really the point! Continue reading →
Much to the chagrin of anyone that uses a web browser on my PC, with particular apologies to my girlfriend, I’ve been an enthusiastic user of Vimperator for several years. Vimperator is a Firefox extension that turns it into a keyboard-driven browser, one that behaves much like the text editor Vim. Unfortunately, Mozilla has deprecated the XUL extension API that vimperator and many legacy extensions depend on, in favour of the web extension standard pioneered by Google with Chrome.
I can understand why they made this change. Legacy extensions are a large source of pain, can pose a security risk to host systems, and make invasive, sometimes unstable changes to the behaviour of the web browser. Mozilla often took flak from users for poor performance caused by poorly-written extensions, which were sometimes installed without the users’ knowledge or consent (Skype click to call extension, I’m looking at you).
What’s more, XUL extensions are partly responsible for the slow roll-out of their multiprocess implementation, called Electrolysys.
All this probably explains why Mozilla decided to adopt Google’s extension standard, and drop XUL. Unfortunately, Vimperator, a volunteer project, looks as though it will be a casualty of this decision, and it is highly likely that it never work after the legacy extension APIs are removed in Firefox 57.
Distutils was and still is the original tool included with the standard library. But then setuptools was created to overcome the limitations of distutils, gained wide adoption, subsequently stagnated, and a fork called distribute was created to address some of the issues. Distutils2 was an attempt to take the best of previous tools to support Python 3, but it failed. Then distribute grew to support Python 3, was merged back in to setuptools, and everything else became moot!
Unfortunately, it’s hard to find reliable information on python packaging, because many articles you might find in a Duckduckgo search were created before setuptools was reinvigorated. Many reflect practices that are sub-optimal today, and I would disregard anything written before the distribute merge, which happened in March 2013. Continue reading →
As a Sysadmin who works on a keyboard all day, I was enamoured by Jeff Atwood’s post about his CODE Keyboard, that he developed in partnership with WASD Keyboards. Essentially, the CODE Keyboard is a pre-spec’d standard WASD keyboard, with Cherry MX Clear switches.
If you have no idea what I’m talking about, you should read WASD’s Mechanical Keyboard Guide, which covers the different types of switches and their characteristics.
I’ll admit I didn’t do a lot of research. After a quick read on the site about the switches, I figured brown would probably suit me best, as I didn’t want to annoy my neighbours too much, and I chose the smaller Ten-Key-Less layout to keep the mouse closer (rarely am I entering large numbers in sequence, so the numeric keypad simply wastes space most of the time).