When something that big barely turns a profit, I immediately suspect Hollywood accounting.

But if true, they made a game, covered their costs, left the company with an asset that can keep making sales, and probably developed their in-house talent and tooling along the way. That’s a lot of points in the “win” column.

Wise leaders understand that, in business, victory means getting to try another project with the same team, next year. Failure means disolution of the business. Earn enough years and projects with the same team in a row, and maybe you take one of the big wins one of those years.

Smoking kills people.

A Crazy Taxi 3/4 scale cabinet would be delightful.

You’re right on all points.

I hope we at least get lots of lazy news reporting that refers to the lead actor as playing the part of “Zelda” - ideally live streamed and in-person, in front of the actress who plays “Zelda”.

“Well sorrrrryyyy, Princess.”

I feel seen.

The error message is a timeout. That implies a few things:

• probably nothing wrong at the controller. Timeouts aren’t the controllers fault.
• of course, something must be wrong at the device
• or in between

Since you ruled out obvious stuff like batteries and updates at the device…

I would check in between - check the connectors of any network cables involved. For anything wireless, also check if there’s a device priority table you can prioritize your controller in. I would also try turning off a few devices to see if there’s just too much traffic on the network.

Source: That image contains a stack trace. I am fluent in stack trace WTF. Timeout means the message was sent and there was no timely no response.

The compromise I’ve landed on is that I host my own DNS mx records, and point them to a paid enterprise mail provider.

This gets me the advantages of a paid provider while keeping my actual email address fully mine, to take wherever I want.

I did still have to learn a bunch of DNS rules in order to send all the correct “I’m not an evil spammer” headers and DNS records. But following a one page tutorial worked for me.

Edit: A disadvantage of my approach is that I’m still at the mercy of my email provider if I want to export my message history, and for the privacy of my message history.

I have had some pretty obnoxious recurring reboots on my Pi4 when I don’t add a heat sink and fan.

Sometimes the obvious solution is the way to go.

Your idea sounds good to go ahead and publish your pubkey(s) to fully public URL you control and can memorize.

Then you can stash or memorize the curl command needed to grab it (them) and authorize something to it (them).

A lot of more complicated solutions are just fancy ways to safely move private keys around.

For my private keys, I prefer to generate a new one for each use case, and throw them out when I’m done with them. That way I don’t need a solution to move, share or store them.

Edit: Full disclosure - I do also use Ansible to deploy my public keys.

I was probably running some weird little Python web CGI dice roller or some such. I spent a lot of time teaching myself the HTTP stack the unnecessarily hard way, lol.

Yeah. Probably Apache. Can’t remember what that I was doing, but it almost certainly ran on Apache, and I almost certainly spent 90% of my energy configuring Apache.

Nice.

I’ve had acceptable outcomes on LibreComputer boxes running Armbian. I’ve had terrible luck with anything except the core Armbian image, but for a lot of stuff, Armbian on Libre gets the job done during the chip shortage.