MurphyA/hacker-news huggingface dataset:
by bredren | 2025-07-23 03:47:19+00:00
>you might sometimes prefer a smaller one because being able to do something in real-time, or being able to run on a mobile device, is more important than marginal accuracy gains for some applications.

This reminds me of ~”the best camera is the one you have with you” idea.

Though, large models are an http request away, there are plenty of reasons to want to run one locally. Not the least of which is getting useful results in the absence of internet.
by cortesoft | 2025-07-23 03:47:27+00:00
> If it's not worth fixing and not worth tracking, but you want to remember it, that's a fine thing for a regular code comment.

In my mind, every todo in code is of this type - worth fixing (someday, maybe) but not worth tracking. If it needs to be tracked, put the details in the ticket and just link to the code, don't put a commment in there.

To me, the point of the todo comment is to see it if I am working/touching/utilizing that bit of code. That is the time it should be worked on, not when someone finally gets to a ticket in the ticket tracker.

It's all about the method of action - if the task is something that should be prioritized against other work, put it in a ticket. If it is a task that should only ever be done if I touch this bit of code, then put it in a TODO comment.
by qbane | 2025-07-23 03:49:27+00:00
This has a long history dating back to the Flash era.

https://owasp.org/www-community/attacks/Clickjacking

> One of the most notorious examples of Clickjacking was an attack against the Adobe Flash plugin settings page. By loading this page into an invisible iframe, an attacker could trick a user into altering the security settings of Flash, giving permission for any Flash animation to utilize the computer’s microphone and camera.
by elevation | 2025-07-23 03:50:14+00:00
Supply side economics, which aims to stimulate growth by reducing costs for industry, is jeered today as “trickle down economics”; it’s considered regressive because the benefits are concentrated for suppliers while the benefits to consumers never materialise. This policy has “failed every time it’s tried!”

Tariffs are the antithesis of supply side strategy. Yet tariffs, which increase costs for suppliers like any other tax, are derided by the same people as “regressive” as if they will always be born 100% by the consumer. Supposedly, tariffs cannot possibly benefit the working class on any time scale.

At least one of these positions must be at least partly wrong. Which is it?
by user_7832 | 2025-07-23 03:51:14+00:00
> If you use an Android phone and haven’t disabled system animations, then yes, you’re likely affected. iPhone users are not affected.

Okay... that was much worse than I expected. Looks like you can get the victim to click anywhere, which looks bad. I thought Android had protections against this?

> It is based on transition animations instead of overlays, so it doesn’t need special permissions and isn’t blocked by Android’s overlay protections.

Oh well. Not sure how that slipped past.
by lukewrites | 2025-07-23 03:51:21+00:00
Reading reviews of this type of keyboard is really interesting to me because their use is such a subjective experience. I have found that the glove80 has far and away the most comfortable thumb cluster for my hands as well as the most comfortable positioning for my pinkies.

I couldn’t make the corne variants work because tucking my thumbs hurt. The ergodox is too big. Even a keyboard like the ZSA Voyager just doesn’t fit me right. However, the glove80, running a 40 key layout that I’ve come up with after doing a fair amount of heat mapping my own keystrokes, gets rid of all my hand and wrist discomfort. My only complaint is what a hassle it is to haul around.

The only “wisdom” (hard earned) I would pass along is:

- Make a heat map of your keyboard over a few days to see what keys you need.

- tweak your layout to make it easy and comfortable to get to the keys and key combos you use.

- remember you do NOT have to use every key!
by temp0826 | 2025-07-23 03:53:09+00:00
> Of course this is all moot because vaping will be revealed to be the current #1 cause of lung cancer in the coming decades, by a long shot. No citation necessary.

That isn't obvious or apparent to me at all so I do think a citation would be good to see. Nicotine is definitely a culprit in a lot of cardio-related issues for sure. I think some flavoring agents are the more questionable thing and would be curious to hear about those specifically in relation to lung cancers.
by dimatura | 2025-07-23 03:53:18+00:00
You can roughly divide barcode reading into a "frontend" and a "backend". The backend is the most well understood (but not necessarily trivial) part: you take a binary image, with each pixel corresponding to one little square in the QR code, and decode its payload. It doesn't need computer vision. The "frontend" is the part that takes the raw image containing the barcode and tries to find the barcode, and convert the barcode it finds into a nice, clean binary image for the backend. This is a computer vision problem and you can arbitrarily fancy, including up to using the latest trends in ML vision models. However, this isn't necessarily needed in most cases; after all, barcodes are designed to be easy to read for machines. With a large, sufficiently well focused and well exposed image of a barcode you can get away with simple classical computer vision algorithms like histogram-based binarization and some heuristics to identify the spatial extent of the barcode (for example, most barcode symbologies mandate "quiet space" (blank space) to be around the barcode, and have start and stop markers; QR codes have those prominent concentric squares on the corners).

As for implementation, Zxing-cpp [1] is still maintained, and pretty good as far as open source options go. At this point I'm not sure how related it is to the original zxing, as it has gone substantial development. It has python bindings which may be easier to use.

On mobile, Google MLkit and Apple vision also have barcode reading APIs, not open source but otherwise "free" as in beer.

[1] https://github.com/zxing-cpp/zxing-cpp
by ninetyninenine | 2025-07-23 03:53:26+00:00
>We understand LLMs pretty well. That we can't debug them and inspect every step of every factor on every prediction doesn't mean we don't understand how they work.

This is the definition of lack of understanding. If you can’t debug or know what happens on every step in means you don’t understand the steps. Lack of knowledge about something = lack of understanding.

The amount of logic twisting going on here is insane.
by bredren | 2025-07-23 03:54:11+00:00
There are big gains to be had by having one top tier model review the work of another.

For example, you can drive one model to a very good point through several turns, and then have the second “red team” the result of the first.

Then return that to the first model with all of its built up context.

This is particularly useful in big plans doing work on complex systems.

Even with a detailed plan, it is not unusual for Claude code to get “stuck” which can look like trying the same thing repeatedly.

You can just stop that, ask CC to summarize the current problem and attempted solutions into a “detailed technical briefing.”

Have CC then list all related files to the problem including tests, then provide the briefing and all of the files to the second LLM.

This is particularly good for large contexts that might take multiple turns to get into Gemini.

You can have the consulted model wait to provide any feedback until you’ve said your done adding context.

And then boom, you get a detailed solution without even having to directly focus on whatever minor step CC is stuck on. You stay high level.

In general, CC is immediately cured and will finish its task. This is a great time to flip it into planning mode and get plan alignment.

Get Claude to output an update on its detailed plan including what has already been accomplished then again—-ship it to the consulting model.

If you did a detailed system specification in advance, (which CC hopefully was originally also working from) You can then ask the consulting model to review the work done and planned next steps.

Inevitably the consulting model will have suggestions to improve CC’s work so far and plans. Send it on back and you’re getting outstanding results.
by anonymars | 2025-07-23 03:55:42+00:00
This assertion is extremely privileged and I heartily disagree with it

Even if we're just going to say "diet and exercise" it is a privilege to not live in a food desert and have sidewalks. If we are to mention the free yearly physical it's a privilege to have a doctor nearby and be able to get the time off work

So no, I don't think I am the one missing the point
by usr1106 | 2025-07-23 03:57:53+00:00
Why? I immediately thought: Which country and starting to read the article gives the answer.

Americans seem to assume that there is only one country and abroad is an exception needing extra disclaimers.

Edit: The article also says the study is by a right of center thinktank. Would that also be needed to be mentioned in the title? Of course it would the context. But the rule is not to editorilize, we can read and think ourselves.
by fragmede | 2025-07-23 03:58:28+00:00
Birds didn't read Ornithology in order to fly, sure. But you can be damn sure the engineers at Boeing cracked a textbook on the way to making the 747.

Real-world experience teaches you how you survived. Education teaches you how others failed. You need both to avoid old mistakes and make new ones.

It’s not about credential hustling, it’s about having more tools in the toolbox.
by dietr1ch | 2025-07-23 03:59:17+00:00
No, I knew there's some trickery to avoid part of the noise in git, but it's not enough as I won't be looking at that log or blame everytime I read a file. Using a TODO comment still seems better to me.

A TODO surfaces details where it wouldn't even occur to me that there's something interesting hidden in the log. Trying to find them feels like smashing the action button everywhere to get a random secret in a game, like secret doors in rtcw or finding stuff with the shovel in zelda.
by dimatura | 2025-07-23 03:59:53+00:00
You can examine the code of zxing-cpp (which is fairly nice IMO) for a simple, "classical computer vision" approach to this. It's not the most robust implementation but it is pretty functional.

But in general, you can divide the problem more or less like this (not necessarily in this order) 1. find the rough spatial region of the barcode. Crop that out and only focus on this 2. Correct ("rectify") for any rotation or perspective skew of the barcode, turn it into a frontoparallel version of the barcode 3. Binarize the image from RGB or grayscale into pure black and white 4. Normalize the size so that each pixel is the smallest spatial unit of the barcode.
by pbrum | 2025-07-23 04:00:01+00:00
This stuff is hard. Today was the first time my little startup started sending out little videos of demo features to the group of about 20+ people (all friends/family/close colleagues) I'd interviewed in round 1 of customer work. How did it go? Ok, but not great. The disappointment in there is not from any negative reactions, but rather to the large amount of non-reactions (simple things like "oh cool" and nothing else from someone who knows full well how important this is to me).

But that's ok! I know maybe they'll have more time later. If not, I will nudge them. And I have other people to ping and later will move on to cold pitching anyway. And I've read in countless founder books, testimonials, etc about how hard and laborious this is. Keep a firm mindset, be systematic about going through all the steps, never skip a day of work, meet your own deadlines, have a bulletproof work ethic. Rome wasn't built in a day!
by ajkjk | 2025-07-23 04:00:51+00:00
Well I don't know how dartium did it really, but it seems to me like "add a new website implementation language to Chromium" would be a tutorial on Chrome/Chromium's home page.

Such that one could throw together, I dunno, news.ycombinator.com/index.z and see if they can do a better job than HTML/CSS.

As far as the actual solution to try for, table stakes is a native implementation of something that looks like React (but presumably reimagined from scratch).
by polski-g | 2025-07-23 04:01:21+00:00
We use Plane. It's acceptable. Not great, not terrible. Jira wanting 26k per year, per customer we have was unacceptable.

I wish their docker deployment was normal (only docker-compose.yml), not a shell script that launches docker.

It needs ldap auth and better search capability (fts, boolean, filtering).

UI is clunky; everything is editable all the time, so you might end up accidently editing the ticket contents.
by mk_stjames | 2025-07-23 04:03:23+00:00
In addition to zip bombing AIs with file parsers, I've wondered about 'context bombs' in the sense of trigger phrases that trip up LLMs into getting stuck into repeating phrases or reasoning evaluations without ever hitting an end of sequence (EOS) token, thus running a system up against API call limits / burning credits / effectively ddosing services etc.

Due to the inherent fuzziness/diversity in all models right now I don't think there is a universal approach to this idea but it is something people deploying these systems may want to try and detect.
by Terretta | 2025-07-23 04:04:10+00:00
I still prefer Andale Mono.

Here's an interesting take on the two: https://neil.computer/notes/berkeley-mono-december-update/

See if you can figure why I linked this one.

---

More about Andalé: https://en.wikipedia.org/wiki/Andalé_Mono

This conversation may still be going on 20 years from now: https://nedbatchelder.com/blog/200602/monospace_fonts_compar...

Nice we have more choice since this capture in 2006: https://www.donationcoder.com/forum/?topic=2499.0
by jschveibinz | 2025-07-23 04:04:18+00:00
The constitution guarantees a counterbalance.

Roughly 50% of the time the control of Congress is with the opposing party to the President--and the rest of the time Congress is with the President. So it's not unusual at all for Congress to pass a majority of legislation that is proposed by the executive branch.

But your last paragraph is troubling: democracy is not at risk in either case. Democracy is what puts the leaders in place. Voting still matters.

The only current problem with US democracy that I see is the lack of voter engagement. We only get 60+% of voters to turn out for elections.
by hakfoo | 2025-07-23 04:04:31+00:00
I'm trying to figure out ways to placate the boss by fitting AI into the edges of my workflow.

"Look at these commits and do a review" to find stupid stuff like forgotten exception throws or nulls. Or "Critique this documentation for a different audience"

I don't want to get into the "let the machine write the code" phase because that's the task I enjoy most, and it swaps my efforts into review, which I'm bluntly less confident about (having to follow and second-guess an architecture without being "there" when it was evolved increases the chances I'll miss stuff)

The stuff that AI demos well at-- "refactor 5,000 lines of code", "build a new client from ground level" are simply not what my team works on; we end up doing things where building a prompt to actually make the change we want-- and only the change we want-- takes longer than writing the code itself. 80% of the time is the debugging and planning.
by ninetyninenine | 2025-07-23 04:04:34+00:00
So the horse reading peoples minds by observing human body language is a high probability outcome?

When you see a fucking horse doing mathematics, it's not unreasonable to think maybe it was doing mathematics.

Like where is your quantitative data and evidence? What are you using to say it's "low probability"? You have no idea how consciousness in humans work. You have no idea how LLMs work. Yet you can just declare a low probability fact out of thin air?
by anonzzzies | 2025-07-23 04:05:59+00:00
Yes, when Claude code says that, it usually means its going to attempt some hacky workaround that I do not want. Most commonly, in our case, if a client used one of those horrible orms like prisma or drizzle, it (claude) can never run the migrations and then wants to try to just manually go run the sql on the db, with 'interesting' outcomes.
by alephnerd | 2025-07-23 04:06:20+00:00
> Given that, I question how many of these are actually caused by the tariffs.

For automotive and electronics, a lot of it was a result of CHIPS and IRA related subsidizes

That said, the tariffs do help incentivize domestic production instead of taking advantage of subsidizes from CHIPS+IRA and then comingling with SKUs from abroad.

Think of the Biden-era CHIPS+IRA as the carrot, and the Trump associated tariffs and export controls as the stick.
by Neuronree | 2025-07-23 04:07:26+00:00
I am working for a company that had a very old data base and still does a lot with paper. I started working on digitizing and organizing everything and I found it would be easiest to scan in large batches but naming would take forever. I decided to build a pretty basic python script using OCR to pull the data from the PDFs and use it for renaming. Once it worked well, I fell down the rabbit hole of making it a web app and setting it up to be easy to setup (even for the very non technical).
by ocdtrekkie | 2025-07-23 04:08:26+00:00
I was drastically oversimplifying by calling certificates a password. But the point actually does definitely stand: In the long-lived certificate days, you'd keep your CAs and such offline, and generally speaking, highly secured. Now you have to give your automations everywhere everything they need to constantly generate keys that claim to be your site. People are pushed to make drastically less secure choices about how they generate certificates because it needs to happen so often. A lot like adding a 1 on your last password. ;)

Also, short lifetime certificates help deprogram concern about certificate warnings (most nontechnical users know to ignore them, as a network admin, I've never seen a certificate warning that was actually due to a compromise... so I also ignore them all), which leads to hypothetically much less safe behavior than if certificate warnings only happened when rational.

Which is to say, if you believe a certificate that expired yesterday should result in a scare screen to users or worse with HSTS, interfering with the ability to access it all, you failed security 101.
by AnonC | 2025-07-23 04:09:09+00:00
> We can currently build for nearly all SwiftUI targets: MacOS, iPhone, iPad, Apple Vision Pro, AppleTV. Watch is the odd duck out because it lacks on-device networking that we require for this library.

Could you please elaborate on the statement about Apple Watch? Apple Watch can connect to WiFi directly with Bluetooth off on its paired iPhone. Specific variants also support cellular networks directly without depending on the paired iPhone. So is it something more nuanced than the networking part that’s missing in Apple Watch?
by dnemmers | 2025-07-23 04:09:09+00:00
The single-engine Piper PA-28 aircraft left Montana's West Yellowstone Airport just before midnight

Just two minutes later, the signal was lost.

Not to speculate too hard, but from the location of the crash, and proximity to the departure airport…it sounds like spatial disorientation from night flying and turning in the right environmental conditions.

They were likely spiraling when they thought they were accelerating.
by Thorrez | 2025-07-23 04:09:14+00:00
So put a giant tax on it? That is an interesting idea. I'm pretty sure the people who say it's a right will fight that.

And there's also the question of how big the tax should be. Someone with an illness that requires expensive treatment but is expected to not die for a long time might cost the insurance company millions in treatment. Would that tax be millions?

One problem would be in the case of government-run healthcare, or government-run insurance. In that case, to what extent would the tax just be taking money out of one of the government's pockets and putting it in the other? I'm not sure that would disincentive it.

In fact, some doctors, nurses, might consider it good to help fund the government, and thus it might almost be an incentive for them to do it.
Show HN: PTS Library – Analyze LLM reasoning through "thought anchors"
by codelion | 2025-07-23 04:09:58+00:00
I built PTS (Pivotal Token Search), an open-source library for mechanistic interpretability analysis of language models. The core feature is generating "thought anchors" - identifying which specific sentences in a model's reasoning chain significantly impact task success.

What it does:

- Generates chain-of-thought reasoning traces from any LLM

- Uses counterfactual analysis to measure impact of each reasoning step

- Identifies critical sentences that make-or-break task completion

- Exports semantic embeddings for clustering analysis

- Provides systematic failure mode categorization

Example use case:

I used PTS to compare Qwen3-0.6B vs DeepSeek-R1-Distill-1.5B on math problems and discovered they have fundamentally different reasoning architectures:

- DeepSeek: concentrated reasoning (fewer, high-impact steps)

- Qwen3: distributed reasoning (impact spread across multiple steps)

Quick start:

# Generate thought anchors

pts run --model="your-model" --dataset="gsm8k" --generate-thought-anchors

# Export for analysis

pts export --format="thought_anchors" --output-path="analysis.jsonl"

The library implements the thought anchors methodology from Bogdan et al. (2025) with extensions for:

- Comprehensive metadata collection

- 384-dimensional semantic embeddings

- Causal dependency tracking

- Systematic failure analysis

Why this matters: Most interpretability tools focus on individual tokens or attention patterns. Thought anchors operate at the sentence level, revealing which complete reasoning steps actually matter for getting correct answers.

Limitations: Currently focused on mathematical reasoning tasks. Planning to extend to other domains and larger models.

Links:

- GitHub: https://github.com/codelion/pts

- Research example: https://huggingface.co/blog/codelion/understanding-model-rea...

- Generated datasets: Available on HuggingFace

Would appreciate feedback on extending this to other reasoning domains or interpretability approaches.
by 0xDEAFBEAD | 2025-07-23 04:11:05+00:00
>Studies have also shown that people who don’t smoke but have a family history of lung cancer, such as Ms. Chen and Ms. Liu — both of Ms. Liu’s grandfathers had the disease — are at increased risk. This could be because of shared genetics, a common environment or both, said Dr. Jae Kim, chief of thoracic surgery at City of Hope in Duarte, Calif.

Couldn't this be secondhand smoke?
by sgc | 2025-07-23 04:12:29+00:00
Some of us don't wait for school to introduce us to things, but seek them out because we are interested. And although I saw a couple of these in our libraries, my uni studies had nothing to do with newspapers (as most fields of study don't). Even some I had seen walking by, I never looked at seriously until I found them via a specific google search that showed to me they might be of interest.
by ocdtrekkie | 2025-07-23 04:12:40+00:00
I do see your position re: passwords tend to successfully be canceled and certificates tend to not. But I would certainly argue that the downsides of rotation on user behavior and technical security design are quite costly. They remove a lot of the opportunity for risk-based authentication (like TOFU) and require people set up fragile automations capable of generating keys that claim to be them. And every certificate warning that isn't due to a real security problem creates alert fatigue that makes certificate errors seen as spurious.

I think short certificate lifetimes will be viewed in the relatively short future as misguided as the old NIST recommendation on passwords.