MurphyA/hacker-news huggingface dataset:
by SpaceNugget | 2025-06-17 14:52:26+00:00
I think the point of the comment you replied to is that "reviewing code" is different in a regular work situation of reviewing a coworkers PR vs checking that the LLM generated something that matches what you requested.

I don't send my coworkers lists of micromanaged directions that give me a pretty clear expectation of what their PR is going to look like. I do however, occasionally get tagged on a review for some feature I had no part in designing, in a part of some code base I have almost no experience with.

Reviewing that the components you asked for do what you asked is a much easier scenario.

Maybe if people are asking an LLM to build an entire product from scratch with no guidance it would take a lot more effort to read and understand the output. But I don't think most people do that on a daily basis.
Show HN: Smart Silence – Auto-remind to silence your phone via geofencing
by ebagsnave | 2025-06-17 14:52:29+00:00
Hey HN,

I just released Smart Silence on the App Store — it’s a privacy-first iOS app that helps you avoid your phone going off in quiet places like synagogues, churches, theaters, or meetings by reminding you to silence it at the right time and place.

It uses geofencing to detect when you arrive at or leave a Silent Zone and sends a notification prompting you to enable Do Not Disturb via a Shortcut. Due to iOS restrictions, the app can’t toggle DND automatically — but it gets you 95% of the way there with a single tap or automated Shortcut.

Highlights: • Geofence-based detection: minimal battery impact, no GPS polling • Smart, respectful DND reminders (not forceful or naggy) • Community-powered: users can mark quiet zones and share schedules • iOS Shortcut integration for fast, one-tap activation • No ads, no tracking, no account required

This came from a real-world need — helping people stay respectful in communal spaces without fiddling with settings. I’d love your feedback, especially from folks who care about mobile UX, location-aware automation, and building within iOS limitations.

Try it here: https://apps.apple.com/us/app/smart-silence/id6737205196 Website: sm4r7.io Happy to answer questions, share architecture choices, or talk about where it’s headed (e.g. silent streaks, Android, etc.).
by a_stein | 2025-06-17 14:52:30+00:00
From the blog post:

I've got some big news to share today: Payload has joined Figma. It's as wild and exciting to write that as it is for you reading it.

When we first started talking with Figma, it was about investing in Payload and what we’re doing in open source. They saw what we were building was unique, and it lines up well with how they see the world.

You probably know the entire Payload team has been using Figma deeply for a long time, and it was pretty exciting for all of us to see that they share the same vision we do.

Speaking of which, in the past I’ve talked a lot about a “utopia” — about simplicity and developer experience. My team and I refuse to compromise on design intent, flexibility, and how that translates into well-structured code.

Figma and Payload together can and will solve a problem that’s been bugging me (and probably all of you) for years. The gap between design and code still exists. Designers create in Figma, then devs recreate in code, then content teams struggle to maintain it all. It’s inefficient and frustrating. And historically, the CMS tends to make it worse.

With Figma, we can (and will) solve these problems in new ways without compromising. If either Figma or Payload didn’t see this potential screaming at us from a mile away, neither would have moved forward.

I’d like to assure you directly that, in the immediate future, nothing is changing for users and how you interface with Payload remains the same.

What that means is:

Payload remains open source—with Figma’s full commitment to OSS Our commitment to building Payload and creating the best developer experience possible The self-hosted capability of Payload Our focus on our community (aka: all of you) The team and I will still be running Payload (including Sean) What does change:

We now have more resources We can tackle bigger problems We will integrate with design systems in ways no other CMS can A lot more people will be using, testing, and building on Payload I'm sure you have questions, and we'll do our best to answer and keep up with them in our Discord and on Github. In the meantime, I'm pumped about the future and I can't wait for what's ahead.
by Covzire | 2025-06-17 14:52:38+00:00
>>If you don't like nonbinary pronouns, don't use them.

That's not even what I'm talking about, it's "Body Type A" or "Body Type B" where the proverbial child has been sawn in half so nobody can have it, these mods restore the choice back to people who have a legitimate claim TO their pronouns.
by xpe | 2025-06-17 14:52:42+00:00
> I'm way more comfortable with the "stochastic parrot" framing, since we all know that parrots shouldn't always be taken seriously.

First, comfort isn't a great gauge for truth.

Second, many of us have seen this metaphor and we're done with it, because it confuses more than it helps. For commentary, you could do worse than [1] and [2]. I think this comment from [2] by "dr_s" is spot on:

> There is no actual definition of stochastic parrot, it's just a derogatory > definition to downplay "something that, given a distribution to sample > from and a prompt, performs a kind of Markov process to repeatedly predict > the most probable next token". > > The thing that people who love to sneer at AI like Gebru don't seem to > get (or willingly downplay in bad faith) is that such a class of functions > also include thing that if asked "write me down a proof of the Riemann > hypothesis" says "sure, here it is" and then goes on to win a Fields > medal. There are no particular fundamental proven limits on how powerful > such a function can be. I don't see why there should be.

I suggest this: instead of making the stochastic parrot argument, make a specific prediction: what level of capabilities are out of reach? Give your reasons, too. Make your writing public and see how you do. I agree with "dr_s" -- I'm not going to bet against the capabilities of transformer based technologies, especially not ones with tool-calling as part of their design.

To go a step further, some counter-arguments take the following shape: "If a transformer of size X doesn't have capability C, wait until they get bigger." I get it: this argument can feel unsatisfying to the extent it is open-ended with no resolution criteria. (Nevertheless, increasing scale has indeed shown to make many problems shallow!) So, if you want to play the game honestly, require specific, testable predictions. For example, ask a person to specify what size X' will yield capability C.

[1]: https://www.lesswrong.com/posts/HxRjHq3QG8vcYy4yy/the-stocha...

[2]: https://www.lesswrong.com/posts/7aHCZbofofA5JeKgb/memetic-ju...
by nine_k | 2025-06-17 14:52:44+00:00
At one of my previous jobs, we designed a whole API to be slightly more contrived but requiring only one round-trip for all key data, to address the iffy internet connectivity most of our users had. The frontend also did a lot of background loading to hide the latency when scrolling.

It's really eye-opening to set up something like toxiproxy, configure bandwidth limitations, latency variability, and packet loss in it, and run your app, or your site, or your API endpoints over it. You notice all kinds of UI freezing, lack of placeholders, gratuitously large images, lack of / inadequate configuration of retries, etc.
by dgb23 | 2025-06-17 14:52:45+00:00
Btw that's largely our (web devs) fault.

https://extensiblewebmanifesto.org/

Good intentions and some good ideas. But ultimately lead to a fractured, overly complicated and bloated web.

I say yes to lower level, more general capabilities. But why does that have to mean we get bad APIs (web components, indexeddb, service workers...) and lack fundamental and well established UI components (combobox, toggles, tabs, tooltips, data grids...) and incomplete implementations (lacking HTTP verbs for forms)?

(Also why we're at it, I'm going to sneak in a complaint about half baked and broken language features like `const` and `import`. Also we shouldn't have abandoned Do-Not-Track...)
by abeppu | 2025-06-17 14:53:12+00:00
From the results paragraph in the top of the linked journal site:

> Furthermore, 42% rated one of their experiences to be the single most profound of their lifetime.

> Although no serious adverse events were reported, 46% rated a psilocybin experience as among the top five most psychologically challenging of their lives.

From skimming the paper, it looks like they don't do a correlation analysis between the various questionnaire responses, only between the groups and responses (perhaps correctly due to insufficient data), but I wonder: are you more likely to find the experience profound if it was challenging?
by tonyarkles | 2025-06-17 14:53:44+00:00
You're right most of the time. I have had a 99% "unnoticeable" experience with Starlink in rural Canada. I definitely still experienced rain fade during heavy rain storms and occasional clear-sky blips for 30s-2min or so. Vastly superior to anything else I've used for Internet access in remote areas for sure, but not perfect. I have also experienced longer-term (30 min or so) service degradations where the connection stayed up but the bandwidth dropped to ~10Mbit/1Mbit.

Most of the time no one would notice. For some applications it's definitely something that needs to get designed in.
by wil421 | 2025-06-17 14:53:49+00:00
None of these things happen in my X5. It will even detect my bike rack and not automatically stop like my wife’s X7 does with iDrive 7. You can turn off all the speed warnings but no one is going to do it in a rental.

Not surprised the X2 sucks it’s the cheapest model and usually the Germans do not do well in this category. The cheap small Mercedes are similar.

The biggest annoyance is the horn beeps when I leave the car running and grab something from the trunk.
by addaon | 2025-06-17 14:53:49+00:00
> It depends on location

Can you clarify? From https://www.uber.com/us/en/ride/uberblack/, the only obvious location dependency is that drivers must "meet state- or local-level livery regulations" -- I think this just means that for this subset of drivers, Uber chooses to actually verify that they're following the law? Which I know is a deviation from their usual model, but seems like it's very literally the least they could do. Is there more per-geo (per-country?) variation in what "Black" means that's not documented there?
by okdood64 | 2025-06-17 14:54:32+00:00
2014: Who would not carry their wallet and solely rely on their iPhone to pay for things when running errands?

I understand it's cool to be cynical on HN but: this is a step in the direction for a future world where a lot of countries will let you in with a digital passport.

Now whether you think that's a good thing or not, that's a different story.
by Sanzig | 2025-06-17 14:54:39+00:00
While many websites are bad for large unoptimized payloads sizes, they are even worse for latency sensitivity.

You can easily see this when using WiFi aboard a flight, where latency is around 600 msec at minimum (most airlines use geostationary satellites, NGSO for airline use isn't quite there yet). There is so much stuff that happens serially in back-and-forth client-server communication in modern web apps. The developer sitting in SF with a sub-10 ms latency to their development instance on AWS doesn't notice this, but it's sure as as heck noticeable when the round trip is 60x that. Obviously, some exchanges have to be serial, but there is a lot of room for optimization and batching that just gets left on the floor.

It's really useful to use some sort of network emulation tool like tc-netem as part of basic usability testing. Establish a few baseline cases (slow link, high packet loss, high latency, etc) and see how usable your service is. Fixing it so it's better in these cases will make it better for everyone else too.
by palata | 2025-06-17 14:54:54+00:00
For someone who "works in cybersec", you have surprising opinions...

Like you seem to care about your messages not being entirely public ("And even a bad third-party app will be sufficient to prevent drive-by hackers with a pineapple from reading my messages") but at the same time you're fine with Telegram not being E2EE.

And then you seem to consider that a state actor being able to read the messages in transit is the same as them hacking into the phones?

And it all suggests that somehow the only reasonable threat model is "not caring about a state actor targetting oneself specifically and not caring about anything more than 'drive-by hackers with a pineapple'"?
by fritzo | 2025-06-17 14:54:54+00:00
In defense of ads: Ads do solve the pay-per-use problem, where most apps are subscription based so I'm constantly leaking subscription fees for apps / services I no longer use. Ads are great in that if I stop using a service, I stop paying the attention cost.

Ads also solve the price stratification problem: wealthy users pay with their valuable time, and poor users pay with their less valuable time.
by dghlsakjg | 2025-06-17 14:56:07+00:00
For the love of god, yes, design as if all of your users are going to be on a 1mbps connection that drops out for 5s every minute, because at some point, a lot of them (most of them, I would wager) will be using that connection. Often it is when you are on those connections that it is most important that your software work.

The article looks at broadband penetration in the US. Which is useful, but you need to plan for worst cases scenario, not statistically likely cases.

I have blazing fast internet at home, and that isn't helpful for the AAA app when I need to get roadside assistance.

I want the nytimes app to sync data for offline reading, locally caching literally all of the text from this week should be happening.
by ryandrake | 2025-06-17 14:56:24+00:00
I believed this, too, before COVID hit and I saw ~half my country try to throw everyone else under the bus so that they could continue to eat at their favorite restaurants, and buy their khakis, and hoard goods to price gouge their neighbors, and just making a belligerent scene any time they were unable to do something the way they want to. Many people will naturally pull together and act cooperatively and altruistically, but also many, many people just live to grief everyone else.
by NoGravitas | 2025-06-17 14:56:49+00:00
> Leaving aside the fact that this isn't an LLM problem; we've always had tech debt due to cowboy devs and weak management or "commercial imperatives":

But this is one of the core problems with LLM coding, right? It accelerates an already broken model of software development (worse is better) rather than trying to help fix it.
by mlhpdx | 2025-06-17 14:56:51+00:00
> you should not assume that it's better than around 25Mbps down and 3Mbps up

This is spot on for me. I live in a low-density community that got telcom early and the infrastructure has yet to be upgraded. So, despite being a relatively wealthy area, we suffer from poor service and have to choose between flaky high latency high bandwidth (Starlink) and flaky low latency low bandwidth (DSL). I’ve chosen the latter to this point. Point to point wireless isn’t an option because of the geography.
by cometapi | 2025-06-17 14:56:58+00:00
OpenAI’s latest reasoning model, o3‑pro, represents a significant leap in performance and capability for AI-driven applications. Launched in early June 2025, o3‑pro offers developers and enterprises advanced reasoning, multimodal understanding, and tool use—all at a premium price point. This article synthesizes the most recent announcements, user reports, and benchmark data to provide a comprehensive overview of o3‑pro’s performance, cost considerations, and availability.
by nonethewiser | 2025-06-17 14:57:35+00:00
>I personally find these arguments persuasive. But experience has also taught me that “eat your vegetables” is one of the least effective arguments in the world. Scolding people might get them to agree with you in public, or even in principle, but it’s unlikely to change their behavior once no one’s watching.

I interpret this to mean the author may not actually find this argument persuasive.
by epistasis | 2025-06-17 14:57:45+00:00
When Apple did their disastrous Apple Music transition, I was in the habit of daily recreation that involved driving in areas without mobile access.

All of a sudden one day, I was cut off from all my music, by the creators of the iPod!

I switched away from Apple Music and will never return. 15 years of extensive usage of iTunes, and now I will never trust Apple with my music needs again. I'm sure they don't care, or consider the move a good tradeoff for their user base, but it's the most user hostile thing I've ever experienced in two decades on Apple platforms.
by sneak | 2025-06-17 14:57:52+00:00
That’s false. PC needs to be taken to a judge for a search warrant.

What you are probably thinking of is what is called the “exigent circumstances” warrant exception, and it was misapplied here by over-zealous police who violated his rights.

There is no evidence to support that the injuries sustained by the woman in his apartment were caused by him, according to that document.
by jagermo | 2025-06-17 14:58:05+00:00
I am convinced that you can find waste (probably not as much corruption) in every modern government. However, you need people to really dive into the processes, ask what and why those have been set up in the past (every rule has an origin story) and if they can be bundled or streamlined. Same with expenses, you need things like forensic accountants and time to understand things.

Doge wanted to take shortcuts and destroyed everything without having alternatives in place. They had hoped for short-term wins, and neither the workers there nor their boss has the attention span or the experience necessary to really understand and optimize processes, thus reducing waste.
by em-bee | 2025-06-17 14:58:10+00:00
absence of evidence is not evidence of absence. just because we can't see or measure it, doesn't mean that it doesn't exist.

however, the more important part is that i believe that believing that we have no free will is outright dangerous. if we don't have free will, then how can we be responsible for anything we do. without the belief in free will our life will grind to a halt.

the big mistake that sabine and others are making is that not having free will is entirely illogical. and therefore, as a believer in science i must reject the idea that there is no free will and and call on science to continue to search for the truth.
by morleytj | 2025-06-17 14:58:10+00:00
This is a huge issue for me with a lot of sites. For whatever reason I've spent a lot of time in my life in areas with high latency or jist spotty internet service in general, and a lot of these modern sites with massive payload sizes and chained together dependencies (click this button to load this animation to display the next thing that you have to click to get the information you want) seriously struggle or outright break in those situations.

The ol reliable plain HTML stuff usually works great though, even when you have to wait a bit for it to load.
by bookofjoe | 2025-06-17 14:58:15+00:00
Being significantly older than you (I retired from the practice of anesthesiology at age 67 in 2015) I am able to recount my experience with cocaine use to prepare patients for nasal intubation.

When I began my residency at the UCLA Department of Anesthesiology in the fall of 1977, I was instructed on how to use cocaine.

First, one requested a 2cc glass vial of cocaine hydrochloride solution (4-10% strength, prepared from cocaine powder).

The patient in the O.R. was then sedated heavily to both eliminate fear and anxiety and decrease the stinging and discomfort resulting from the imminent application of the cocaine solution against the nasal mucosa.

Cotton pledgets on thin wooden sticks about 6 inches long were submerged in the cocaine solution until saturated, then very slowly and delicately introduced into both nostrils simultaneously and rotated while being advanced deep into the nasal cavity: usually they went in about half their length.

A nice aid to successful intubation: As a rule, we chose to intubate via the nostril which most easily and deeply accommodated the pledget.

We then waited for 15-20 minutes for maximum local anesthesia and vasoconstriction, then removed the pledgets and proceeded with nasal intubation.

I continued to use cocaine for nasal intubation until I moved to the University of Virginia in 1983; for whatever reasons, the drug wasn't part of our therapeutic armamentarium there, rather lidocaine with epinephrine was employed in the same manner as cocaine solution and produced equivalent results.
by bwfan123 | 2025-06-17 14:58:26+00:00
> I might starting calling this "the original sin" with LLMs... not validating the output.

I would rephrase it - the original sin of llms is not "understanding" what they output. By "understanding" it is meant the "the why of the output" - starting from the original problem and reasoning through to the output solution - ie, the causation process behind the output. What llms do is to pattern match a most "plausible output" to the input. But the output is not born out of a process of causation - it is born out of pattern matching.

Humans can find meaning in the output of LLMs, but machines choke at it - which is why, LLM code looks fine at a first glance until someone tries to run it. Another way to put it is, LLMs sound persuasive to humans - but at the core are rote students who dont understand what they are saying.
by throw7 | 2025-06-17 14:58:29+00:00
I refuse to be in servility to an app and don't use whatsapp. Facebook uses you. Let others, your friends, and family know the facts.

In the case of "business requirements", push back on businesses. You are actually the customer.

I get it though. The best might be a compromise where you try to limit the contacts on whatsapp to only those you have no choice.
by kragen | 2025-06-17 14:58:39+00:00
Dandelion rubber was totally a viable thing in Soviet Russia, or, rather, Soviet Kazakhstan. Like many technologies, it's not a question of feasibility but of economic competitiveness.

https://en.wikipedia.org/wiki/Taraxacum_kok-saghyz

> TKS was cultivated on a large scale in the Soviet Union during World War II. The Soviet Union cultivated Taraxacum kok-saghyz, together with Taraxacum hybernum and Scorzonera tau-saghyz, on a large scale between 1931 and 1950—notably during World War II—as an emergency source of rubber when supplies of rubber from Hevea brasiliensis in Southeast Asia were threatened. The United States, the UK, Germany, Sweden and Spain also cultivated the plant for the same reason. During this time period, the highest yields achieved by the U.S. reached 110 kg of rubber per hectare, while the USSR achieved yields of 200 kg of rubber per hectare. The Raisko sub-camp of Auschwitz was a German-operated production factory for the plant. Some of the women deported on the Convoi des 31000 worked on its production there.[8] With the conclusion of World War II and the return of affordable Hevea brasiliensis rubber (which has 8 to 10 times the yield[9]), the majority of T. kok-saghyz programs ceased.
by xnx | 2025-06-17 14:59:25+00:00
Probably the closest modern analogue is a more realtime version of Google Docs with the comments pane blended in. Slack is popular and useful, but good information that comes up in conversations gets buried by further responses, or lost to dumb retention policies. With chat apps, it takes extra work to preserve the useful bits of conversations. With Wave he goal was to collaboratively build permanent shared knowledge.