There are a bunch of aluminium Lily58 cases out there, they're not cheap tho.
Most of the time keys popping out means your plate is too thick or the switch holes aren't a good fit. You can often improve it (and the sound) with some foam between the plate and the pcb - you can buy laser cut neoprene plate foam for lily58s, or you can always freehand it with a knife and a sheet of 2-3mm foam (it's not that hard and doesn't have to be perfect).
It's pretty common for Alice-style keyboards to have two Bs (the one in the pic in the article does) as on a normally-staggered keyboard the B key is basically equidistant from the home keys so it's common to use either.
But it would be a bit of a problem for keycap sets, some come with extra Bs to accomodate Alice keyboards, but none that I'm aware of have extra G/H/T/Y. That would mean you'd be into buying two sets or using weird keys, so it's probably unlikely to be a popular choice.
That said, there's so many custom keyboards out there, and it's easier than you think to design and build your own - if you feel strongly about it go for it.
I did have that problem a little when learning to type on a split, but I very quickly corrected after hitting the table a few times haha. I actually think it's arguably easier to learn to type on a split as it'll quickly force you to break some bad habits.
Yeah that OSMC box is just running Debian with their stuff coming from its own package repo. You can get a root shell. I realise I could have built something myself (and have in the past) but it's absolutely worth the money to me to get everything in a tiny package and working perfectly from day one.
I wouldn't recommend Kodi for streaming, it kinda works but the experience isn't great. I use it exclusively for playing stuff from my server full of legally acquired public domain videos (ahem).
I do watch YouTube videos on it, but I use TubeArchivist (basically a fancy wrapper for yt-dlp) to pull them onto the server first, and a script to organise them into nicely-named directories.
Yeah I have a couple of recent Samsung OLEDs and they're fine without an internet connection despite reports that they wouldn't be. If I press one of the annoying streaming service buttons on the remote it'll give me a setup popup which needs to be dismissed, otherwise they work fine, albeit without any built in streaming support.
I'd read reports that Q-Symphony (audio from the TV speakers and soundbar simultaneously) wouldn't work, but it does.
I stuck an OSMC (https://osmc.tv/) box to the back of both of them so they can play stuff from my NAS. They're not the cheapest solution and I realise Kodi/XBMC on which they're based isn't everyone's jam (I grew up with XBMC on an Xbox so it is very much mine) - but they play everything, have wifi, HDMI-CEC, integrated RF remote, and work out of the box.
Model numbers if anyone cares: Samsung QE65S95C, Samsung QE77S95F. I believe S95, S90 and S85 (at least up to F) are all very similar so they should all work but ofc ymmv.
My experience of working with Perl as a primary language from late 90s to today: Perl was dead long before Perl 6/Raku was a real thing. By the time that happened it had already lost massive ground to PHP, Python, Java, etc.
PHP had replaced CGI as the easiest way to get code on a webserver, Python and Java were easier to read and understand, easier to structure large systems with, and generally easier to use. Ruby came along and MVC frameworks became the thing for complex web platforms.
Meanwhile Perl was sorta keeping up, the "Modern Perl" movement helped dispel myths about "write only" code, things like Moose, DBIC, Catalyst, Mojolicious, etc meant you could write pretty modern stuff with it. But the community was smaller, fractured by Perl 6 and dominated by some ahem divisive characters which made it intimidating for newcomers, and it just slowly died from there.
By the time Stack Overflow came along it was easy to see that other languages had vibrant communities surrounding them and for me it never really recovered.
This is the approach I take too. If I need it and I can do it then I'm going to. If you don't want me to then block me.
I must say I've had some raised eyebrows over that approach but if the alternative is not getting my shit done then I'm gonna do it unless explicitly forbidden.
SSH tunnelling is an utter necessity in the ridiculous corporate environment I work in. Incredible amounts of bureaucracy and sometimes weeks of waiting to get access to stuff, get ports opened, get some exception in their firewalls and vpn so someone can access a thing they need to do their job.
This guide mentions -D but doesn't really articulate quite how powerful it is if you don't know what it does.
ssh -D 8888 someserver, set your browser's SOCKS proxy to localhost:8888 (firefox still lets you set this without altering system defaults). Now all your browser's traffic is routed via someserver.
I came here to say this. Yes I know https://no-www.org/ is a thing, but browsers have a ctrl+enter shortcut that'll top and tail the domain with https://www. and .com - having that go to an error page is not great particularly given the reason to do it was partially ease of access by customers.
Even running your own local resolver, if you generate enough traffic they'll still block you. I think their definition of open relay is based on traffic volume.
(which is their right, of course - just a warning that might help someone not find this out at 4am like I did)
In our defence, he offered. It had hit hour 6 of both the primary and the backup aircon being down, on a very hot day - everyone was way beyond blame and the NOC staff were basically up for any creative solution they could find.
Similar thing (catastrophic aircon failure due to a flood in a crap colocated DC) happened to us too before we shifted to AWS. Photos from the colo were pretty bizarre - fans balanced on random boxes, makeshift aircon ducting made of cardboard and tape, and some dude flailing an open fire door back and forth all day to get a little bit of fresh air in. Bizarre to see in 2010-ish with multi million dollar customers.
We ended up having to strategically shut servers down as well, but the question of what's critical, where is it in the racks, and what's next to it was incredibly difficult to answer. And kinda mind-bending - we'd been thinking of these things as completely virtualised resources for years, suddenly having to consider their physical characteristics as well was a bit of a shock. Just shutting down everything non-critical wasn't enough - there were still now critical non-redundant servers next to each other overheating.
All we had to go on was an outdated racktables install, a readout of the case temperature for each, and a map of which machine was connected to which switch port which loosely related to position in the rack - none completely accurate. In the end we got the colo guys to send a photo of the rack front and back and (though not everything was well labelled) we were able to make some decisions and get things stable again.
In the end one server that was critical but we couldn't get to run cooler we got lucky with - we were able to pull out the server below and (without shutting it down) have the on site engineer drop it down enough to crack the lid open and get some cool air into it to keep it running (albeit with no redundancy and on the edge of thermal shutdown).
We came really close to a major outage that day that would have cost us dearly. I know it sounds like total shambles (and it kinda was) but I miss those days.