I don’t mind the order of path, arguments and options, but what the hell is the deal with long arguments with a single dash? i.e. -name
instead of —-name
I don’t mind the order of path, arguments and options, but what the hell is the deal with long arguments with a single dash? i.e. -name
instead of —-name
They’re Meross, this one specifically.
https://shop.meross.com/products/meross-matter-plug-with-energy-monitor-mss315-uk
I got a couple of PM plugs with Matter support. I can’t pair them with HomeKit or Home Assistant. I spent about 5h troubleshooting this, inspecting network packets and whatnot and didn’t get any closer to having them working.
I’d rather things just had MQTT support. Happy with Zigbee though, as I can route those to MQTT as well.
You don’t and likely never will get a fully open stack for those GPUs. Even the latest Radeon cards have a lot of closed-source binary blobs for firmware.
Where the line is drawn between the driver and the firmware blobs makes a massive difference though. Look at the recent case of AMD trying (and failing) to license HDMI 2.1+ for their open source drivers.
I don’t think I’ve ever come across a DNS provider that blocks wildcards.
I’ve been using wildcard DNS and certificates to accompany them both at home and professional in large scale services (think hundreds to thousands of applications) for many years without an issue.
The problem described in that forum is real (and in fact is pretty much how the recent attack on Fritz!Box users works) but in practice I’ve never seen it being an issue in a service VM or container. A very easy way to avoid it completely is to just not declare your host domain the same as the one in DNS.
If they’re all resolving to the same IP and using a reverse proxy for name-based routing, there’s no need for multiple A records. A single wildcard should suffice.
I would get a CAD model of the PS5, import it into fusion and design the part around it either by extruding to it or using it as a cut tool.
That phrase used to drive me nuts. It’s so obvious its meaning is conveyed a lot better by flipping it around!
This is terrible advice. The OLED model is better across the board. The risk of burn-in is also wildly overstated.
The only reason to get the original model would be price.
Don’t get me wrong, I have an original and it’s great. I don’t consider the OLED model enough of an upgrade to justify the extra cost but I wouldn’t think twice if I was getting my first.
This is obviously due to personal choices, so take everything I say here as things I care about - not necessarily that I expect everybody else to care about.
It’s not “a different exe”. It’s got Epic’s DRM - meaning it’s tied to the Epic Store, its continuous service, etc. If they fold, I lose access to the games I have on it. In all fairness, I don’t think they will fold any time soon but it still worries me.
With Steam not as much, for a couple reasons: they’re bigger so slightly less likely to fold; they’re not publicly listed so they answer to Gabe Newell and don’t have any legal requirement to increase share value; they promote and put a lot of time, sweat and money towards Linux gaming; and their store is just generally better than Epic’s.
Epic, on the other hand, is actively hostile to Linux gamers: you can’t even play Fortnite on it, they have no native store/launcher; and they don’t have any of the pros of Steam.
Furthermore, I already own more games than I will probably be able to play in my lifetime, so it’s not like I’m “missing an opportunity” by skipping a game that’s on the Epic store. :)
Same here. That’s the reason I haven’t played Alan Wake 2.
Fair enough. I’m using Debian testing with bits of unstable and experimental added in for GPU drivers and Mesa.
Mostly, yes. Some unstable and bits of experimental mixed in.
As another Debian user, I’m excited to get it in maybe a month or 2!
Not sure if this is helpful in any way, but it might give you some clue.
100./8 addresses are reserved for CG-NAT.
This is probably the IPv4 address your modem/router is receiving from the ISP.
Why doesn’t Cyberpunk work?
I’ve played it on SteamOS, Nobara and have been playing at the moment on Debian so it’s definitely not a Linux limitation.
“Quantum security” is a fairly widely accepted term in the industry and it has meaning.
Other terms with the same or similar meaning are quantum cryptography or post-quantum security.
https://www.ncsc.gov.uk/whitepaper/quantum-security-technologies
https://thequantuminsider.com/2023/07/17/quantum-security/
https://www.nomios.com/resources/what-is-quantum-security/
https://www.weforum.org/global_future_councils/gfc-on-cybersecurity/projects/quantum-security/
https://www.hashicorp.com/blog/quantum-security-and-cryptography-in-hashicorp-vault
https://blog.1password.com/passkeys-quantum-computers-encryption/
This is about them adding post-quantum encryption, which means encryption that could survive an attack using quantum computers.
This is computer science and mathematics, not pseudoscientific crap.
Up until a few months ago, Vulkan was very unstable on BG3. It’s been fine for a while though. I haven’t made performance or smoothness comparisons though, I just default to Vulkan and it’s been fine.