I uploaded a small package of my preferred monospaced console fonts here.
The servers that host this website have been successfully migrated from Debian 9 to a fresh installation of Debian 10. As part of this migration quay.net now resolves to 220.127.116.11 and is no longer available on the old server, hal9000.
This upgrade means that the website now supports TLSv1.3 and a number of other improvements. If you come across any missing content or bugs, please let me know.
I’m not much for social media, but on the off chance you want to connect with me, I do have a fairly inactive Mastodon account.
I may not reply immediately, but I do check in from time to time.
I’ve just written a quick and dirty guide on how to use Certbot on Debian 9 with Route 53. This is useful if you are trying to manage wildcard certificates and don’t want to, or can’t, screw around with managing the current state of the Route 53 plugin on Debian 9.
Without further ado: quay:wiki – Let’s Encrypt Usage Notes
If you’re loooking for a bit of light reading before bed, this might be just the answer: An Advanced Introduction to GnuPG.
On a mostly related note, I’m going to move all of my (admittedly trivial) secure e-mail to my ProtonMail account. If you have any reason to contact me securely, I advise you e-mail with GPG at gmobrien at protonmail dot com as of December 2018.
No big editorial, just a note for folks who have reason to use any of my GitHub projects and read the blog…
From here on, I’ll be maintaining any public software over here: https://gitlab.com/gmobrien
After a few shenanigans with Rogers and Teksavvy, I managed to switch over to my cable Internet service yesterday. Thankfully the only issues were administrative. After 24 hours of service, I’m cautiously optimistic that my local segment doesn’t seem to be especially congested.
I’ve not quite cracked 100Mbps download speed in any of my tests, but I have been able to hit 98Mbps pretty consistently and I’m always hovering around 10Mbps up. My ping times seem to stay to between 10-15ms to servers hosted in the downtown Toronto core. This is up about 5-7ms from my DSL service, but I’m fortunate enough to have always had good ping times in artificial tests simply because of location and this doesn’t seem to be a showstopper. I guess I’ll know more when I get a chance to sit down and play a few online games.
Last night during the supposed peak usage period, I was only seeing a drop in download bandwidth of 3-4Mbps at worst and barely any difference in upload bandwidth at all. My latency did increase a little bit as well but never more than 5ms and most of the time it was closer to 1ms.
If this holds, then four times the bandwidth is a fair trade for not having the lowest ping on the server! I thought I’d share this in case anybody else is considering Teksavvy cable as I found it incredibly hard to find anything other than horror stories which were clearly a result of unique circumstances when I was researching the switch.
Here’s a link to my Speedtest results if you are interested in a bit more detail.
So for the first time at home I have what until relatively recently would have been viewed as LAN speed for my Internet service, and with an unlimited, and reasonably managed bandwidth policy. I’m not an abusively high user, I’ve almost always stuck inside my current cap on my DSL service, but I do appreciate that a good service provider should manage their networks during extreme congestion.
My experience with Teksavvy has been positive enough over the years, I’ve been a customer since 2006, and I’ve only ever had one provider that was better and this was back in the .com bubble days when Ottawa was crawling with technically savvy and responsive providers! So I’m giving them the benefit of the doubt that they will not do anything naughty with their traffic shaping policies. Continue reading