While I have no idea about legality, it is quite obvious that X/Twitter is not really run as a company run as a public communications platform, but rather as a fever dream of Musk.

Especially the Eli Lily Co. disaster should’ve been a wake up call for X of how much harm the fake checkmarks can bring, yet nothing was done. Most likely because Elon Musk didn’t care. He basically runs it like it’s how little service that he fully owns and controls with full disregard to anything but his own vision.

Therefore including his other businesses makes sense, as the fine that is only based on X’s income would probably be negligible in his opinion, as he runs it on a loss anyways. Only bigger fines would actually have any effect in my opinion.

Ome thing I don’t quite like about kitchenowl is how the grocery list doesn’t really seem to allow entering amounts of stuff, which is especially annoying when you try to shop for ingredients for a recipe. Otherwise it’s a phenomenal app in terms of unifying cookbook recipes as well. The autosummaties also work quite well, it seems.

What I experienced is that Snaps/Flatpaks that contain X11 apps will behave very oddly in a Wayland sessions, at least with NVidia GPUs.

Using distros that still use X11, like Linux Mint, seems to help a lot.

One thing I will commend Snaps/Flatpak for however is bundling dependencies, especially deprecated ones. I spent DAYS trying to install an older version of .NET framework that’s no longer supported to get a game (Vintage Story), but to no avail. With the appropriate Snap/Flatpak it worked first try, well, once I found the distro that doesn’t have the X11 problem that was previously stated.

He was Austrian, BTW.

I do think it’s worth the money however, especially since it allows you to cutomize your search results by white-/blacklisting sites and making certain sites rank higher or lower based on your direct feedback. Plus, I like their approach to openness and considerations on how to improve searching without bogging down the standard search.

I should have elaborated on it a bit more, my bad.

While it’s true that DDoS is more of an active technology rather than a CYA thing. It does however also act as insurance when it comes to the “blame game”: if your site goes down it’s not your fault but the provider’s fault, meaning you might be able to recoup lost profits through a lawsuit.

Of course the only way to avoid this for the provider is to provide better and stronger systems, which normally would grow homogenous through more customers and/or growing fees for all customers, which would pay for better capacity and stronger protection by itself.

However here we have a client that is a high value target that others might want to take down at all costs. Even if they didn’t sue, a strong enough attack might, alongside naturally expected DDoS on other clients, not only take down this customer’s server, but others as well, which really isn’t something you want, for the reasons stated above. And rapidly increasing security could be not worth it, as it could devolve into an arms race by proxy with a high risk of the customer leaving if you raise their fees to much, leaving you with a system which’s maintenance will now dig into your profits due to a lost big income stream, or make other customers leave if you raise the general fee.

I don’t want TP convince anyone they are not like jerks, but rather highlight why a corporation would do something like this to a (most likely) lucrative client.

I think the main problem is that people try to shoehorn OOP mechanics into everything, leading to code that is hard to understand. Not to mention that this is basically encouraged by companies as well, to look “futuristic”. A great example of this approach going horribly wrong is FizzBuzz Enterprise Edition.

OOP can be great to abstract complex concepts into a more human readable format, especially when it comes to states. But overall it should be used rarely, as it creates a giant code overhead, and only as far as actually needed.

And insurances provide monetary compensation until you become a common liability, too high to be covered by any sort of fee. DDOS protection is just the same. It’s only feasible if it happens rarely, like they usually happen. However if it’s a common occurrence it will just eat up the profits made by the fees and then some, which just is stupid to do in any case.

Linus Torvals talk at the Aalto University. Specifically a segment where he talks about how hard it is to work with Nvidia when it comes to the Linux kernel.