I can't find a reliable source, but from what I can find this cat dipped it's own face in nacho cheese sauce. If that's true, it's not molten cheese, not hot, probably uncomfortable and it's own damn fault.

It has some good parts, such as the ability to use for loops, and the fact you can kind of avoid using it as much thanks to it's webassembly support

Math is more than just numbers and arithmetic. There's even a Wikipedia page dedicated to the Mathematics of Sudoku.

Maybe I'm too European to understand your point, but my phone selling my call and message history would be just as outrageous.

Is the user aware that the data they synchronize to their car, a machine that they own, is sold by the car manufacturer to advertisers? Do they explicitly agree to the selling of their data, when selecting what connectivity they want?

Can you blame the user for making a choice, when they're not told the consequences of that choice?

Sounds a lot like flattening with extra steps to me

It should also be noted that the post will only appear on that kbin instance, and no other instances.

That's not necessarily true. Generally the cartridges shipped with the printers aren't filled entirely, or are otherwise smaller than separately bought ones.

I recently had GCC give me the error "returning to the gate for a mechanical issue", fun stuff as well

I'm not sure I'd classify it as a bug. Instances can temporarily go down at any moment for numerous reasons, to account for this instances will keep retrying to connect with an exponential backoff. At what point should an instance assume that another instance is permanently gone?

Perhaps a good start would be adding a status indicator to every community with something like last sync: 1 minute ago.

You can see that an instance/community is gone by visiting the instance directly. In this case at https://lemmy.fmhy.ml/c/imaginarymechas (which obviously won't work now, as it's gone).

Whenever you submit a post to a community, first your own instance saves the post locally, then sends it to the instance hosting the community, this instance then sends it to any other instance with users subscribed to the community. When the hosting instance is down, then that step of course fails, resulting in the post being only visible to members of your own instance.

Honestly, it's quite likely they really never lost a real life lightcycle race