This seems like it's implicitly painting a false dichotomy between an implied autonomous Spez that is causing damage and a subservient Spez that is just a name attached to board action. How about this, if Spez is being asked to do stupid things by the board, he's failing extraordinarily to even cushion them with PR, which is the actual least he can do.
I built this and the other rocm packages from AUR (some removed now) along with pytorch build-flagged for rocm. It did eventually work, but It was a real pain in the ass and cost a whole lot of time. After that though, something broke (who knows) and I ended up rebuilding everything again just to get it back to a working state. I'm currently too afraid to update to these community packages, partially because I don't know if the build flags I used are the duct tape keeping my builds functional (I have an rx590-8gb which is maybe at the edge of supported gpus). Instead, I just added every rocm package to my IgnorePkgs, which isn't a great sign.
I really did loath the removal of SMS. It went like this for me: I would set up non-techie family with signal and that would be SMS and secure messaging for them. Then Signal removed SMS, so I had to explain to them that I had actually set them up with something "unstable" and needed to change their apps around. As a consequence, they're more hesitant to try things I suggest and I can't blame them. As for the actual messaging, inevitably they'll forget to juggle apps and just default to SMS and there's only so much I can go against the stream here.
This is cool, but I think being the default in the mainline app is critical. Also, iirc signal doesn't like modified apps, so this might be on shaky ground.
It goes over an older Ketchup recipe and gives some related history. If you like historical food recipes and/or culinary history, you might want to check the channel out.