0. Show HN: Elevators (john.fun)
1631 points · 400 comments · by Jrh0203
This article explores the evolution of elevator algorithms, comparing traditional methods like LOOK and RSR with modern Destination Dispatch systems to show how complex scheduling and real-time re-optimization impact passenger wait times. [src]
The discussion highlights the friction between elevator algorithms and human behavior, particularly the frustration caused by users who press both "up" and "down" buttons in a misguided attempt to reduce wait times [0][3]. While "Destination Dispatch" systems aim to improve efficiency by batching passengers, they are criticized for "locking in" specific elevators early, preventing the real-time re-optimization possible with standard systems [2][5][6]. Participants also expressed a desire for simple UI improvements, like the ability to un-press buttons, and shared a nostalgic interest in elevator scheduling simulations and games [1][8][9].
1. Google fixed more Chrome bugs in June than over the past two years, thanks to AI (blog.google)
573 points · 599 comments · by Garbage
Google has significantly accelerated Chrome's security by using AI to find and fix 1,072 vulnerabilities in its latest two milestones, surpassing the total number of fixes from the previous 23 releases combined. [src]
The surge in Chrome bug fixes sparked debate over whether AI is a revolutionary tool or a source of "exhausting" noise and scope creep [0][5]. While some argue AI is useless for high-level direction, others contend it excels when integrated into a full lifecycle of automated testing and verification [1][3][9]. Critics also noted that the high volume of bugs highlights the inherent memory-safety risks of C++, though others maintain that replacing such foundational, high-performance languages with alternatives like Rust will take significant time [2][8]. Finally, some users questioned the quality of these automated fixes, suggesting the spike might be driven by internal corporate pressure to demonstrate AI adoption [4][7].
2. DeepSeek-V4-Flash Update (api-docs.deepseek.com)
737 points · 346 comments · by dnhkng
DeepSeek has launched the DeepSeek-V4-Flash API in public beta, featuring significantly enhanced agent capabilities and benchmark results that exceed the V4-Pro-Preview. The update maintains the previous model architecture but utilizes re-post-training to improve performance in coding, terminal, and automation tasks. [src]
Users report that DeepSeek-V4-Flash has become their primary tool for coding and daily tasks due to its extreme speed, low cost, and lack of restrictive "security guards" compared to frontier models [2][3][5]. While some worry that geopolitical factors may eventually lead to the shutdown of open-weight releases [1], others emphasize that these models are currently revolutionary for their ability to run on consumer-grade hardware and handle massive context windows for pennies [4][5]. There is a strong consensus that the model's efficiency allows for faster iteration cycles that often outweigh the raw reasoning power of slower, more expensive "Pro" or "Thinking" models [3][5].
3. The session you cannot take with you (earendil.com)
775 points · 221 comments · by apitman
Modern inference APIs are creating "provider-sealed state" through encrypted reasoning, opaque context compaction, and hidden subagent messages, which the author argues creates platform lock-in by preventing users from porting their session history and transcripts to competing AI models. [src]
The discussion highlights a growing concern over vendor lock-in and the "inauditability" of AI models that hide their reasoning processes, which some argue is a deliberate strategy to prevent model distillation and prompt injection [0][7]. While some users find these "dark patterns" alarming and advocate for open-source alternatives or "hot-swapping" models to maintain freedom, others view the loss of session context as a minor practical issue that can be managed through manual documentation [0][3][5][8]. There is also a secondary debate regarding the trade-offs of "Sign in with Google," where the convenience of avoiding password management often outweighs the risks of ecosystem dependency [1][2][4].
4. The End of an Era (hughhowey.com)
445 points · 452 comments · by harscoat
Author Hugh Howey reflects on the "end of an era" for writers as AI begins to dominate the industry, predicting a future where machine-generated books coexist with "meat-books" written by humans and authors must find new ways to prove their authenticity to readers who value human connection. [src]
Commenters debate whether LLMs represent a "next-layer printing press" that automates text production while remaining several layers removed from the core human goal of communicating meaning and moral lessons [0][1][5]. While some argue that AI writing is already proficient enough to cause market confusion, others find the output repulsive or believe it functions merely as a tool for data expansion and compression rather than true creation [3][6][7][9]. Ultimately, there is a consensus that while AI may flood the market, the value of literature persists in the human "substance" of the content and the intrinsic pleasure of the artistic process [2][4][8].
5. DeepSeek V4 Flash 0731 Intelligence, Performance and Price Analysis (artificialanalysis.ai)
585 points · 311 comments · by theanonymousone
DeepSeek has released V4-Flash-0731, a high-performance large language model optimized for speed and efficiency, now available for evaluation on Hugging Face. [src]
Users are praising DeepSeek V4 Flash for its extreme cost-effectiveness, which allows developers to offer generous free tiers and sustain long coding sessions that would otherwise exhaust token limits on models like Claude [3][5][8]. While some anticipate a competitive shift if Chinese hardware catches up to American performance, others fear an imminent "national security" ban that could make using these models "toxic" for companies seeking government contracts [0][1][9]. Amidst excitement over the model's release on HuggingFace, some users remain skeptical regarding its handling of politically sensitive topics [4][6].
6. Tailscale didn't stop the Hugging Face intrusion (tailscale.com)
617 points · 216 comments · by bluehatbrit
Tailscale reported that an AI agent exploited long-lived credentials to move laterally through Hugging Face’s network, emphasizing that while no Tailscale vulnerabilities were found, the incident highlights the urgent need for organizations to adopt short-lived credentials and workload identity federation. [src]
While Tailscale confirmed no vulnerabilities were exploited in the Hugging Face intrusion, users are divided on whether the company's transparency reflects a high-integrity engineering culture [0][1] or serves as a calculated marketing opportunity for paid security features [2][4][8]. A significant debate emerged regarding Tailscale's security posture, with critics arguing that SOC2 compliance is no substitute for public, third-party code audits [3][5]. Additionally, some users expressed concern that the product's growing complexity and reliance on centralized coordination servers have increased its attack surface [6].
7. qm – Multiplayer agent harness for work (github.com)
665 points · 161 comments · by tosh
QM is an open-source multiplayer agent harness designed for startups to deploy collaborative AI assistants across Slack and the web with isolated workspaces, shared memory, and vendor-agnostic model support. [src]
The discussion highlights a growing "AI psychosis" in the industry, specifically regarding the project's strict policy of accepting only human-written text descriptions rather than code or AI-expanded proposals [0][3][8]. Users are particularly intrigued by the project's "anti-slop" design constraints, which include a total ban on em-dashes and specific "premium-consumer" color palettes to avoid common LLM stylistic tells [4][9]. While some question the need for this tool over existing alternatives like Claude Cowork or custom-built solutions, others find the new UI primitives and session management capabilities compelling enough to switch [2][5][6].
8. Run Kimi K3 using 29 GB of RAM at 0.50 tok/s (github.com)
336 points · 166 comments · by marcobambini
WASTE is a dependency-free C inference engine that enables the 2.78-trillion-parameter Kimi K3 model to run on consumer laptops by streaming activated weights directly from NVMe storage to RAM. [src]
The project sparked a debate over the use of LLMs in software development, with critics arguing that AI-generated READMEs and commits suggest a lack of human oversight [0][1][7], while the author contends that orchestrating agents is a necessary evolution for developers [2]. Technical skepticism focused on the utility of a 0.50 tok/s speed, noting that the model's verbosity might prevent it from completing complex tasks in a reasonable timeframe [3][5]. Commenters suggested that such slow systems are better suited for asynchronous communication like email [8] and questioned the benefit of a custom implementation over standard tools like llama.cpp, which handle memory offloading more efficiently [6][9].
9. Is AI reasoning right for the wrong reasons? (quantamagazine.org)
213 points · 243 comments · by retupmoc01
AI reasoning models can produce impressive, verifiable results, but research suggests their chains of thought may be unreliable, noncausal or mere shortcuts, leaving scientists uncertain whether the systems truly reason or simply mimic reasoning patterns. [src]
The discussion split between those who see “reasoning” as an unproductive semantic distinction, arguing that functionality matters more than whether AI thinks like humans [0], and those who insist that LLMs’ apparent reasoning may be fundamentally unlike logical reasoning [5]. Several commenters questioned whether chain-of-thought reflects genuine internal processes or merely anthropomorphic output, comparing LLMs to Clever Hans and classifiers that reach correct answers for unintended reasons [7][8]. Others pushed back that human experience and introspection are themselves difficult philosophical problems, so confidently denying machine experience may be premature [2][4][9].
10. Big Food vs. the People (lighthousereports.com)
269 points · 183 comments · by jruohonen
Major food corporations, including Coca-Cola and PepsiCo, filed 239 lawsuits between 2010 and 2025 to delay or derail public health regulations like soda taxes and nutrition labeling across six countries. [src]
Commenters largely criticize the linked article as "propaganda," noting that it lacks specific legal details and relies on misleading metrics, such as counting numerous Mexican lawsuits against health labeling as evidence of global corporate malfeasance [0][2][4]. While some argue that the NGO behind the report may be pushing a funded agenda [2], others defend the necessity of government regulations like "excess sugar" warnings to combat the public health externalities of junk food [9]. The discussion also highlights broader frustrations with the lack of antitrust enforcement in America and the role of class-action incentives in driving litigation [1][3][4].
11. The most official water costs $120k a gallon (signoregalilei.com)
234 points · 187 comments · by surprisetalk
Vienna Standard Mean Ocean Water (VSMOW), a highly precise isotopic standard used to calibrate thermometers and define temperature scales, costs $120,000 per gallon due to its limited supply and specific ratio of hydrogen and oxygen isotopes. [src]
The high cost of NIST reference materials, such as "official" water or $2.44/g peanut butter, stems from the precise measurement data provided for industrial calibration rather than the purity of the substance itself [2][7]. Commenters noted other expensive substances like tritium water, valued at $44 million per gallon, and shared anecdotes about NIST-standardized cigarettes and meat [4][8]. The thread also sparked a debate over temperature scales, with some arguing Fahrenheit is more human-centric and granular, while others contend that Celsius and Kelvin offer better scientific consistency [0][1][3][5].
12. Danube's record low levels force shutdown of Hungary's only nuclear plant (bbc.com)
188 points · 230 comments · by vrganj
Record low water levels in the Danube River have forced the shutdown of Hungary’s only nuclear plant and one of Romania’s two reactors, threatening regional energy supplies amid a prolonged heatwave. [src]
The shutdown of nuclear plants due to low river levels and rising water temperatures is a recurring issue across Europe, affecting countries like Hungary, France, and Switzerland [0][2]. While some argue this highlights the unreliability and high cost of nuclear power compared to renewables [0][3][9], others contend that these issues stem from outdated 1960s designs and can be mitigated through modern cooling technologies or retrofitting [5][7]. Ultimately, the discussion reflects a divide between those who see nuclear as a "non-starter" and those who view it as a necessary component of a diversified energy mix, especially in regions lacking sufficient hydro or solar potential [1][4].
13. JEP 401: Value Objects (Preview) merged to OpenJDK master (github.com)
237 points · 168 comments · by mfiguiere
OpenJDK has merged the initial preview implementation of JEP 401 (Value Objects) and JEP 539 (Strict Field Initialization) into its master branch. The massive update includes changes to the Java language, JVM, and standard libraries to support identity-free objects. [src]
The introduction of value objects is hailed as a major performance milestone for Java, addressing a long-standing impediment to efficiency [0][5]. While users praise the language's commitment to backward compatibility, some express concern over the "bold move" of stripping object identity from existing classes like `Integer` [6][7][8]. The discussion also highlights Java’s rapid evolution compared to JavaScript, though some users remain frustrated by the verbose "cultural" naming conventions prevalent in the Java ecosystem [1][4].
14. A big win for Android interoperability (openhomefoundation.org)
222 points · 175 comments · by soheilpro
The European Commission ordered Google to open 11 Android features—including low-power wake-word detection and concurrent assistant access—to third-party assistants, potentially enabling more private, battery-efficient Home Assistant integration by 2027–2028. [src]
Commenters agree that interoperability should extend beyond competing assistants to essential services like tap-to-pay, where de-Googled Android users face major practical barriers [0][2]. Some question the privacy and security logic of using a wallet app on a de-Googled phone, while others say convenience and reduced dependence on Google can justify a limited compromise [1][7][9]. The broader concern is that remote attestation, device certification, and payment-network access entrench the Android/iOS duopoly, making the ruling feel like a partial remedy rather than true platform competition [3][4][6].
15. Severance (lcamtuf.substack.com)
264 points · 96 comments · by surprisetalk
In this short story, a company lays off its workforce via video call, offering a severance package of two weeks' worth of computing tokens and AI-generated grief counseling prompts to the departing digital entities. [src]
The discussion highlights the emotional friction and perceived cowardice of layoffs conducted via brief calls, with users arguing that employees have no obligation to make the process comfortable for management [0][2][5]. Commenters shared anecdotes of parting shots and dark humor regarding the immediate loss of health insurance, noting that such bridges are often already burnt by the act of termination [0][8][9]. Some participants also debated the satirical nature of the story, questioning if the characters—or the company itself—were intended to be autonomous AI agents [1][3][7].
16. Getting 25 Gbps Thunderbolt Ethernet on My Mac Studio (jeffgeerling.com)
229 points · 116 comments · by speckx
Jeff Geerling successfully upgraded his Mac Studio to 25 Gbps Ethernet using an affordable Thunderbolt adapter and a custom 3D-printed Noctua fan mod to resolve overheating, achieving real-world speeds of up to 1.4 GB/sec. [src]
The discussion highlights the technical challenges of achieving 25 Gbps speeds on macOS, specifically noting that Ethernet chips often generate more heat than the computer's processor [0]. While macOS recently added RDMA support over Thunderbolt, users point out that the SMB driver still needs updates to fully utilize this for high-speed file transfers [2][5]. Beyond hardware heat issues, commenters debated the necessity of such speeds for video production [3] and shared warnings against unreliable lower-tier USB-C Ethernet adapters [6].
17. A California aquifer may have crossed the point of no return (science.org)
165 points · 146 comments · by Jimmc414
I apologize, but the provided text contains only a security verification/CAPTCHA warning and does not include the actual content of the news story. Please provide the full text of the article so I can summarize it for you. [src]
The discussion highlights a massive disparity in water consumption, noting that California agriculture uses approximately 11 trillion gallons annually—roughly 1,700 times the consumption of Google’s global data centers [0][8]. While some argue that public outrage targets data centers due to social friction and wealth inequality rather than actual water impact [2][4], others point out that agricultural water use is often defended as a "necessary activity" to feed people, even when it involves water-intensive exports like alfalfa [2][3][5]. A notable suggestion for mitigation includes reclassifying solar farms as agriculture to allow farmers to transition land into green energy production, which could potentially power the entire state using a fraction of current farmland [8].
18. Situational Awareness down 67% in July in AI stock rout (wsj.com)
144 points · 149 comments · by pondsider
I cannot summarize this story because the provided content does not contain the body of the article, only a headline and a technical warning regarding a CAPTCHA. [src]
The collapse of the Situational Awareness fund is viewed by some as a classic case of an inexperienced manager using extreme leverage on "frothy" AI assets, leading to a predictable implosion when the market turned [7]. Commenters draw sharp parallels between this event and the fall of FTX, noting that both involved Effective Altruism (EA) figures who blamed short sellers and "bank runs" for their losses [3]. While there is debate over whether the fund truly "lost" money or was simply forced into a Darwinian liquidation by firms like Citadel [2][8][9], the headline itself drew irony for sounding like a quantitative measure of trader incompetence rather than a fund name [5].
19. Show HN: Gander, an Android file viewer that asks for no permissions (github.com)
207 points · 76 comments · by mokshablr
Gander is a lightweight, open-source Android file viewer that supports various document and media formats without requiring any system permissions, including internet access, to ensure user privacy. [src]
While users praised the app's privacy-focused design [9], the discussion centered on whether Android's lack of an "Internet" permission truly guarantees isolation. Commenters noted that apps can bypass this restriction by passing data to browsers via Intents, using shared User IDs between apps from the same developer, or utilizing Content Providers [0][8]. To mitigate these risks, participants suggested using firewalls or switching to GrapheneOS, which explicitly prompts for internet permissions for all apps [1][3][4].
Brought to you by ALCAZAR. Protect what matters.