made you look
Without NAT/ULA (private ipv6 addresses), your devices are routable by default and must be isolated by explicit policy.
Yes, that’s where the basic firewall configuration comes in.
I’m running native v6 at home, with no private addressing (Since it was never implemented right in OSs unfortunately), each system has it’s own public IP address, and even an entirely unsecured device is protected since there’s still a firewall between my network and the internet.
Especially since you can get M.2 to SATA adapters, so people stuck with SATA only motherboards can still upgrade their storage.
Literally the same deal when companies stopped making IDE drives, people just used SATA to IDE adapters instead.
If you detach the origin from the host it’d work, aka HTTP Alternative Services. Firefox used to (maybe still does? idk) use it to silently switch from using the base hostname to a hidden service when running under Tor, when the site provided the mapping.
Clearnet stuff would work without it, but any I2P/Tor support needs server integration, which would be non-existent at the moment I’d bet.
Git itself (Or any other VCS for that matter) really should treat symlinks as special, similar as to how btrfs stores everything as “reflinks” internally. They be stored as special references to other tracked objects (so it’d be impossible to commit a symlink that pointed at anything other than a checked-in file, and ensure they always match), and git can materialise them as needed.
We’ve got shovels and we are in a big hole … which way are we going to dig?
Yeah, I actually really don’t like JSON. It looks simple but actually isn’t, that’s a bad combo.
CBOR is much nicer, but annoyingly they made their human readable debug version of it similar enough to JSON that people assume it’s just a binary form of JSON, it isn’t.
The entire number and math system is just a straightforward implementation of IEEE 754.
Yeah, but using doubles for everything is its own downsides e.g. it’s why JSON “can’t” store 64bit integers for starters.
They did add the BigInt class recently, which annoyingly you can’t use with JSON because it requires specialized handling (Because of the aforementioned issue with JSON).
(So you “can” store 64bit integers in JSON, the spec just says not to, so people just ignore the spec. You just then run into silent truncation issues with clients that do follow it, like browsers.)
Pretty sure that’s just high-frequency trading.
This behavior is actually in line with what I’d expect, as Unicode support in Windows predates UTF-16, so Windows generally does not handle surrogate pairs and instead operates almost exclusively on WTF-16 code units directly.
So it’s just straight UCS-2, and the software does enforce that, pretty much the opposite of “WTF-16”.
Edit: Pretty sure “modern” (XP+ I think) Windows actually does enforce UTF-16 validity in the system, but there’s always legacy stuff from the NT4/2K era that might turn up.
Webp is a smaller file size than jpeg for the same image quality in almost all circumstances
For lower quality images sure, for high quality ones JPEG will beat it (WebP, being an old video format, only supports a quarter of the colour resolution than JPEG does, etc.) JPEG is actually so good that it still comes out ahead in a bunch of benchmarks, it’s just it’s now starting to show it’s age technology wise (like WebP, it’s limited to 8bpc in most cases)
It also doesn’t hurt that Google ranked sites using WebP/AVIF higher than ones that aren’t (via lighthouse).
Edit: I should clarify, this is the lossy mode. The lossless mode gives better compression than PNG, but is still limited to 8bpc, so can’t store high bit depth, or HDR images, like PNG can.
Edit 2: s/bpp/bpc/
Well, all websites are written in JS (on the frontend)
Not true anymore unfortunately, some sites are using frameworks compiled to WASM instead.
e.g. X is apparently using Yew now.
Edit: Ok the “apparently” is doing heavy lifting, since now I can’t find the original source I read about it. Turns out “X” is a garbage name with no searchability, only an idiot would use it.
Musk has started talking about an ill-defined idea called “universal high wealth.”
iirc Musk’s whole idea was that every person on earth would buy a robot or two of his (or ideally rent them), send them off to work jobs while they stay at home, then split the combined income with Tesla.
Of course, it’s never explained why the companies wouldn’t just buy/rent those robots directly.
Make it out of a rail gun for an even more scifi version.
Ehh, bots have always presented nonsense UAs to servers. And since modern browsers hard-code the OS version in the UA string, pretending to be an old browser on an old OS could be a (probably ineffectual) way to bypass fingerprinting.
Anything that polls location data can record it and sell it, probably more apps that sell it than don’t.
Funny thing is, it was actually the device they connected that was faulty, the build of Windows they were using just didn’t handle that failure condition at the time.
MS at least learnt that lesson (for the most part), actually test things first.
The headline makes this sound a lot worse than the article does.
From the article there’s basically a list of exemptions in the law that describes who doesn’t need to follow it (e.g. an online booking site for doctors visits), everybody else needs to check the rules to see if they do. And if they do, they then need to follow extra child safety rules (e.g. Roblox is opting out under-16s from open DMs by default)
GitHub can quite rightly say they don’t fall under the restrictions of the law, and that could be the end of it. The simple fact that it doesn’t have any form of private messaging feature is probably enough.
they’re just a radical left communist
God I wish that was remotely true
JXL is two separate image formats stuck together. An improved version of JPEG that can also losslessly and reversibly recode most existing JPEG images at a smaller size, and the PNG like format (evolved from FLIF/FUIF) that can do lossless or lossy encoding.
“VarDCT” (The improved JPEG) turns out to be good enough that the “Modular” mode (The FLIF/FUIF like one) isn’t needed much outside of lossless encoding. One neat feature of modular mode though is that it progressively encodes the image in different sizes, that is if you decode the stream as you read in bytes you start with a small version of the image and get progressively larger and larger output sizes until you get the original.
Why is that useful? Well you can encode a single high DPI image (e.g. 2x scale), and then clients on 1x scale monitors can just stop decoding the image at a certain point, and get a half sized image out of it. You don’t need separate per-DPI variants.
Man, it sure would be helpful for my argument if I could.
I went back and checked the ones I was looking at, very helpful fine print stating “not for NVEM ssds”, so they all only work with mSATA M.2 SSDs, hell of a let down.