Longest blog post title ever. Anyway, this is a summary of how to get started with a Ghost blog running on a DigitalOcean droplet if you want the blog to be accessible using your own domain name. I decided to write this article because, while the procedure is far from complicated, it requires several steps (you have to work with your Ghost blog configuration files, with your DigitalOcean account and with your domain name registrar) so it’s easy to get confused and miss something.
Page 3 of 13
After registering my most recent domain, I have received way more spam&scam emails than usual. This time I received a couple of emails that made me giggle harder than the other ones, so I decided to share some of the fun with you. Hopefully it will also help some users out there who might not be too technically-savvy to avoid falling for these pathetic scams.
I have recently upgraded my pool of mirrors to double my storage space and, upon rebooting the machine, I received this email from the FreeNAS server:
freenas.local kernel log messages: > GEOM_ELI: Device ada0p1.eli destroyed. > GEOM_ELI: Detached ada0p1.eli on last close. > GEOM_ELI: Device ada2p1.eli created. > GEOM_ELI: Encryption: AES-XTS 128 > GEOM_ELI: Crypto: software > GEOM_ELI: Device ada1p1.eli destroyed. > GEOM_ELI: Detached ada1p1.eli on last close. > GEOM_ELI: Device ada3p1.eli created. > GEOM_ELI: Encryption: AES-XTS 128 > GEOM_ELI: Crypto: software -- End of security output --
The interesting thing is that I have never enabled encryption for this pool, so this looked weird.
FreeNAS is full of secrets, and some of its log messages are quite cryptic, even for the more experienced part of the community. The most recent one I have stumbled upon myself is the
Freed UMA keg message, always followed by something along the lines of
Lost n pages of memory.
Very quick update for you today: I have decided to change the blog’s theme. This one looks a bit more suited to a technical blog, I am keen to give this a try. Let me know what you all think ;)
Comodo offer free email certificates, which is awesome as email is an inherently insecure method of communication. So, if you were toying with the idea of playing around with email encryption and signing, you have no more excuses now.
Getting the free cert to work on macOS, however, might be tricky if you don’t pay attention to a couple of things. Here are the pitfalls I have encountered in the process and how I was able to fix them.
I couldn’t help myself, I needed to write a short rant. I am using a Netgear GS116Ev2 switch as my core switch at the moment, and it works great when it works. When it doesn’t, it’s pretty stupid. Twice in the last week, while performing some changes to the configuration (and not even something big, I am talking about adding a VLAN) the switch became unresponsive and I had to restore to factory settings. Trying to find a support email is close to impossible, so that doesn’t help either. Getting a reply from their Twitter account looks even more difficult, they really seem not to give a fuck.
We all know this: one of the biggest issues with Windows 10 Mobile (previously known as Windows Phone) is the lack of apps. I am convinced it’s one of the main causes of the platform failing massively in the global smartphone market (only 0.7% market share last year according to Gartner).
This kinda makes me sad a little, as I felt the mobile OS market could use a bit of fresh air after all these years of iOS and Android which, even if constantly improved, always felt like more of the same to me. I agree that Windows Phone sucks on so many levels that it would be hard to list all of its problems without forgetting about some others, but at least it was different, you know? And it looked awesome.
Anyway, enough with the melancholic intro. If you want to configure a Private Internet Access VPN on your Windows Mobile or Windows Phone device, you will have to take care of things manually, as PIA does not offer a Windows Mobile app (hence my introduction, just to tie up all loose ends).