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.

Disney climbed the ladder of public domain and then pulled the ladder up behind themselves.

As a LightBurn user and license holder, this is annoying, but I could see this being a good thing in the long run. Right now, there is very little opensource alternative to LightBurn. As of today, there is a much stronger incentive to make it happen. I’m hopeful this spurs on a modern tool in the open source community that works as an alternative. What LightBurn might have done is save them selves some support overhead and created competition. We’ll see how that works out for them.

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.

Effectively, the other option is passwords, and people are really, really, bad at passwords. Password managers help, but then you just need to compromise the password manager. Strong SSO, backed by hardware, at least makes the attack need to be either physical, or running on a hardware approved by the company. When you mix that with strong execution protections, an EDR, and general policy enforcement and compliance checking, you get protection that beats the pants off 30 different passwords to 30 different sites, or more realistically, 3 passwords to 30 different sites.

The modern direction is actually going the other way. Tying identity to hardware, preventing access on unapproved or uncompliant hardware. It has the advantage of allowing biometrics or things like simple pins. In an ideal world, SSO would ensure that every single account, across the many vendors, have these protections, although we are far from a perfect world.

On Steamdeck, I haven’t tried multiple controllers, but with one, it has been rather seamless for both the PS5 and the Stadia controller. They are both Bluetooth, and when I turn them on they just work. That said, the original SteamDeck(which is what I have) doesn’t support CEC or Bluetooth waking, so the Switch wins out on automatically turning on and switching my TV’s input. The OLED SteamDeck is supposed to fix that, but I’m not paying for a replacement until this one dies or a SteamDeck 2 comes along.

Since I was personally called out here, Windows 10 was my last home version of Windows, but it was earlier days of 10. For work, however, I manage about 1700 Windows workstations and servers, so I know all those problems still. To be fair, I’ve been running Linux in some form since before Ubuntu existed. I think it was Debian in 2001 or 2002 that was my first Linux desktop.

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/

For sure, that’s what it is designed for. A proper remote desktop system would need to be able to support low bandwidth links and gracefully drop frames if latency is high or bandwidth is low.

VNC might have seen improvements over the years, but last time tried it, it didn’t handle high resolution/detail well at all. RDP can stream practically any media in close to real time, as to where VNC really broke down if you tried to change too much of the screen at once. Ideally, there’d probably be a new open screen sharing standard that used modern encoding and decoding to allow for high bandwidth connections smoothly. Moonlight gets close, but isn’t really designed as an RDP/VNC replacement.

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.

I don’t want to let nations off the hook for being bastards, but the technical incomlktence of both our core infrastructure and the tools that support them is also astounding.

It is possible, although unlikely, that it is the display server for WebOS, the OS Palm built and LG bought. I seem to recall them having their own display server.

I agree. The hardware was out of date before it was released. The controls were poorly placed to make the joycon gimmick work. It was designed for little kids hands and didn’t offer a solution for adults. The steamdeck really highlighted all these problems by doing it better day one. But for the target demo of the switch, very little of that mattered, and it was a great success. I just hope the Switch 2 learns from these mistakes and doesn’t repeat them.

Both cursed and nice. If you plan is to have a box for emulating old games, it is really a great theme for it.

You are correct, TreestyleTabs was my jam for years, but I have moved over to Sidebery because it performs better and has better support for containers, as well as being considerably more customizable.

Not at all. Just managing clients stuff on portals that don’t allow for delegated access to a single account.