If you are just looking to repurpose an old device for around the house use and it won't ever be leaving your home network, then the simplest method is to set a static IP address on the device and leave the default gateway empty. That will prevent it from reaching anything other than the local subnet.

If you have multiple subnets that the device needs to access you will need a proper firewall. Make sure that the device has a DHCP reservation or a static IP and then block outgoing traffic to the WAN from that IP while still allowing traffic to your local subnets.

If it is a phone who knows what that modem might be doing if there isn't a hardware switch for it. You can't expect much privacy when that modem is active. But like the other poster mentiond a private DNS server that only has records from your local services would at least prevent apps from reaching out as long as they aren't smart enough to fall back to an IP address if DNS fails.

A VPN for your phone with firewall rules on your router that prevent your VPN clients from reaching the WAN would hopefully prevent any sort of fallback like that.

If you are accessing your files through dolphin on your Linux device this change has no effect on you. In that case Synology is just sharing files and it doesn't know or care what kind of files they are.

This change is mostly for people who were using the Synology videos app to stream videos. I assume Plex is much more common on Synology and I don't believe anything changed with Plex's h265 support.

If you were using the built in Synology videos app and have objections to Plex give Jellyfin a try. It should handle h265 and doesn't require a purchase like Plex does to unlock features like mobile apps.

Linux isn't dropping any codecs and should be able to handle almost any media you throw at it. Codec support depends on what app you are using, and most Linux apps use ffmpeg to do that decoding. As far as I know Debian hasn't dropped support for h265, but even if they did you could always compile your own ffmpeg libraries with it re-enabled.

How can I most easily search my NAS for files needing the removed codecs

The mediainfo command is one of the easiest ways to do this on the command line. It can tell you what video/audio codecs are used in a file.

With Linux and Synology DSM both dropping codecs, I am considering just taking the storage hit to convert to h.264 or another format. What would you recommend?

To answer this you need to know the least common denominator of supported codecs on everything you want to play back on. If you are only worried about playing this back on your Linux machine with your 1080s then you fully support h265 already and you should not convert anything. Any conversion between codecs is lossy so it is best to leave them as they are or else you will lose quality.

If you have other hardware that can't support h265, h264 is probably the next best. Almost any hardware in the last 15 years should easily handle h264.

When it comes to thumbnails for a remote filesystem like this are they generated and stored on my PC or will the PC save them to the folder on the NAS where other programs could use them.

Yes they are generated locally, and Dolphin stores them in ~/.cache/thumbnails on your local system.

It also doesn't say that the line on the bottom is straight, so we have no idea if that middle vertex adds up to 180 degrees. I would say it is unsolvable.

We asked our Dell sales guy this question years ago now, when they had been removed one year and quickly added back the next year.

They are there mostly for government builds, and other places with high security requirements. Usually the requirement is that they need to prevent any unauthorized USB devices from being plugged in. With the PS2 m&k ports they can disable the USB ports entirely in the BIOS.

Updates for CrowdStike are pushed out automatically outside of any OS patching.

You can setup n-1/n-2 version policies to keep your production agent versions behind pre-prod, but other posts have mentioned that it got pushed out to all versions at once. Like a signature update vs an agent update that follows the policies.

This is likely something like a FIDO token/passwordless setup of some sort (i.e. Windows Hello).

The thumbprint would just unlock the hardware device, so the thumbprint itself wouldn't need to be transmitted to your credit issuer. This gives you full two factor authentication of your identity because you need the hardware device (something you have) and your biometric (something you are). They also often allow pins (something you know) instead of biometrics as the second factor.

Well worse than that, Oracle closed sourced ZFS, so OpenZFS was forced to become a fork, and they are no longer compatible with each other.

As for GPL the CDDL license that ZFS uses made sure that code contributions attribute copyright to the project owners, which means they can change the license as they please without having to track down contributors.

You would think with their investments in Oracle Linux and btrfs they would welcome that license change, but apparently they need excuses to keep putting money into Solaris, and their Oracle ZFS appliances instead.

August 15th. https://discourse.ubuntu.com/t/noble-numbat-release-schedule/35649

It's presumably to give you legal ground to sue if some corporation scrapes Lemmy content and uses it to train AI, or whatever other commercial purpose.

Hopefully if enough people do it they would consider the dataset too risky to use. They could try and parse out comments that have that license statement but if any get missed somehow they open themselves up to lawsuits.

That would force them to instead pay for content from somewhere that has a EULA forcing the users to hand over copyright regardless of what they put in their posts (i.e. Reddit).

There is a free fan made remake of the shooter. https://totemarts.games/games/renegade-x/

Unfortunately while EA seems fine with them distributing this as long as it is free, they won't allow them to put it on Steam.

I haven't played it in a couple of years so I don't know if there are still active servers but it is a very good remake.

That probably would work well for those closer to the equator.

But for those in the 100 minutes zone of this map that would mean going to work at 6:30am in the summer (assuming we are using civil twilight as "sunrise"), and 9:30AM in the winter which is much more of a swing than daylight savings puts on us, but at least it is a gradual one.

For those above the Arctic Circle, they just work 24/7 for a couple of weeks in the summer but get a similar time off in the winter ;)

Digitizer issues are usually from getting the wrong digitizer. They are programmed differently for the HAC-001(-01) (v2 classic switch) vs the HAC-001 (v1 classic switch).

More specifically the game card reader board that the digitizer plugs into needs to match. So make sure you buy your digitizer to match the game card reader version, or buy a game card reader to go with it (you can get them for ~$14). Unfortunately many digitizer sellers on eBay don't say which model it is designed for.

Alternatively you can mix and match those versions if you have an unpatched/modded switch. Just launch Hekate, go to tools and run the digitizer calibration.

I haven't repaired too many switches but the first time it happened to me I had a spare v2 game card reader and that fixed it immediately. Second time I used the Hekate method and that worked just as well