Well, that diagram brings up an interesting point. In fediverse if the host dies the federated content can still live on (theoretically, I haven't checked to see if they cull content from dead hosts) but ATProto would dictate that the host is missing and therefore all content associated with the host is now immediately 404.
Static_Rocket
I could appreciate a client certification that is optional, like a list of approved clients on their website or something along those lines.
It should not be enforced by killing the client. I like security, but I enjoy software freedom more.
Llvmpipe is enabled in mesa at compilation time and actually modifies the swrast_*.so the last time I checked. Not runtime configurable. Also, I know at one point it had issues running on 32 bit machines. Not sure if that's still the case.
Just add a new user
Not sure about the Eco tank line, but the smart tank line botched the IPP interface. Ink level reporting is always wrong and printer status is regularly wrong. Exposed settings are limited to push people to the app.
I'm currently use RiMusic, but I wish something would automatically sort through my ListenBrainz recommendations
We'll have a timeline for the plan to make the plan by next quarter
Was actually considering buying premium now that I use YouTube for music more than Spotify, but then the ad stuff happened and now this. Going to avoid it out of principle now.
Sounds like it would specifically be APRS if they were. Neat protocol. Unfortunately no encrypted traffic was allowed last time I looked into it.
Wordpress
Ah, so the kernel actually uses mailing lists. You need to use the get maintainers Perl script to get the people you need to send the email TO and then send it to them with the dri-devel list CC'd.
That shoddy code rots when you update the compiler. (And occasionally good code, depending on what rules the compiler wants to start enforcing)