A smart powerplug and/or a fingerbot would solve that problem I guess? But at that point it’s probably cheaper to buy a network connected picture frame.

You could use something like the Toshiba flash air?

Or the tld is .mobi

Systemd timer to poll upower when running on battery power, when battery is at 20%, use either system beep or set system volume and play a sound?

I’ve used it, it’s pretty rough and unfinished, the current main branch doesn’t build without help and you’ll need ollama or openai keys.

The results however are impressive, even with a small model like phi3 mini through ollama. They got some good prompts behind it and the results name the sources + have some good followup questions.

I don’t directly have a game recommendation, but make sure to launch the games once before your flight to get the dependencies installed too :) I forgot that last flight and couldn’t play half of the games I planned to because of it…

Missing the joke here? We run a 3090 and a 3900x just fine on ArchLinux.

tbh, a lot of big players (Microsoft, Facebook, Google) host a lot of AI stuff on huggingface and quite likely have to pay for that.

Also they had a few successful funding rounds, last one led by Salesforce.

Also Amazon is invested in them, probably offering a lot to them for free or discounted.

The biggest feature of Wayland for me is mixed refreshrate monitors works OOB. On X this is a pain to get even remotely working and it’s impossible if your monitors aren’t dividable (120/60 works, 144/60 stutters).

This is from my experience something that is starting to be a way more common issue (high refreshrate laptops with 60 external monitors at businesses or high refreshrate monitor for gaming and a smaller secondary monitor for info lookup/discord).

other than that, Xorg does win the “more stable” prize for me, but if I wanted stability, I should’ve become a carpenter.

It’s quite a bad UX, but generally error 2 from make means the called program resulted into an error.

Usually this is accompanied with another error somewhere up the log. Multiple cores can make this a challenge to scan the log for however, so maybe try compiling without the -j argument, that should get the actual error closer to the end.

From my experience, it’s usually an outdated config for the kernel (like using a config for 5.1 while compiling 6.7) or a missing dependency. However the real error will be somewhere among the logs, who knows, maybe it’s a missing processor instruction (it’s really bad UX).

oof

I prefer for it to be just a warning so I can debug without trouble, the build system will just prevent me from completing the pull request with it (and any other warning).