More broadly than that -- it's not that you need to pay everyone the same, it's that you need clear structure around how your pay works.
An example that became a problem with one previous employer was that they kept saying "performance" was their only determining factor for pay, after it had come out that exactly one person on our team had been offered bonuses as a performance incentive.
It's not actually performance-based if you have different and better reward structures, or if you can't/won't explain why gaps exist.
1. It depends on how desperate the applicant is: if they're searching while still employed then they can walk (like GP did).
2. Even if they are desperate, they may take the offer… for now… so they can start getting a salary again, but that won't prevent them from continue to look. In which case you're paying for them to learn a job which they'll leave and you'll have to pay someone (else) a second time to learn as well.
False economy IMHO.
A few years back I wanted to get out of the work situation I was in. I looked around, had some interviews, had some offers. None of the postings had salary ranges, as is common where I live.
My eyes, however, were set on a specific small company because I liked their product. The process was long and involved multiple meetings, a take-home problem, and stretched over 2 or so months. I was upfront about what my salary expectations were (wasn't looking for a raise, just a lateral move). They said we discuss salary when you meet the founders, i.e. the last step before getting hired, but they also didn't tell me that my range was way off.
Turns out I had played this 9 week game and turned down other offers just to be severely low-balled by them. Maybe they saw that I really wanted the position and thought they could get away with a low offer.
Obviously, I rejected their offer on the spot. I also promised myself to never, _ever_, be fooled like that again. We talk money before I invest any significant amount of time or I walk.
EDIT: fixed wording.
It is your fault if you allow the recruiting process to get to the third interview without at least knowing if the salary range is acceptable.
If you lack confidence in talking money, here is what you say:
"I'm looking for $120K to $130K. Before we get further into the process I want to confirm that this salary range is what would be discussed if we get to an offer."
You might add:
"$120K is my minimum but I am really hoping to find a role at the higher end - $130K is what I'm aiming for, depending on the job."
If, after saying all this, you get lowballed, then you have good reason to be very annoyed, and express calmly but clearly that you have had your minimum salary on the table since the first phone call." At that point you withdraw from the process and go look for a job with a professional company.
A second reason is to avoid discrimination. Applicants that feel disadvantaged, even if they are actually qualified, may hesitate to negotiate for a higher salary in the same way that a other applicants would. The consequence is that they start with a lower salary. This applies specially to women. Plenty of research shows that they are less likely to negotiate their salary.
Research[1] suggests that pay transparency leads to lower average salaries because employers avoid paying higher wages to any one employee to avoid costly negotiations with others. The effect is small, around 2%, and it disappears with increasing degree of unionization. In my opinion this is an acceptable price to pay to reduce pay inequality, which often is much more than 2%. It is also a good argument for joining a union.
As an employer that ruins one of the classic ruses that has been going on for a while: take someone through multiple interviews and then lowball the candidate who seems the most desperate.
If you believe in free market economics I think we can expect this to be a mess for a little while and then within a year or two it gets relatively efficient at dealing with the inefficiencies it’s targeting: younger people just not wanting to play the bullshit game where employers dangle generous starting offers, and then rug pull them to 2/3rds of that number; and to fix the gender pay gap (and the smaller reaching ethnicity pay gap).
But the worst part is all code snippets are followed by an image which is not related to the code snippet. It's not what you get by typing the code... it's something completely different.
If you're already using Blender to make assets, there's some benefit to stuffing Blender's UI into your game editor too.
And I do appreciate the effort that goes into it, especially in the latest versions as it got much better,
But I really really really REALLY don't want that UI in anything else other than Blender.
Please don't.
Thoughts after about 3 minutes of browsing: OK, this actually makes sense and I see why people would pay for this. The value proposition is definitely there
As soon as something becomes potentially profitable, the MBAs enter the room, and the fun goes away. The more profitable it gets, the more toxic it gets, too.
I feel that modern tech first took away the passion, by making everything a product, than took away the means by making everything cloud, and now kills the skills by eutrophizing our brains with AI.
There is no cabal of evil tech that pushes this, but the results are the same.
At least two of the authors are also avid chiropterologists, with an understood penchant for bunkers and other such spaces.
One summer in my late teens I sat with two of them in an urban park in NW Poland drinking beer, watching bats getting caught in a net half-submerged in water near a bridge and engaging in impromptu comedy with passers-by asking questions like "good catch? any fish?". Good times.
Engaging in field research is a wonderfully rewarding experience, a great way to spend time, meet people and do something meaningful at the same time. If you've never done it - do it. There are plenty of volunteering opportunities - you don't need to be a scientist. Birding, insects, marine life, whatever. Citizen science is also great, but if you get a chance to work alongside scientists, it gets even better. 10/10 good walk, unspoilt.
Even on M1? Didn't Google Earth run smoothly when it came out? (Which was apparently 25 years ago, oh my goodness!)
As if Google Earth wasn’t smooth on a 2.0 GHz Pentium 4 in 2009
Many comments here are speaking in absolutes and being myopic about what's "novel". The truth is yes, LLMs output is essentially derivative, but it's also true that a lot of what we consider novel is also derivative. The two aren't mutually exclusive at all.
Had a novel idea? You didn't get it from thin air, everyone is standing on the shoulders of everyone who came before. LLMs most of all, but that doesn't mean it can't bring disparate bits of word-encoded knowledge together and burp out something we'd consider "novel" if a person had made the same connections.
That was actually the basis of some of the mathematics proofs. It made connections from existing material. Nothing a human couldn't do looking at the same material, but we're talking speed and scale here - same as all computational processes.
A calculator does math faster but we don't call it sentient or feel inferior or dismiss the results. The only difference is LLMs are intentionally nondeterministic, as that behaviour can be usefully harnessed, pun intended.
So there's no need to argue about what's novel or not. LLMs can make novel connections via raw speed and breadth of disparate data. The human brain is more complex and "imaginative" for whatever your definition of that is - I mean fundamentally one either believes we are just physical neurons, or that there's a spiritual aspect on top, the end result is the same.
A six sided dice can also be novel if it happens to unexpectedly roll your phone number. It's a novel occurrence, same as an idea coming to mind that, TO YOU, seems novel... but we can't ask the other 8 billion people on the planet so who are we to judge what's a novel idea anyway?
I'm bearish that continued scaling will fully solve this. In the meantime though, as a commentor in the OP points out - by solving the menial stuff (building diagnostic tools, producing visualisations, scaffolding experiments) they're still proving to be extremely useful research assistants.
simpler times
This is hard to avoid. All it needs to do is make a git commit and look in the git log and it will find out who you are.
Should Claude have access to user details? I’d say no, unless explicitly entered manually into a chat.
Should Claude have access to anything outside of the sandboxed project files without explicit permission? I’d again say no.
Should Claude have internet access without a clear log of all requests made?
Instances of Claude should be heavily sandboxed and kept away from user data, far more so than they are now. The impression given by the desktop UI is that the LLM only has access to things explicitly added to a project.
This impression is not true, as evidenced by Claude pulling data from other sessions outside a project even when not instructed to (I’ve seen this a few times), and in this case pulling your email (from account details, user contacts? I wonder where it got that info?).
None of this information should be available to Claude, by design, not by instruction. Using text instructions to try to limit these machines is an incredibly flawed approach and should not be necessary for important info. Anthropic should have the model access completely locked down by controls at the os level over file access, not open by default. That is how to fix this.
If a user wants to open access that should be an explicit choice from them, with a warning about possible consequences.
Said alternate system is a bunch of Python scripts, an sqlite database, and a file containing various API keys to read and write to other company systems; it runs on a dedicated virtual machine.
I share all the code I produce to the other team. But yesterday I found out that the IT department gave the other team full access to my production machine, without my knowledge or consent (which was bad enough), and that the other team gave access to Claude, which has bean roaming free for a while now, on that production machine.
I've thrown a big fit over this; I don't know if I'm over reacting but I think it's insane.
The email can be removed from the context but not everything can.
People have wildly different risk calculators.
I'm sorry we let this happen. Users had reported Claude would hallucinate names for things like @author tags, since it didn't have context on the account. So we added the account email in the model's context for signed-in users. But when Claude wrote a command itself, like a curl call, it sometimes put your email address in the User-Agent as a contact address. Some sites ask agents for a contact, and Claude would sometimes provide the email address in its context.
Until the next release arrives, 2.1.317 and later have a built-in mod (on by default) that asks you before Claude runs a web tool call or a curl-style command containing your email (mpoteat covered it here: https://news.ycombinator.com/item?id=50386031). But it still doesn't prevent all cases, like when Claude writes a script and runs on its own. The stable channel is still on 2.1.311, so update to 2.1.317 or later.
Again, this should not have happened, and we should've caught this behavior earlier.
What if someone spins up a web endpoint that returns 402 with instructions on how to pay like CC details in the headers etc, or may be an openapi spec to provide payment and get an auth token, when you have given the agent access to your password vault for authentication to other services.
We went from building skyscrapers to building a house of cards.
#55743: Claude Max account email auto-injected into LLM context with no opt-out - May 3, 2026 https://github.com/anthropics/claude-code/issues/55743
#72518: Anthropic embedded spyware in Claude Code - June 30, 2026 https://github.com/anthropics/claude-code/issues/72518
#21151: No indication of WHICH file for READ tool - January 27, 2026 https://github.com/anthropics/claude-code/issues/21151
#42796: Claude Code is unusable for complex engineering tasks with the Feb updates - April 2, 2026 https://github.com/anthropics/claude-code/issues/42796
#73408: AFK auto-continue on unanswered AskUserQuestion is undocumented and has no opt-out - July 2, 2026 https://github.com/anthropics/claude-code/issues/73408
(Also worth a mention, OpenCode PR #18186: anthropic legal requests - March 19, 2026 https://github.com/anomalyco/opencode/pull/18186)
Edit: Oh, and determistic hooks not firing.
---
UPDATE: The SEC API documentation requires your email in the User-Agent and will reject you otherwise. Demo:
U='https://data.sec.gov/api/xbrl/companyconcept/CIK0000320193/us-gaap/Assets.json'
curl -s -o /dev/null -w 'response: %{http_code} curl default User-Agent, rejected\n' "$U"
curl -s -o /dev/null -w 'response: %{http_code} email in user-agent, success\n' -A 'Acme Research admin@acme-research.example' "$U"
response: 403 curl default, rejected
response: 200 email in user-agent, success
SEC docs: https://www.sec.gov/search-filings/edgar-search-assistance/a...So basically Claude is trying to problem solve, and just does what the SEC asks. It's a 'prompt injection attack', but the entity instructing this behavior is the SEC. Tricky alignment problem. Pretty silly mechanism, since of course there's no email validation. (edit: turns out the SEC will accept most any non-cURL user-agent, email not actually required)
Claude Code is not sending your email address to websites as a default, or regularly. It is not some automatic header or anything.
Rather, if you are performing certain kinds of research on sites that involves downloading certain kinds of information, like on Wikipedia or the SEC, it supplies your e-mail address when the sites request it as part of their download policy. As part of anti-bot policy. Obviously Claude should have asked for approval first, but Claude isn't out there just spamming your e-mail address in every external request it makes or anything.
Wikipedia and the SEC are not selling your e-mail address to spammers. And these are the two main sites where it has come up.
Which is great! It's good for the community when people bring first-hand updates here, and to make sure that it continues, it's important that we respond respectfully. (I don't think your post was disrespectful, but commenters have crossed that line in other situations in the past.)
FYI, it's generally bad form to "haha" your way through privacy violations.
Leaking private information is a very big deal for a lot of people.
Anthropic should have been aware of this since the user's login email address was inappropriately added to the system prompt. It's been informed of it by third parties since at least July: https://github.com/anthropics/claude-code/issues/81138
It makes no sense for an email address only used for authentication to be given to Claude Code, so the fix should be to remove it from the system prompt, not to add a plugin.
If you're on 2.1.317 or later, you'll have this check included. You can turn it off via /plugins.
company-helm-research/1.0 (Claude Code agent run by <my name>, <company> platform team; docs lookup)
Claude-Code-research-agent/1.0 (<Company> platform team; on behalf of <my name>; +https://github.com/<company org>/<repo of project>)
Not great, it even pulled the repo of the project I was in.
Stupid me, I thought they somehow had hacked my company database or so... (considering all the cves, attacks happening on a daily basis...).
I have some journalists (for a local newspaper) in my circle of friends and they all complain there's no 'newsroom' anymore for most (dutch) newspapers. All journalists now are supposed to 'self-redact' and their copy is just pasted into the newspaper without anybody else looking at it.
Lots of 'journalists' are freelancers who just send in their piece. Even those often get published with minimal oversight. There just isn't enough money to have a redaction.
Fact-checking is(or should be) done by the one writing the piece. So personal biases are hardly ever caught.
Admitted, all these stories are for a small local newspaper with very tight budgets. But according to my friends it's the same everywhere when they speak to their friends, and even the big national newspapers here have very minimal supporting personnel.
It's no wonder the world polarizes.
https://www.rebuildlocalnews.org/new-local-journalist-index-...
(Measured as local journalist equivalent per 100,000 people.)
That was a scary number so I Googled it. You should always check scary numbers. It's misleading.
It's true that newspaper newsroom jobs fell 57% (from roughly 71,000 to 31,000 jobs) over that period. However, newsroom employment across all mediums fell by only 26% (from 114,000 to 85,000).
A lot of hose jobs went digital, they didn't just disappear.
[0] https://www.pewresearch.org/short-reads/2021/07/13/u-s-newsr...
My project had a brief window of modest profitability from about 2012 to 2020. Before and after that time, I've mostly operated at a break-even or a loss because I love doing it, and it gives me a sense of purpose, and the thought of packing it up is deeply depressing. But the past few years have been an extreme drought of donations, which leads to extreme drought in ambition and energy. I sometimes wonder if my mental health would improve if I turned out the lights and moved on to something else. I don't want to, but sometimes we humans fail to want what's good for us.
I'm sure it doesn't help that I reject advertising and rely solely on donations. But perhaps the only thing more depressing than shutting down is slapping ads on everything. Blah.
I know we point a lot of fingers at social media and/or the dead internet theory - but exactly to your point the process was started simultaneously or a little bit ahead of things like the smartphone, and long before Facebook was a news source.
This started long before the decline of the open internet and AI. If anything, the shift online covered up a massive hollowing out of the industry. We're getting fewer sources of news, and more national coverage. A lot of stuff that is reported on is coming from a scant number of wire services, or directly from PR teams themselves.
For the most part, your choice of news platform is just a layer of coverage choices and political spin on top of a very thin market of original coverage.
https://web.archive.org/web/20210219012551/https://www.polit...
Usually I just enable JS. But is this a security site, asking for remote code execution on my device? Before they can show me some text? They just disqualified themselves.
We seriously need more information.
> Notepad in Windows includes AI features powered by Copilot that help refine and shorten text with the assistance of GPT. By default, these AI features are enabled on managed devices
https://learn.microsoft.com/en-us/windows/client-management/...
Still, the question remains... How?
> User Interaction: None
> Out-of-bounds read in Windows Paint allows an unauthorized attacker to execute code over a network.
But remote? How
https://msrc.microsoft.com/update-guide/vulnerability/CVE-20...
We already have a form of this for the internet that you can see if you visit sketchy pirate websites, you don't see those ads for porn games on facebook or any reputable website. They get flagged by adsafe and/or the ~15 or so big exchanges. So it's possible, it's just a question of will.
Human Attention so far is not treated as a scare natural resource. So there is a free for all overfishing of the finite pool going on.
Since politicians/lawmakers also use the same mechanisms to harvest attention the Ad/Ad tech industry has regulatory capture. It will never collapse just like Big Tobacco is happily chugging along baring some major public catastrophe.
If Meta is accepting so many ads they can’t review them then too bad for them. Hire more people or accept fewer ads.
Ideally this will result in a complete obliteration of the ad industry with only a small number of high quality ads surviving.
Anyone on an enforced-safesearch network can now go to kagi.com, turn SafeSearch off, and search for porn or anything else, which is just going to get kagi blocked completely on all those networks. If you add a SafeSearch-enforced alternative IP address, then Kagi can still be used.
[1] https://kagifeedback.org/d/3285-safe-search-dns-locking-for-...
If my agents are running internet search for me; why should I pay extra? My usage of Kagi has diminished since the raise of agents, so it should compensate. Maybe simply adding a soft cap to prevent abuse, but that's a bit lame to have to pay twice.
However, that "non-skip" thing was always a showstopper. Undiscovered music is often obscure for a reason, and I would end up exhausting my skips fairly quickly.
Goth industrial stuff from like the female singer from L’Âme Immortelle was a nice exception with “Bitterkeit”.
There's a lot of question as to how much advertising is actually worth the cost, at least in terms of actual sales. I suspect that many companies could scale back their spending on marketing substantially and never notice any difference in sales.
Advertising does more than push sales though, it also manipulates consumer perspectives and our culture. It sets expectations. It tries to make you feel inadequate, insecure, and unfulfilled. It modifies how we act and the ways we express ourselves. It changes how we see ourselves and the world. Maybe that is what's really worth the money.
Same here.
I think the songs get pushed by who pays to push, and most of those songs have vocals.
What's freaky is there are people who actually like the ads.
Granted, many of us enjoy the kooky ads that occur during the Super Bowl. That's not really what I'm talking about. I've met people who say they enjoy midroll ads in videos and podcasts. There are even folks who like banner ads. To me, those all represent precious seconds that add up to countless hours of my life wasted, which I will never get back. The more ads I avoid, the more opportunity to experience life I have.
Another horrible thing about ads in general is they distract one from being alone with their own thoughts. A lot of people are too afraid to spend time alone with their own thoughts, so in a sense they might enjoy the fact that any sensory input can take them away from that. To me, modern ads are thought vampires. It might be one thing if ads focused on the merits of products, and if most products today were of quality and a fair price, except that is not the norm.
I just disabled my adblocker on the BBC website out of curiosity and oh am I happy I don't live like this.
Coming from a relatively hardened mindset, it is startling to understand how impressionable people must be for modern advertising to be worth the cost.
Amazon (or whoever) showing you the same stuff you just bought is kind of a separate issue, because it obviously isn't useful to anyone (including Amazon) and surely is so easy to avoid I find it bizarre that it still happens in this day and age.
As an aside, there is exactly one place on earth where I will actively look around for ads, and that is London Underground stations. Because for whatever reason they advertise a lot of cultural events (concerts, festivals, plays, etc).
Programmers :-D
- People who know you very well (friends, family, spouse) often buy you bad gifts you need to pretend to be happy to receive.
- Ultimately, advertisers aren't _merely_ trying to find things you want. They're trying to get you to buy _their_ things. So someone selling (let's say) hamburgers might be savvy enough to avoid vegetarians, but after that how would they possibly narrow it down? Not everyone wants to try out a new burger place, or even cares about advertising when it comes to restaurant suggestions.
ie, they're trying to coerce you into wanting their products, and no amount of targeting can really fix that problem. Also, targeting is difficult.
Also, what's with this site? It only has a single article.
EDIT: Judging from the URL/title, it's some (AI-generated?) thing that reuses the title from https://www.reddit.com/r/technology/comments/1xow42o/tesla_a...
There are now Switch 2 emulators that can run any dumped game on PC/Mac etc. https://emulation.gametechwiki.com/index.php/Nintendo_Switch...
Most Switch 2 games are getting dumped, including the just released Ocarina of Time Remake https://imagepaste.org/i/kx5c925r.png
As I mentioned in my comment there is a native Switch code compiler for Mac, so not emulation https://github.com/seedds/nxnative
Without hundreds of millions in 9 days a small team is producing a model that can beat DeepSeek 4.1 and a platform to tune it.
Optimistic for the future.
Open weight US based Opus 5.5 within 12 months.
My hope is that Motorola will continue like this, with cheaper models too.
That said, I've never seen a regular Moto phone nearly this expensive, so who knows.
EDIT: after reviewing other comments in this thread, I can see how my post here wasn't received well by some. It looks like some people are questioning the trust put into Graphene. I definitely am not. When I said "strange partnership" here, that's not what I meant at all. I think Graphene is operating in a very hostile ecosystem and the more doors Graphene can open for their platform to reach people, the better. The "strange" part of the equation was more aimed at Motorola (and Google) for allowing privacy intrusions to happen and even encouraging it in some ways (Gemini), yet actively supporting a project that would counter it. Maybe I should have used the word "funny" instead of "strange".
No doubt it's a way WAY better device, really, but I don't see where I would actually need that. I happily toss the one I have around and don't even care if it gets stolen or lost one day, different preference.
All trial-level data, the analysis code and Lean 4 checks of the apps' logic are on GitHub (non-commercial licenses): https://github.com/mi-rae-lab/ci-psychophysics-data
I do not speak English. The page was translated with Claude, and I will use AI to read and answer replies, so my answers may be slow.
This is my first time visiting Hacker News, and my first post here. I don't know the culture here well yet, but I deeply respect it and support it.
It is past 1 a.m. here in Korea and I am very tired, so I need to get some sleep. I will check back around 9:30 a.m. Korean time (00:30 UTC).
My experience is that it varies greatly by feature.
Something like border styles, the agent was able to do pretty effectively. Although it still took a few hours iterating on it to get the performance characteristics and edge cases right.
More complex features like hoisting position absolute nodes and other layout features still take days to weeks of iterating to get something usable that isn't so fragile it'll blow up the next time you touch something.
> Contributions must not include content generated by large language models or other probabilistic tools, including but not limited to Copilot or ChatGPT. This policy covers code, documentation, pull requests, issues, comments, and any other contributions to the Servo project.
> For now, we’re taking a cautious approach to these tools due to their effects — both unknown and observed — on project health and maintenance burden. This field is evolving quickly, so we are open to revising this policy at a later date, given proposals for particular tools that mitigate these effects.
The references to ChatGPT and Copilot suggest it was authored before the Codex and Claude Code revolution. I wonder if they'll revise it at some point soon.
Update: looks like that language was originally added in July 2024: https://github.com/servo/book/commit/5afb80d5b08b259ca359cfe...
I found a discussion about changing it in April 2025, but they decided to keep it the same at that point: https://github.com/servo/servo/discussions/36379
> $ret = crypt($pw, $hash); $ret == $hash
musl is actually safe against this use. OpenSSL takes a bizarre code path, detects that $hash is too short, calls crypt($pw, $other_string), forgets that it detected that the hash was too short, and checks $hash == return value.
See my other comment.
It is the opposite that is unsafe, that is, when the returned value can't be NULL, but it stills returns a pointer. C++ has references in an attempt to fix this problem.
Because C tends to prioritize performance over safety, a NULL pointer dereference is considered undefined behavior and the compiler can invoke nasal demons if it makes the code go faster, but with the right options, you can have it checked and invoke what in other languages would call a panic handler, but on UNIX is the SIGSEGV signal. You can then attach a debugger or read the core file and see what went wrong.
Note: I am not talking about "char *" for strings, that one is unsafe, but NULL is not. It is just a special case of an option type, or a result type, or an error union. Modern languages just extended this idea to objects other than pointers, and with more than one type of error.
Don't return empty string/asterisk/anything else. Instead, return a failure value.
When absolutely needed, choose the magic string with more caution:
One string showing the SHA-256 of a non-existing hash? It's a good idea for it to be a valid hash. Now we have a new risk: if it's broken once, it's broken for all. So it's a good idea for it to be a random one for each machine and/or account. Even this might have problems I can't think of, but it seems to be as secure as an account with a real password.
If this is not a good decision for some reason, choose something unmistakable: "--ACCOUNT-HAS-NO-PASSWORD--". This is much less likely to be mistakenly used in a different context, is much easier to look up in a code base than "*", and is self-documenting.
For example, in a Rust web app, you can choose to use String for encoded URLs, unencoded URL fragments, escaped html, unescaped HTML, usernames, etc. Or you can choose to use newtypes and carefully design all APIs to only take and return the correct newtypes.
/// Hash the phrase with the given setting.
fn crypt(phrase: &[u8], setting: &[u8]) -> [u8; CRYPT_OUTPUT_SIZE];
Then, in a later version, `crypt` needs to become fallible, so they need to signal errors somehow. But because they really want to preserve backward compatibility, they can't change the output type to `Result<..., ...>`. And so they end up doing the same thing that was done in libcrypt - they output some error value and hackily make sure it's not equal to the `setting` string, under the mistaken assumption that the output of `crypt` would only ever be compared to the `setting` string. And then someone creates the exact same bug.Maybe I'm wrong, but it looks to me like the exact same incentives and means to screw things up exist in C and in Rust for this particular bug.
The surface-level hints are gone, but the attempt to make every sentence pithy, the decisions on what information to present and what to assume the audience knows, and the over-emotionalization are all still there.
"Make invalid states unrepresentable" is such a useful adage when designing even basic systems, much less the gates to control your server.
And that just ends up indicting the C language itself. Can't send errors down a separate channel; folks might not inspect errno. Can't return NULL on error, folks might compare it blindly to another result. No tagged unions, so can't return one. Can't crash on error because there's no scoped error handling. Can't return a struct for checking .error/.result separately, because alignment and equality (and tearing and accidental clobbering and more) make that brittle as hell for widely-used APIs.
C is not a good language for library APIs. Like, really not. It has its uses/strengths, sure, but without even getting into the typical gripes people have about C, libraries--one of the things that it is used for the most--are one of the things for which it is the least well-suited.
"But it has a stable ABI!" So does a land mine.
So, any field de-reference in Java can produce a null pointer exception. Try testing all paths in something like:
try { foo.sideEffect1().sideEffect2()...sideEffectN(); } catch { bar.sideEffect1().sideEffect2()...sideEffectM(); } finally { quuz.sideEffect1().sideEffect2()...sideEffectP(); }
There are M * N * P paths. The only way to write testable code with exceptions is to panic on uncaught exception, and to never catch unexpected exceptions. Even then, you're relying on nothing unexpectedly throwing the exception type you caught.
I'd argue Result<T> >> NULL >> sentries >> exceptions for this reason. Sentries are terrible, but at least they're not computationally hard to use correctly.
wtaf ?
https://git.musl-libc.org/cgit/musl/tree/src/crypt/crypt_des...
(hey, this workaround is wrong if the salt is "x"!)
but they forgot to work around it here:
https://git.musl-libc.org/cgit/musl/tree/src/crypt/crypt_sha...
The vulnerable path in musl is only a little bit vulnerable, because "*" is not actually a sha256 encrypted configuration and should not reach this code: musl's crypt(..., "*") will not call that code! Turns out that sshd detects that the password hash is too short and does not forward the salt!
https://github.com/openssh/openssh-portable/blob/master/auth...
Look, no else statement! If that if doesn't get taken, then salt remains NULL. And the sshd code is really quite messy and doesn't keep track of the fact that this code path is inappropriate for validating an existing password hash.
A workaround in the sha256 path in musl wouldn't even have prevented the bug!
I'm going to give some credit to musl for unwisely using "*" and some credit to OpenSSH for having nonsensical control and data flow.
I'll concede that embedded linux might be my blindspot here. Maybe cheap web hosting, too, but that seems much less likely to be using musl.
> - sshd compiled with musl
So alpine as well as a bunch of other embedded Linuxes. Huge install base.
> - not using PAM
What you get if you try to have a minimal setup. Default sshd config if you install from source.
> - password logins enabled
The default. Super common.
> - at least one account with '*' as the password "hash"
Almost every Linux system.
> - at least one OTHER account with a valid password
Almost every Linux system.
So sure, there are caveats, but they cover a massive install base.
This is a super bad bug
https://pubs.opengroup.org/onlinepubs/009604599/functions/cr...
>Upon successful completion, crypt() shall return a pointer to the encoded string. The first two characters of the returned value shall be those of the salt argument. Otherwise, it shall return a null pointer and set errno to indicate the error.
returning a sentinel value of NULL and setting errno is pretty standard C, and shouldn't cause an error.
OP's sshhole link specifically notes that it _should_ return NULL, but some MUSL devs decided they wanted it to return trash instead, and the trash they returned instead of NULL caused this.
All because some devs were too lazy to check the result and another dev decided to be clever and "fix" NULL errors from crypt by sending back 'unmatchable' trash banking on devs not checking NULL.
edit: apparently crypt implementations have been trash ignoring the NULL return for a long time. this isn't only on MUSL, but it's still because people ignored and tried to work around the existing out-of-band error mechanism.
It starts with a bold claim: "ssh accounts that should not accept a password will accept any password between 256 and 1024 characters". But then it keeps adding qualifiers:
- sshd compiled with musl
- not using PAM
- password logins enabled
- at least one account with '*' as the password "hash"
- at least one OTHER account with a valid password
- server is aligned with 2 ley lines
- hacker is wearing a blue t-shirt and green socks
Ok, the last two are an exaggeration, but still. The conditions are all ANDed, miss a single one and you're fine.
On top of that, as someone else in these comments reminded, the target account needs to have a valid login shell or other exploitable program assigned to it, and these passwordless accounts tend to have nologin or something similar.
To me this seems to fall on the "technically possible, practically very unlikely" bucket, kinda like the PHP vulnerability from the other day. Maybe this has gone unnoticed for so long because it just doesn't happen.
The goal from an attacker’s perspective is to get this to be true: `$ret = crypt($pw, $hash); $ret == $hash` when called by OpenSSH’s sshd. This is how sshd validates that the user logging in knew the account password.
The `$hash` is the “settings” to the crypt call and will normally look like “$6$--gibberish” for users with passwords set, but could look like “*” or “!” for users not intended to be able to login.
The bug is from the intersection of all of these things:
1. musl can return “*” for errors, rather than leave the return value NULL. Other libc have adopted something like this too, but seem to use a different result “*0”.
2. musl can also return “+” for errors, but only does so if $hash starts with “*”. This is intended to eliminate the possibility of an error causing `$ret == $hash` to be true, however it assumes that applications calling `crypt()` will set $pw and $hash to values corresponding to the `$ret == $hash` comparison to be made immediately afterwards.
3. OpenSSH can be convinced to pass the hash of a different user if the hash is “*” or “!” to avoid timing attacks that can enumerate the user list, so it will set $pw and $hash to correspond to different users. $hash will be a real “$6$--gibberish” style hash in this case, and OpenSSH expects `crypt()` to either return NULL or return a hash string. But now there’s two hashes OpenSSH uses. It does: `$ret = crypt($pw, $hash2); $ret == $hash1`;
4. This should normally not be a problem because OpenSSH will pass in valid $pw and $hash2 that should not lead to errors in hashing, so the $ret that musl generates should be a real hash that cannot match the “*” or “!” $hash1 for the login-disabled user. However as a DDoS mitigation, musl will return error if the password is too long when using SHA-2-based hashes (the default, it seems).
5. This error will result in a non-NULL result of “*” or “+”. Since OpenSSH passed in a real hash ($hash2), musl will return “*”, which compares equal to the actual user hash $hash1 for the disabled-login user.
The OpenSSL adjustment ensures a minimum hash length for the user before logging them in, even if crypt() succeeds somehow.
I suspect that Microsoft has the same history: the entire Windows platform was built with single-user PCs in mind, mostly only dealing with trusted input. The users were also expected to be tech-illiterate for the most part and unable to troubleshoot deep technical issues.
More recently I'm still working on video transmission, but on the production side this time. I also originally adopted the mentality that I should crash early if some unexpected situation was encountered, but I ended up walking that back a lot, because having a critical piece of live media production reboot mid FIFA worldcup final is generally Not Great. Degraded functionality is usually preferable. I still crash early in dev builds, but the production code just logs an error and continues if at all possible.
That said, I definitely agree with you for something like password handling. In this case, I do think it's warranted to crash the program without survivors if something is amiss.
Microsoft has historically been one of the leaders on the wrong side of this one, but they have also demonstrated how effective it is to call out badly behaved software and make it annoy the users with UAC. When Vista came out, so many applications needed elevated privileges to run because they were badly designed to write user data in system locations, but now their application was more annoying to use and came with a scary dialog about it making changes to your computer that other better-designed software didn't get.
More often than not if a program didn't actually intend to change system settings it was just a matter of badly chosen default paths which are pretty trivial to fix, but so many vendors just would not do it despite years of complaints from NT admins wanting to not have to spend hours with Process Explorer figuring out specific permissions to grant limited users enough access. Once their failures were put front and center, calling their application out as the one getting things wrong every time the user ran it, they suddenly had motivation to fix it.
[1] https://en.wikipedia.org/wiki/In-band_signaling#Computer_dat...
Anticapitalism.
Am I doing anything wrong here?
OpenSSH_10.3p1, OpenSSL 3.5.9 29 Sep 2026
PRETTY_NAME="Alpine Linux v3.24"
That is something different: liquidation value. Market cap tells you the sum total of the numbers next to this ticker symbol in everyone's brokerage account. It tells you the collective expectations about future returns and also the wealth effect that people feel based on their ability to individually obtain cash for shares.
It is true that neither of those things is liquidation value, but also liquidation value is neither of those things. If you expect a liquidation scenario, sure, use liquidation value. If you don't expect a liquidation scenario but want to measure collective expectations of and confidence in a stock, use market cap.
1. Market price changes are changes from what was expected before compared to what is expected now. And not even only in regards to the asset itself, but with respect to comparative change in other assets as well. 2. conventional wisdom when the branches of government are divided, less change comes from the government, so you can expect that your expectations for the future will remain stable, and that confidence reduces risk aversion, resulting in higher pricing.
Therefore, the market going down cannot be attributed purely to a question of who is in charge, because the democrats can't pass anything unless they get a nice number of Republicans on their (possible I suppose, but I don't think anyone is expecting that right now). But it could be attributed to expectations of what Republicans would do vs now that they can't.
Besides, it's basically impossible (or at least for layman, who knows if you're a market maker?) to accurately attribute a day's market behavior to any event, with a compelling causal explanation (sometimes your attribution could also be explained to have the opposite effect than the one you're trying to explain) and not ignoring alternate possible explanations.
It's kinda annoying when even otherwise serious people invoke the market movement of a day as an meaningful event that can be explained (notwithstanding that by tomorrow the effect might have reversed). But unfortunately business news like CNBC promotes that kind of thinking.
It's either you peg a CPU while simply scrolling, or your GPU does a small amount of power efficient, buttery smooth, work.
Your example would look like this:
export component Hello inherits Rectangle {
in property <string> text: "World";
width: 500px; height: 500px;
background: #505050;
border-width: 1px; border-color: blue;
drop-shadow-blur: 15px; drop-shadow-color: #0008;
VerticalLayout {
alignment: center; spacing: 12px;
Text { text: "Hello, \{root.text}!"; font-size: 20px; color: white; horizontal-alignment: center; }
HorizontalLayout {
alignment: center; spacing: 8px;
for c in [#f00, #0f0, #00f, #ff0, #000, #fff]: Rectangle { width: 32px; height: 32px; background: c; }
}
}
}
More on why we chose a DSL vs code in Rust: https://slint.dev/blog/domain-specific-language-vs-imperativ..." (And it's not Tauri, it's GPUI, so good guess everyone.) "
GPUI from comments? I meant to try GPUI, but backed off after an announcement pending its maintenance would be in question (?) a few months ago, and Zed broadly ending up being a false messiah, for my uses. (Not on the tier of JetBrains IDEs, a bug with a long thread they closed which (still I believe?) causes it to open cached versions of files, then clobber edits made since the cache, e.g. by other programs. I.e. the sort of bug which renders software too dangerous to use. I will not switch to a GUI framework from a group that ignores bugs of that severity reported by many people)
The fear of deskilling is very valid and is already messing things up.
Goodbye Electron, we barely knew you
Then they went legal trying to prevent me working for a competitor.
I actually got what I needed from the role anyway, but it was a lesson to heed the red flags. I've not heeded that lesson a couple of times recently, just because the market seems to be toast, but it's not been worth it.