HNHacker News
TopNewBestAskShowJobs

johncolanduoni

5,429 karma · joined July 14, 2015

my public key: https://keybase.io/johncolanduoni; my proof: https://keybase.io/johncolanduoni/sigs/ZUjmc07ldkvSmh8asZn9tbdF2DBdptDfB3Y-eMh9gXQ
submissionscomments
johncolanduoni··on Google broke my heart
It’s certainly due for an update, but it isn’t doing nothing at all. The friction it creates for unlicensed use at scale is enough to keep all the streaming services etc. afloat, which in turn are still funding the production of content. Maybe the anarchy that would follow its abolition would be superior to the old system creaking along, but that remains to be seen (and would be silly to accept on faith).
johncolanduoni··on Google broke my heart
It’s not good evidence, because people issue false DMCA takedowns all the time. Which I presume they would point out in court.
johncolanduoni··on There were BGP anomalies during the Venezuela blackout
In principle, it means you could run multiple sites from the same IP and someone intercepting traffic to that IP (but not the client’s DNS path) couldn’t tell what site each connection was to. It mostly makes sense for CDNs, where the same IP will be used for many sites.

If you don’t use a CDN at all, the destination IP leaks what site you’re trying to connect to (if the domain is well known). If you use a CDN without ECH, you send an unencrypted domain name in the HTTPS negotiation so it’s visible there. ECH+CDN is an attempt to have the best of both worlds: your traffic to the site will not advertise what site you’re connecting to, but the IP can still be shared between a variety of sites.

It’ll be interesting to see how countries with lighter censorship schemes adapt - China etc. of course will just block the connection.

johncolanduoni··on There were BGP anomalies during the Venezuela blackout
It’s also how browsers detect a website supports HTTP3. Browsers will request it just to check if they should connect to an https:// URL via HTTP3 (though they generally don’t block on it - they fallback to HTTP1/2 if it takes too long).
johncolanduoni··on Murder-suicide case shows OpenAI selectively hides data after users die
I want even the most open AI company to guard my chats jealously. But guarding them from my mother’s estate after I’m already gone is another matter.
johncolanduoni··on Murder-suicide case shows OpenAI selectively hides data after users die
Would anyone have luck suing a person on some random bodybuilding forum who was similarly sycophantic? ChatGPT didn’t invent strangers on the internet flattering your psychosis.
johncolanduoni··on Jensen: 'We've done our country a great disservice' by offshoring
I’m not sure square footage is what matters here, though comparing the overall market for datacenter/manufacturing jobs would be more useful than individual installations anyway. It’s not like the U.S. is hurting for physical space in which to put factories or data centers. Speed of light isn’t that slow — the big New York IXP is actually in New Jersey and it would be fine even if it was further away.
johncolanduoni··on During Helene, I just wanted a plain text website
Yeah, and that’s my point. The problem is not technological, you can make a super readable HTML site by just putting text in <p> tags, and RSS readers for blogs that didn’t rug-pull their content still work fine. People lost interest in giving out something for nothing, so now the web is an ad-infested mess.

If someone makes a new tech that makes that impossible, 10 principled FSF-enjoyers will write content for it and nobody else. Web standard bloat is bad, but it didn’t cause this problem, and you can’t fix it by creating a new spec.

johncolanduoni··on Loss32: Let's Build a Win32/Linux
Look, it’s not that complicated. If you just build your software with gcc or whatever in a docker container with pinned versions, put the binary on your website, and call it a day, 5 minutes later someone is going to complain it doesn’t work on their 3 year old Linux Mint install. The balkanization of Linux is undeniable at this point. If you want to fix this problem without breaking anything else, you have to jump through hoops (and glibc is far from the only culprit).

You can see what the best-in-class hoop jumping looks like in a bunch of open source projects that do binary releases — it’s nontrivial. Or you can see all the machinations that Flatpak goes through to get userspace Mesa drivers etc. working on a different glibc version than the base system. On every other major OS, including other free software ones, this isn’t a problem. Like at all. Windows’ infamous MSVC versioning is even mostly a non-issue at this point, and all you had to do before was bundle the right version in your installer. I’ll take a single compiler flag over the Linux mess every day of the week.

Do you distribute a commercial product to a large Linux userbase, without refusing to support anything that isn’t Ubuntu LTS? I’m kind of doubting that, because me and everyone I know who didn’t go with a pure Electron app (which mostly solves this for you with their own build process complexity) has wasted a bunch of time on this issue. Even statically linking with musl has its futziness, and that’s literally impossible for many apps (e.g. anything that touches a GPU). The Linux ecosystem could make a few pretty minor attitude adjustments and improve things with almost no downside, but it won’t. So the year of the Linux desktop remains illusive.

johncolanduoni··on During Helene, I just wanted a plain text website
RSS is just a list of links to webpages, maybe with summaries. The readers generally fetch those webpages and filter out the text, but every browser has equivalent functionality now. You can do it with literally any HTML page, though some websites try to fight it (since depending on the reader, it neuters ads).
johncolanduoni··on Loss32: Let's Build a Win32/Linux
It has to be as ancient as the oldest glibc you want to support, usually a Red Hat release with very old version and manual security backports. These can have nearly decade-old glibc versions, especially if you care about extended support contracts.

You generally have difficulty actually running contemporary build tools on such a thing, so the workaround is to use —-sysroot against what is basically a chroot of the old distro, as if cross-compiling. But there are still workarounds needed if the version is old enough. Chrome has a shorter support window than some Linux binaries, but you can see the gymnastics they do to create their sysroot in some Python scripts in the chromium repo.

On Windows, you install the latest SDK and pass a target version flag when setting up the compiler environment. That’s it. macOS is similar.

johncolanduoni··on Loss32: Let's Build a Win32/Linux
Making an executable “request” older symbol versions is incredibly painful in practice. Basically every substantial piece of binary software either compiles against an ancient Debian sysroot (that has to have workarounds for the ancient part) or somehow uses a separate glibc copy from the base system (Flatpak, etc.). The first greatly complicates building the software, the second is recreating Windows’ infamous DLL hell.

Both are way more annoying than anything the platforms without symbol versioning suffer from because of its lack. I’ve never encountered anyone who has packaged binaries for both Linux and Windows (or macOS, or the BSDs) that missed anything about Linux userspace ABIs when working with another platform.

johncolanduoni··on Loss32: Let's Build a Win32/Linux
We definitely can, because almost every other POSIX libc doesn’t have symbol versioning (or MSVC-style multi-version support). It’s not like the behavior of “open” changes radically all the time, and you need to know exactly what source symbol it linked against. It’s really just an artifact of decisions from decades ago, and the cure is way worse than the disease.
johncolanduoni··on Loss32: Let's Build a Win32/Linux
Even open-source software has to deal with the moving target that is ABI and API compatibility on Linux. OpenSSL’s API versioning is a nightmare, for example, and it’s the most critical piece of software to dynamically link (and almost everything needs a crypto/SSL library).

Stable ABIs for certain critical pieces of independently-updatable software (libc, OpenSSL, etc.) is not even that big of a lift or a hard tradeoff. I’ve never run into any issues with macOS’s libc because it doesn’t version the symbol for fopen like glibc does. It just requires commitment and forethought.

johncolanduoni··on Python 3.15’s interpreter for Windows x86-64 should hopefully be 15% faster
I don’t know about calling them fatal, but inculcating a culture that believes the flaws are inescapable laws of reality is probably key.
johncolanduoni··on NIST was 5 μs off UTC after last week's power cut
Next to Newark Airport too. He’s lucky they didn’t throw the book at him - they could’ve hit him for reckless endangerment.
johncolanduoni··on NIST was 5 μs off UTC after last week's power cut
Where were we talking about the UK? All anyone said in this message chain was HFT (and NIST).
johncolanduoni··on NIST was 5 μs off UTC after last week's power cut
The victim firm would definitely notice, they’d tell the FCC, and their investigators will show up with a device that literally points them to wherever the jammer is. If you do this for stupid, silly reasons you will get fined[1], if you do it in commission of another crime you will probably get made an example of. It doesn’t matter how evil you are, it’s hilariously easy to get caught doing this.

[1]: https://www.nj.com/news/2013/08/man_fined_32000_for_blocking...

johncolanduoni··on NIST was 5 μs off UTC after last week's power cut
The parent was saying HFT firms would do this to other HFT firms. They would care about doing this kind of thing - it’s not a white collar crime. And foreign adversaries would care about doing this during peacetime, especially for very unclear benefit.
johncolanduoni··on NIST was 5 μs off UTC after last week's power cut
Deploying a GPS jammer in civilized territory is a great way to go to prison.
johncolanduoni··on Garage – An S3 object store so reliable you can run it outside datacenters
I don't have an issue with `unsafe` - Java has the mythical unsafe object, C# has it's own unsafe keyword, Python has ffi, etc. The title of that blog post - that there is no memory safety without thread safety - is not quite true and it acknowledges how Java, C#, and Go have strong memory safety while not forbidding races. Even the "break the language" framing seems like special pleading; I'd argue that Java permitting reading back a sheared long (64-bit) integer due to a data race does not break the language the same way writing to a totally unintended memory area or smashing the stack does, and that this distinction is useful. Java data races that cause actual exploitable vulnerabilities are very, very rare.
johncolanduoni··on Vm.overcommit_memory=2 is the right setting for servers
There are functions on many C allocators that are explicitly for non-trivial allocation scenarios, but what major operating system malloc implementation returns NULL? MSVC’s docs reserve the right to return NULL, but the actual code is not capable of doing so (because it would be a security nightmare).
johncolanduoni··on Garage – An S3 object store so reliable you can run it outside datacenters
I’ve used RocksDB for this kind of thing in the past with good results. It’s very thorough from a data corruption detection/rollback perspective (this is naturally much easier to get right with LSMs than B+ trees). The Rust bindings are fine.

It’s worth noting too that B+ tree databases are not a fantastic match for ZFS - they usually require extra tuning (block sizes, other stuff like how WAL commits work) to get performance comparable to XFS/ext4. LSMs on the other hand naturally fit ZFS’s CoW internals like a glove.

johncolanduoni··on Garage – An S3 object store so reliable you can run it outside datacenters
Somewhat unrelated, but I just looked at the RustFS docs intro[1] after seeing it here. It has this statement:

> RustFS is a high-performance, distributed object storage software developed using Rust, the world's most popular memory-safe language.

I’m actually something of a Rust booster, and have used it professionally more than once (including working on a primarily Rust codebase for a while). But it’s hard to take a project’s docs seriously when it describes Rust as “the world’s most popular memory-safe language”. Java, JavaScript, Python, even C# - these all blow it out of the water in popularity and are unambiguously memory safe. I’ve had a lot more segfaults in Rust dependencies than I have in Java dependencies (though both are minuscule in comparison to e.g. C++ dependencies).

[1]: https://docs.rustfs.com/installation/

johncolanduoni··on Vm.overcommit_memory=2 is the right setting for servers
No non-embedded libc will actually return NULL. Very, very little practical C code actually relies only on specified behavior of the spec and will work with literally any compliant C compiler on any architecture, so I don’t find this particularly concerning.

Usefully handling allocation errors is very hard to do well, since it infects literally every error handling path in your codebase. Any error handling that calls a function that might return an indirect allocation error needs to not allocate itself. Even if you have a codepath that speculatively allocates and can fallback, the process is likely so close to ruin that some other function that allocates will fail soon.

It’s almost universally more effective (not to mention easier) to keep track of your large/variable allocations proactively, and then maintain a buffer for little “normal” allocations that should have an approximate constant bound.

johncolanduoni··on The state of the kernel Rust experiment
Your priorities do not match that of most kernel developers or most operators of network-connected Linux systems (even if we ignore Android). So I don’t think your problem is with Rust at all, you’ll need to fork Linux if you want the project to stop putting huge amounts of effort into memory safety (as it has for decades).
johncolanduoni··on The state of the kernel Rust experiment
What number of CVEs is Rust kernel code allowed to have before we have good evidence it’s a categorical failure? Do you turn off KASLR for your Linux machines because there exist CVEs it doesn’t protect against?
johncolanduoni··on The state of the kernel Rust experiment
Please explain how it adds to the discussion about different ways to broaden supported Rust target architectures. Because both have the word Rust in them?
johncolanduoni··on The state of the kernel Rust experiment
That was definitely me, you got me. How did you know from my comment about a potential Alpha LLVM backend?
johncolanduoni··on Getting bitten by Intel's poor naming schemes
Even more fun is that some of those (IOMMU and ACPI version) depend on motherboard/firmware support. Inevitably there is some bargain-bin board for each processor generation that doesn’t support anything that isn’t literally required for the CPU/chipset to POST. For userspace CPU features the new x86_64-v3/v4 profiles that Clang/LLVM support are good Schelling points, but they don’t cover e.g. page table features.

Windows has specific platform requirements they spell out for each version - those are generally your best bet on x86. ARM devs have it way worse so I guess we shouldn’t complain.

← PreviousPage 4 of 34Next →