Welcome! :D It’s like a breath of fresh air, huh?

You might have one installed in UEFI mode and one installed in BIOS mode. That happened to me, and windows never played nice because of it.

Very cool. I’m consistently impressed by the KDE devs.

Absolutely fucking not. I don’t need a sycophantic hallucinatory robot telling me to drink bleach to cure my athlete’s foot.

An i3-N305 in a regular laptop form factor for $1100? I’m good.

Year of the Linux desktop and all that.

I cannot recommend Bazzite enough. It is amazing, and it’s based on Fedora, which is also amazing. I’ve used Arch based distros before, and they can be really cool, but they break once in a while, especially if you haven’t updated them in ages.

I’ve turned on a PC with Fedora after a year and a half, and just updated as usual, and it all worked. Bazzite is even easier, because updating simply means downloading a new base image and updating your Flatpaks. Easy peasy, and very quick.

To get Docker, to run your servers, in Bazzite, you can use ujust:

https://docs.bazzite.gg/Installing_and_Managing_Software/ujust/

Or switch your base image to Bazzite DX:

https://github.com/ublue-os/bazzite-dx

For what I use it for (mostly Beat Saber, but also 3D modeling), it’s not bad. For what I’d like to use it for (AAA VR games), it’s terrible. But, it’s way better than the Quest 1 I had before it. Still, the Frame is going to absolutely destroy it.

Yes, that is technically possible, but you’ll probably have to design it yourself, because I don’t think anyone else has/will. You need to really consider the security implications of this kind of setup. If anyone discovers how to send an email in the way you’re talking about to your box, they would 100% be able to take over your box.

I feel the exact same. I have a Quest 3S, and I can’t wait to dump it immediately as soon as I get a Frame.

I don’t think a year old base is bad. Unless there’s an absolutely devastating CVE in something like the network stack or a particular shared library, any vulnerabilities in it will probably be just privilege escalations that wouldn’t have any effect unless you were allowing people shell access to the container. Obviously, the application itself can have a vulnerability, but that would be the case regardless of base image.

What’s even better is the source code. It’s just true, but false.

It’s hilarious to me that we’ve known for so long that humans are the weakest link in any security chain, and yet we’ve built this weakness right into our machines now.

The AI proofread it and said it was great.

It’s actually impressive that it learned to be the most average programmer, and ended up being way shittier.

A superb image will have a health check endpoint set up in the dockerfile.

A good image will have a health check endpoint on either the service or another port that you can set up manually.

Most images will require you to manually devise some convoluted health check procedure using automated auth tokens.

All of my images fall into that latter category. You’re welcome.

(Ok, ok, I’m sorry. But you did just remind me that I need to code a health check endpoint and put it in the dockerfile.)

Tell me you’re from the USA without telling me you’re from the USA.

Jellyfin and Immich, first and foremost. From there, Nextcloud, Home Assistant, RustDesk, Docmost, and Nephele.

(Full disclosure: Nephele is my own service. I find it quite useful.)

Yeah, I completely agree. It’s straightforward, but it’s got a lot of downsides. Everything always takes eight bytes. Even if you’re just storing 0 or 1.

It makes handling numbers a lot simpler in most cases, though, and simplicity was the goal of JavaScript. I just wish there was a better solution than typed arrays.

Yeah, but only kind of. It depends if you’re using the new syntax. Within new language constructs (like classes and modules), code runs in strict mode without having to use "use strict". It gets rid of some of the annoying quirks.