I work in the retail tech industry doing DevOps, SRE, cloud, and all that fun stuff. I love technology and am an all around geek.
Toronto, Canada 🇨🇦
All media of my own making is shared under a CC-BY 4.0 license.
All my code is shared under an MIT License.
| Social Links | https://jeffhiggins.me |
| Pronouns | he/him |
| Country | Canada |
I heard that Cloudflare was an at-cost registrar, but I'm pretty sure the domain was cheaper from WHC.
This is comparing a .ca to a .social, so it is not a direct comparison, in hindsight I probably should have transfered a .ca as a test and not my most expensive domain
I transfered a couple of my domains today, and since I couldn't decide which registrar to go to I transfered one to Web Hosting Canada and one to Cloudflare.
Honestly it hasn't helped, they seem equally capable.
The difference really comes down to if I want to be charged in CAD or USD.
Meaning I will probably go with WHC for CAD.
My prod mastodon instance now has network policies applied, everything is locked down with least privilege and all is working.
Makes me happy.
I've been doing a lot of work and learning lately about increasing the security in my home lab, particularly within my Kubernetes cluster.
So I've been leaning all about NetworkPolicies. As of now I've added policies to most of my externally facing apps, and it makes me very happy.
Now in the unlikely event of a pod getting compromised it won't be able to make any lateral movement across my network since the pods now only have access to strictly what they need access to. Before you could scan my entirely lab network, and before I added VLAN isolation a while back my entire network.
Now the only way an attacker could escalate is to compromise the host somehow, which is also unlike since none of my pods run as root.
YAY!
I broke my mastodon instance AGAIN!
It's fixed now, but this time it took me a while to figure out what broke and why, turns out it was a random thing in the minio helm chart that changed the bucket access policy back to private.
RE: https://mastodon.tomodori.net/@vga256/116224095464086764
Fun fact, seamless branching is still very much a thing on bluray and there is a very annoying bug in Google's ExoPlayer where Dolby TrueHD audio cuts in and out on rips from a bd that uses seamless branching... which you would know about if you use an Nvidia Shield.
The most annoying thing about this bug is that the ExoPlayer maintainers say it's not their problem, even though every other player has fixed it.
little known dvd weirdness: back in the early 2000s dvd mastering companies started experimenting with “seamless branching” which would let dvd’s do things like have multiple cuts of the same movie on one disc, without duplicating scenes. when it hit a scene that was only in the “extended” version, it would skip to that track - play it - and then return to the main branch.
problem was that many older dvd players didnt support this. including my 20 year old sony dvp-ns55p. a bunch of my movies like the Alien Quadrilogy would just lock up at random spots. it took me 2 years to figure out that it was exactly at branch points. it’s time to replace this old beast.
today i found a $10 bluray player whilst out thrifting. glad it runs on netscape navigator plugins.
Cam, Ph.D.
CBC Montreal
vga256