GreyBeard

I’ve been using and reasonably satisfied with A.R.M. https://github.com/automatic-ripping-machine/automatic-ripping-machine

It uses MakeMKV and Handbrake, but streamlines the whole process.

Meshtastic is a great one. People are making all kinds of software for it. I saw someone developing a BBS for it. For those who want a summary: Meshtastic is a very low bandwidth radio system for creating mesh networks. The speed of data transfer is similar to the modems of the 80s, so you aren’t transferring anything but text. But the range is good and the hardware is cheap, and it is completely stand alone. It can normally pair with something like a phone for ease of access, but has its own dedicated device for a radio.

In this case, "web’ means web browsers, not servers. Godot projects can be exported as static web pages. Sure, the storage is someone else’s linux box, but execution happens on your local device.

1. I love that Linux (and KDE) give us the flexibility to really make ourselves at home.
2. Eww.

I’m guessing you were making a joke, but the real answer is it is a Godot tile map.

Thanks. It was a silly toy, but it scratched an itch, and was good for at least one chuckle.

Here’s a little game I made because I missed it too. https://dbeta.com/games/webdefragger/

Others have given you a good idea, but since you appear to be using Unifi for switch and firewall, o can give you a clear answer: Don’t set vlan on the Synology. Set it as the “Native” VLAN on the switch port going to the Synology.

Synology can be vlan aware, but you don’t need it. Let the switch do the talking.

On the Synology I recommend putting it on DHCP while you test. Once it starts getting an IP in the right subnet, you can then switch it to static. Just make sure your gateway is right, putting it wrong will cause the device to not be able to reach outside its own subnet.

If you have never heard of it before, I recommend checking out the wikipedia page for it, and some of the information available about its creator.

M365 is doing away with all legacy authentication, do not be surprised if IMAP is completely unusable in the next 12 months. If you simply want to keep a copy of everything, a store and forward SMTP proxy would probably be the solution, so all email going to your domain would hit that first, then send off to M365.

The advantage of docker, as I see it for home labs, is keeping things tidy, ensuring compatibility, and easy to manage/backup setup configs, app configs, and app data. It is all very predictable and manageable. I can move my docker compose and data from one host to another in literal seconds. I can, likewise, spin up and down test environments in seconds too. Obviously the whole scaling thing that people love containers for is pointless in a homelab, but many of the things that make it scalable also make it easy to manage.

If you like OpenArena, check out Xonotic. Its a similarly fast paced open source shooter.

I’d say, by my metric of what “Year if the Linux Desktop” is, 2022 was that year. Absolutely everything came together and finally all clicked in. Not saying everything is perfect, but it works, works well, and has support for the majority of games made for Windows.

Nope. It can be cloud if you want it to, but generally, you can host your own controller. I run the controller in a docker container, personally.

I’d suggest looking into the Unifi product line. They have products that meet your needs and then some. I believe the company is based out of the EU so you are likely good in imports.

The problem with WordPress and the like is maintenance. If you don’t keep it up to date, it will get taken by malware. Guaranteed. Any plugins you add increase the risk.

I moved my blog to a markdown based compiled site a long time ago so I didn’t have to worry about that upkeep.

What are you wanting an AI to do? It’s really unclear from your summary.

So I setup every “client” to have the “server” as the introducer and auto-accept shares. Then on the “server”, I add the new client, and give it all the shares. The new device auto accepts, and all the other clients automatically include the new client.

I may be misunderstanding what you want, but the introducer feature seems to solve the problem. You setup your “server” as the introducer for all your other devices, then when you add a device, you just setup your new device with the server, and all other devices get the trust of the new device from the server.

Completely unrelated: A feature that server likely has that you should investigate is called “iDRAC”. There is probably a dedicated NIC on the back for it. It allows you to power on the server, control most “BIOS” features, and see the screen remotely.