HNHacker News
TopNewBestAskShowJobs

xyzzy123

7,319 karma · joined September 21, 2012

contact zxcdotmx@gmail.com
submissionscomments
xyzzy123··on Ask HN: We just had an actual UUID v4 collision...
I had dup uuids causing soak test failures in a Linux based distributed system. After long investigation it turned out there was a kernel bug (race condition) that meant two processes on MP system reading from /dev/random at the same could (very rarely, like 1 in a million) get the same bytes when reading the device.

I'd look at rng initialisation first.

xyzzy123··on Mythos is the best cybersecurity news in a decade
I don't see that it makes much difference until we know the distribution of issues that Mythos finds and how reliably it discovers them? Vulns from inspection are discovered via a stochastic process of someone looking at the code, knowing about bug classes and paying sufficient attention to notice them. That's still the case.

IMHO the main thing thats interesting about AI assisted bug hunting is that it changes the balance of power from people who had a lot of free time & attention to the state and big business, who have money and frontier model access. It's a broadly "conservative" development in the sense that it distributes more power to groups who've already got it.

Waiting for the cyber "proxy wars" where state A equips deniable groups x, y with frontier access to undermine state B.

xyzzy123··on Should I run plain Docker Compose in production in 2026?
The concept totally works but I would worry about using a beelink in a business context where I had to support it.

For up to low hundreds of users I think you're better off just with 1 vertically scalable box for all the officey / web server workloads.

You mitigate the hardware failure stuff with a vendor contract where you can get someone on-site and overnight you parts, and by keeping things super boring. Volume replication is not boring, avoid at all costs. NAS or SAN if you have to but all disks in the main box for as long as you can.

For 20 person SME maybe a 2-bay Synology or similar, for a heavier company a low end 2U with hardware support. Proxmox under the OS for reduced worry snapshots, rollback, backup etc. Proxmox is there for operational flexibility, resist the temptation to create a network of VMs, you just need 1 CT or VM with all the workload inside it.

For container workloads on 1 host Portainer works as well as k8s IMHO, it gives you the key property you want - you can IaC everything declaratively with terraform + compose over an API.

Caveat that if CI gets heavy you might need to scale that out but you can keep it stateless.

xyzzy123··on A Pascal's Wager for AI doomers
Personally I don't think coding agents will regress significantly as long as there is competitive pressure and independent benchmarks. Regulation is a risk because coding may be equivalent to general reasoning, and that might be limited for political / "safety" reasons.

Social media "regressed" from the point of view of users because the success metric from the network's point of view was value extraction per eyeball-minute. As long as there continue to be strong financial incentives to have the strongest coding model I think we'll see progress.

xyzzy123··on A Pascal's Wager for AI doomers
I mostly agree with your experience, but;

Every day I deal with bad judgement calls from humans (sometimes my own!), but I don't screenshot them because it's not polite.

I don't think we're at the top of the curve yet? Current AIs have only been able to write code _at all_ for less than 5 years.

Code in particular is a domain that should be reasonably amenable to RL, so I don't think there are any particular reasons why performance should top out at human levels or be limited by training data.

xyzzy123··on NIST gives up enriching most CVEs
ReDoS at CVSS 8+ ... in the configuration file parsing of a bundler.
xyzzy123··on NIST gives up enriching most CVEs
Kernel headers out of date -> kernel vulnerability... in a container.
xyzzy123··on Guy builds AI driven hardware hacker arm from duct tape, old cam and CNC machine
I think the novel idea here is you jam some hardware together (whatever you like) that can do "physical real world" things with a well understood interface and then spin up Claude with access to it.

The way I'm thinking about it is, it's a _workflow_ innovation?

So you ask for data sheets for all the visible chips and get PDFs in an output directory with minimal user interaction except to flip the board, ask for a basic idea of connectivity, get a stitched high res surface image etc.... which of course are all currently possible, but you can do them potentially with very low effort. There doesn't have to be a _software stack_ ahead of time. You ask Claude to do the thing, it will figure out how to do it, write some code, pull in some OSS and make the thing happen. You can take this project's software or leave it.

You might say "tell me where you think the JTAG headers are" and it will come up with a workflow to do its best at that task (most likely with variable results...), but nonetheless this is not a thing you can ask of any commercial product I am aware of today. With probes, stuff can get interesting.

Of course experienced hardware & reverse engineers already can do all this stuff and have a plethora of workflows for it but I still think it's an interesting POC of a generalisable approach. You can take or leave this particular software stack. Also, the hardware barely matters, you can duct tape whatever to whatever.

xyzzy123··on Someone bought 30 WordPress plugins and planted a backdoor in all of them
Is it the industry making this choice or the customer?

You could make a car that's safer than others at 10x the price but what would the demand look like at that price?

Would you pay 2x for your favourite software and forego some of the more complex features to get a version with half the security issues?

xyzzy123··on How many "real" high functioning autists vs. 1%ers with some attitude are there?
I dunno if Steve was autistic or no but there's a subtype of people who develop a "special interest" in reading, influencing and manipulating people and get quite good at it. They study people carefully - each encounter is a new way to find out how people tick, their motivations and levers. They tend to have unusually good memories of specific encounters and conversations. They can quickly and reliably size people up. You need many many encounters to build this kind of intuition up, so there are specific professions they cluster in that give them lots of practice, cops / detectives, sales, even retail - but you need lots of (ideally non-trivial) interactions to supply the intuition pump.
xyzzy123··on I still prefer MCP over skills
I just find that e.g. cli tools scale naturally from tiny use cases (view 1 ticket) to big use cases (view 1000 tickets) and I don't have to have 2 ways of doing things.

Where I DO see MCPs getting actual use is when the auth story for something (looking at you slack, gmail, etc) is so gimped out that basically, regular people can't access data via CLI in any sane or reasonable way. You have to do an oauth dance involving app approvals that are specifically designed to create a walled garden of "blessed" integrations.

The MCP provider then helpfully pays the integration tax for you (how generous!) while ensuring you can't do inconvenient things like say, bulk exporting your own data.

As far as I can tell, that's the _actual_ sweet spot for MCPs. They're sort of a technology of control, providing you limited access to your own data, without letting you do arbitrary compute.

I understand this can be considered a feature if you're on the other side of the walled garden, or you're interested in certain kinds of enterprise control. As a programmer however I prefer working in open ecosystems where code isn't restricted because it's inconvenient to someone's business model.

xyzzy123··on I still prefer MCP over skills
Hmm, but you can't write a standard MCP (e.g. batch_tool_call) that calls other MCPs because the protocol doesn't give you a way to know what other MCPs are loaded in the runtime with you or any means to call them? Or have I got that wrong?

So I guess you had to modify the agent harness to do this? or I guess you could use... mcp-cli ... ??

xyzzy123··on I still prefer MCP over skills
My main complaint with mcp is that it doesn't compose well with other tools or code. Like if I want to pull 1000 jira tickets and do some custom analysis I can do that with cli or api just fine, but not mcp.
xyzzy123··on Maine is about to become the first state to ban major new data centers
The DCs are in VA because its fed / spook central, which induces a large number of well paid policy / compliance / paperwork / tech jobs etc.

NoVa literally one of the richest regions on the planet and it's all sorta tied up in the same thing. Seems unfair to say DCs "bring nothing", the whole ecosystem is a manifestation of concentrated defense spend.

xyzzy123··on US forces locate and evacuate downed airman in Iran
I'm not claiming the US is "good"! I'm saying I would prefer a world where IRGC doesn't have long range nuclear weapons.
xyzzy123··on US forces locate and evacuate downed airman in Iran
Conversely I find it strange how many people seem to want US servicemen to come to harm because it would validate their political views.
xyzzy123··on Scientists are working on "everything vaccines"
We're not really calorie constrained anymore and most humans live in much denser environments than they used to. You would expect rate of exposure, the rate of mutation / change and the rate at which new pathogens appear to be higher than in the past.

Consequently, you wouldn't necessarily expect ancestral "defaults" to be optimal for modern environments.

xyzzy123··on Inside the 'self-driving' lab revolution
I don't really see why most existing equipment would be usable in this way. When you automate a thing you often have to rethink the entire problem. But more generally, automation is for _repeatable_ things and a lot of research is... not that.

The expensive equipment is usually a small (but crucial!) part of research activity, which involves things like talking to a lot of people, getting permission to do weird or new things, going out into the environment and collecting things in very specific ways, storing and transporting them carefully, observing, etc. Building or modifying existing lab instruments, doing various things with animals that are not co-operative ... and CLEANING. Who does all the cleaning?

Definitely use cases when you have a specific protocol you want to scale, but I'm also not sure how safe I would feel around AI with a license to experiment and access to dangerous reagents, high temperatures, etc. Or, god help us, an oligonucleotide synthesizer. Which is definitely going to happen (if it has not already).

xyzzy123··on Why so many control rooms were seafoam green (2025)
Think for a minute about why they worked in shacks.

Also worth noting that Birren was a paid consultant for DuPont - the company that made the paint. From that perspective alone you would kinda expect he is gonna pick colours they already produce reliably at scale.

He also consulted for army, coast guard and navy so whatever colours you pick for hazard marking in an industrial setting have to be _vaguely_ congruent or you're going to cause accidents.

xyzzy123··on Why so many control rooms were seafoam green (2025)
Great discussion on colour theory but I think it skips over the fact that chemistry and economics were also real constraints. Paints that don't fade easily, chemically inert, durable etc and can be produced in enormous volume are not that common. Practical stuff like, how easy does it catch fire, do solvents degrade it. Most important: is it CHEAP?

Also by 1944 there would have been a ready made supply chain due to demand from the navy, which would have picked it for similar reasons and consumed it in enormous volume.

I think, practically, control rooms are chrome oxide green (you get to add as much titanium as you like - thats cheap as dirt too EDIT: it would have been lead actually in the 40s) for much the same reason that barns are red.

xyzzy123··on $500 GPU outperforms Claude Sonnet on coding benchmarks
I'm super confused. The small model "cost field" `rag-api/geometric_lens/cost_field.py` was trained on PASS_TASKS like "Write a function that counts vowels in a string." and FAIL_TASKS like "Write a function that converts a regular expression string to an NFA using Thompson's construction, then converts the NFA to a DFA.".

So it seems like it's a difficulty classifier for task descriptions written in English.

This is then used to score embeddings of Python code, which is a completely different distribution.

Presumably it's going to look at a simple solution, figure out it lands kinda close to simple problems in embedding space and pass it.

But none of this helps you solve harder problems, or distinguish between a simple solution which is wrong, and a more complex solution which is correct.

xyzzy123··on Running Tesla Model 3's computer on my desk using parts from crashed cars
Having shell is extremely handy for further discovery. SO handy that if they were just gonna patch the bug and lock you out, you would simply not disclose it.
xyzzy123··on Some things just take time
Very often kids are un-knowing participants in status signalling by adults.

Parents want to signal "this child is looked after and we have a lot of capacity". Clothes, lunches, a lot of things are quietly like this.

A good hand-made gift demonstrates the status of the giver and provides proof-of-work for their regard of the recipient.

xyzzy123··on Some things just take time
You're missing out on 10 years of real world feedback if you do this.
xyzzy123··on Android developer verification: Balancing openness and choice with safety
This will not be a popular comment, but...

A 24 hour wait like this can sometimes be the result of a security team not knowing what else to do. There are all sorts of weird threat models when you think hard about how devices are used, like partners who have legit access to a phone at a certain point in time.

xyzzy123··on Ask HN: If AI makes your devs super productive, why layoff?
Hi, companies over-hired. A problem at big companies is that staff create the need for more staff. You end up with lots of weird situations like departments creating work for each other that doesn't benefit the customer.

Also more mature businesses are different from startups. A mature business would not know what to do with "100 random little ai-powered mission-aligned startups under your control.", in fact that typically reads to management as chaos.

xyzzy123··on UBI as a productivity dividend
One issue is that there's X% (debatable) of people who can't work for reasons that are complex or hard to explain. For many, even if they are physically able, you kinda don't want them to.

I mean, people who will create negative utility in a workplace or cost more in supervision expense than you get from them as output.

They create hazards for others by being drunk or on drugs on the job, or by harassing or bullying others, injuring themselves or others, causing personality conflicts or dramas due to trauma or unresolved mental health issues etc. I don't mean this as a value judgment, it's just like some people really aren't in a place in life where they can function well in work settings.

I'm not sure how you "guarantee" something that is dependent on complex situational decisions.

xyzzy123··on Iran warns U.S. tech firms could become targets as war expands
Iraq I will grant you, those sanctions were a travesty. Cuba bad too.

In general, I don't find the argument that there were 38 million deaths from sanctions very convicing. That estimate is based on excess deaths and correlation. It is serious work. But it doesn't establish causal structure.

What I mean is, those studies don't have the power to distinguish between (regime -> sanctions -> deaths) vs (regime -> deaths + regime -> sanctions).

I would definitely agree that sanctions cost lives (e.g. unavailability of specialist medicines) but I don't see a specific mechanism whereby they cause "millions" of deaths without a complete failure of local governance.

xyzzy123··on Iran warns U.S. tech firms could become targets as war expands
> Iran has weathered decades of sanctions, which is a fancy way of saying "we're going to starve you and deny your citizens basic medical care". The death toll for this is also likely in the millions.

Hi, I think millions is a drastic overstatement here which undermines the rest of your (often legitimate) claims.

Also Israel seems to have fairly normal relations with many countries in the region, the difference seems to be they are "countries not publicly calling for the destruction of Israel".

xyzzy123··on AI is making junior devs useless
> the art of engineering is reducing the amount of code you've to write

I would argue that it's _scaling_ software development?

Making it so that you can create bigger programs: that accomodate more contributors, more requirements, faster, with more features, while being more correct, etc, without everything collapsing into spaghetti and chaos?

Historically, keeping a close eye on lines of code spent helped a lot along most axes. Finding ways to keep "code spent" down will remain very valuable but I don't think it's the _only_ way to scale?

Along the way we've developed architecture conventions, useful interfaces, test practices, standards, protocols, plugins & extension points, package repositories, etc. There are also social technologies like mailing lists, SIGs, bdfls, modern project & product management, etc etc.

To the extent that simplicity is measurable (less LoC spent, less code coupling, less cyclomatic complexity) it seems like it can be addressed as an optimisation problem and automated.

← PreviousPage 4 of 34Next →