


made you look





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.


That’d at least make sense, this is a (literal) black box. Seriously, my monitor takes long enough to wake that it’s at the boot loader screen by the time it’s ready.
I found a post on Reddit claiming it’s a RAM thing, and I should enable XMP to avoid it. But I’ve already got XMP enabled so I need to poke around it again.
And also disable the 5 second delay in the bootloader, not like I’m ever using that fallback option.


❯ systemd-analyze
Startup finished in 14.565s (firmware) + 5.778s (loader) + 2.920s (kernel) + 3.307s (initrd) + 3.972s (userspace) = 30.544s
graphical.target reached after 3.926s in userspace.
You’re letting me down firmware!
Yeah, the Python equivalent would be something like this.
try:
config = get_config()
catch:
sys.exit(1)
It’s possible to handle these things, but if you explicitly don’t then you’ll discover them at runtime.


I’m still annoyed that “OPAQUE” never seemed to catch on. Uses a username/password combo as normal, but never actually sends the password to the server, only a proof of knowledge. Even if the server is hacked and the DB leaked the attackers can’t actually recover anything resembling a password from it, since the server simply never possesses it.
Passkeys are superior (No password at all), if only the UX around them was better.


It was Apple. Or rather, regulators and partnering companies leaning on Apple to manage the content on their app store better, including the content that you could find via those apps.
Could say something about how the app stores are a monopoly power, and the chilling effect these wide ranging and heavy handed content policies have, and why the open web (and web apps) are a better option. But we also handed the web over to Google anyway, so it’s not that much better.


We’re as close to quantum computers as we are to ChatGPT becoming sentient.


The calculator leaked 32GB of RAM, because the system has 32GB of RAM. Memory leaks are uncontrollable and expand to take the space they’re given, if you had 16MB of RAM in the system then that’s all it’d be able to take before crashing.
Abstractions can be super powerful, but you need an understanding of why you’re using the abstraction vs. what it’s abstracting. It feels like a lot of them are being used simply to check off a list of buzzwords.


And here, they are donating for a project by DHH, because they like the project
Said project is an Arch installer with some extra packages thrown in by default, not exactly groundbreaking stuff.


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.


1596.645 × .001 = 1.596645kg of heroin by weight
That’s 0.1%, not 0.001%
0.001% of 440 gallons is 0.5632 fl oz (or just over 16ml out of 1,666 liters)
You can turn the feature off entirely, or just not talk to people who post them? It’s not something like tiktok where you get pushed a bunch of random videos, it’s stuff that people you know are sending you.


It’s real, but probably not an issue in practise.
If it does actually turn out to pose a problem, then just disable secure boot on those systems, not like it’s really securing anything at that point.


He stores all his footage in full quality instead of just storing his final edited videos in a compressed format.
That’s the right way to do it, you want to avoid generation loss as much as possible.


AMD has its own mix of issues with Vulkan between RADV (mesa), AMDVLK, and AMD’s proprietary driver on a per-game basis at times.
Good news, they’re going away. AMD is focusing entirely on Mesa now.
Most likely an hardware issue, ZFS has seen similar types of corruption with certain drives under normal operation.


It was an issue for a long time that browsers just ignored the caching headers on content delivered over HTTPS, a baked in assumption that they must be private individual content. That’s not the case now, so sites have to specifically mark those pages as uncachable (I think Steam got hit by something like this not that long ago, a proxy was serving up other peoples user pages it had cached).
But for something like Google Fonts, the whole point of it was that a site could embed a large font family, and then every other visited site that also used it would simply share the first cached copy. Saving the bandwidth and amortizing the initial cost over the shared domains. Except now that no longer holds, instead of dividing the resources by the amount of sites using it, it’s multiplying it. So while a CDN might put the contents physical closer to the users, it doesn’t actually save any bandwidth (and depending on how it’s configured, it can actually slow page loads down)