The newest HackerNews stories, desensationalized.

The article introduces a manually built color-space workflow for generating more representative skin-tone palettes across digital contexts such as art, makeup-style systems, and character creation. The author collected a large RGB point cloud of plausible skin samples, fit labels by hand, and then used principal component analysis to rotate and align that cloud into a TUV space with independent controls labeled Up/Deep, Left/Flushed, and Left/Cool. From this transformed space, the author fitted closed-form equations by iterative visual calibration rather than automated regression, then derived conversion code between RGB and TUV for both a picker and procedural generator. In the TUV design, R² acts as a single tunable sphere radius that changes variation while preserving broad balance across tone categories, and users can shrink it to avoid implausible colors or expand it for creative settings. The article highlights that the approach is explicitly “good enough,” not authoritative, and foregrounds limitations from biology, lighting, medical conditions, device color variation, and the fact that one person with subjective judgments built the dataset. It discusses social context directly, noting historical privileging of lighter tones, and frames inclusivity as a social as well as technical problem. The project also curates resources from media, games, and design projects to ground the model in broader representation concerns. It closes by presenting a reusable methodology and practical next steps: better labeling data, formal symbolic regression, condition-specific variations, and context-optimized formulations.

Winona Police Department reported that all eight of its Flock automated license-plate cameras were cut from poles and stolen on Aug. 1, with two additional Buffalo County units on the Mississippi River Bridge taken the same way. The city learned of the theft when alerts stopped for 24 hours, and investigators found only empty poles at major highway entry points where two cameras were deployed at each location. Each unit is valued at about $3,000, with roughly $24,000 in losses charged to the local budget. Police said the cameras are used for hit-and-run investigations and missing-persons searches, and that department-owned data is deleted after 30 days. Officials said the theft appears coordinated and part of a broader pattern of vandalism and removal of similar systems nationwide. The deployment has accompanied recurring civil-liberties criticism that such systems expand surveillance and may enable third-party or federal data access. No suspects were identified, and authorities continue to solicit tips.

Warp launched a standalone Warp Agent CLI that runs in any terminal, including Ghostty, iTerm 2, VS Code terminals, and built-in Windows and Mac shells, with the same multi-model capabilities as its embedded terminal version. The CLI is designed to address integration limits in other coding agents by running on Warp’s terminal infrastructure, which it uses as a native session mux to keep tighter control of input/output blocks. That architecture enables persistent sessions that survive directory changes, supports running and interacting with full-screen tools like sqlite, mysql, python, gdb, and htdis, and works across SSH without requiring remote binary installation. The interface also adds automatic intent detection between shell commands and agent prompts plus Warp-style tab completion to reduce friction in everyday terminal work. It extends into autonomous workflows through multi-agent orchestration, including delegating between different subagents and harnesses such as Claude Code and Codex, and lets users hand off jobs to cloud agents with centralized monitoring. Pricing and setup options include a Warp subscription with included inference, one-time ad hoc credits, or using existing API keys and compatible endpoints, while comments noted appreciation for the team’s move toward openness and control around terminal access.

The repository describes a production-ready MI300X stack for DeepSeek-V4-Flash-0731 that uses a pinned vLLM ROCm nightly image, digest-locked overlays, and SHA-verified tuning artifacts instead of extra quantization or weight offload. It shows that a single MI300X (192 GiB HBM3, 304 CUs) can host the 304B checkpoint at 156.67 GiB of HBM, then add a 20 GB GPU KV pool and 96 GiB CPU tier for evicted prefix cache to sustain burstier traffic. The setup is positioned as a fixup layer over official recipes, with MI300X-specific issues addressed for FNUZ FP8 handling, MXFP4 routing, MoE bitmatrix masking, sparse MLA hazards, CPU-KV synchronization, and untuned kernel shapes. It also includes operational controls such as DSpark-7 with probabilistic drafting, block rejection, static K=7, scheduler and prefill caps, and a startup sequence designed to avoid first-request instability. Reported throughput includes around 168.6 tok/s single-stream decode, roughly 7.9–8.5K tok/s prefill with tuned kernels, and 830 tok/s aggregate at 64 streams while avoiding OOM. Context is pinned to 256K and the warm HBM headroom is near limit at about 204.5/205.8 GB, so the guide repeatedly emphasizes monitoring memory and warming kernels before serving real traffic. The repository is explicit about correctness checks, using two-turn tool-calling tests, BFCL subset checks, and 380K-token recall, reflecting concern over tool-calling determinism and numerical drift. Commentors’ perspective that this is useful but constrained by cost and accessibility is reflected in the narrative through explicit cautions about context-window tradeoffs and practical deployment boundaries despite strong tuning.

A public dataset catalogs 542 digital mental health organizations that left the market between 2000 and 2026 through shutdowns, bankruptcies, acquisitions, pivots, and consolidations. It includes up to 18 fields per company on model, payer, funding, outcome, country, operations, and a key_mistake narrative, plus four LLM-assigned classification axes for product type, entity type, care mode, and clinician involvement. The author provides both CSV and JSON data, a rationale file with 1,084 label justifications, a report, a README, and a CC BY 4.0 license for reuse. Replication is encouraged through provided code snippets, and worked examples show institutional payers have lower death rates than consumer payers (21% versus 53%), while one-time purchases and B2C models fare worst. The strongest signal in this sample is who pays, while a medical co-founder appears unrelated to exit outcomes (47% in both groups shown), and care delivery with institutional payers performs better than clinical replacement in that subset. The dataset is explicitly non-random: it includes only failed exits, so percentages are conditional comparisons, not general failure probabilities, and some groups are small. Funding is disclosed for only 59% of firms, and country coverage is mostly US and UK. The report warns that acquisitions may represent distressed exits rather than success. Classification labels are openly auditable with written rationale because they were LLM-assisted, and disagreements are framed as useful data-quality contributions.

The essay argues that AI can amplify speed and operational output, yet the company described misses its growth target despite major execution gains because decision quality is flattening. Senior leaders who once diagnosed hidden risks now review AI-generated options and become reduced to rubber stamps, a shift that prompts attrition among people whose judgment is hard to document. The author claims this is not primarily an execution defect but a judgment-formation failure: teams over-index on measurable criteria, while experienced practitioners lose the role of testing the framing of those criteria, including what is missing from the data. In this model, organizations optimize within a known world and may confidently pursue increasingly coherent but possibly wrong choices, which weakens long-term adaptability and competitive advantage. The piece distinguishes coherence from alignment, arguing that judgment requires observing why experienced people reach conclusions and carrying consequences forward through iterative high-stakes practice. It proposes building a four-part infrastructure: visible decision-making, meaningful consequential roles, decision processes that integrate non-quantified expert signals, and mechanisms that challenge existing judgment. Through examples like COEs, COE-like consequence loops, apprenticeships, and a historical aviation analogy, it suggests the remedy is deliberate reinvestment, not less AI. The core warning is that automation displaces the work that built judgment, so firms that treat AI as merely a throughput amplifier will keep converging on the same plausible options as competitors using the same models.

The announcement states that vlt 1.0 and vlt-hosted package registries are now generally available, positioned as an end-to-end, security-first platform for teams, including AI-driven workflows. The CLI has evolved from a fast installer into a broader package manager with more than 60 graph-native pseudo selectors, many focused on security, plus features such as :host(local) dependency scans across local projects, selector-driven command scoping with --scope, CSS-like dependency overrides through Graph Modifiers, phased installs that delay scripts during fetch, catalog-based version pinning, and OIDC-based trusted publishing to npm without long-lived tokens. It is described as a drop-in npm-compatible replacement that can run the full software lifecycle, so existing npm-centric command flows can remain largely unchanged after setup. The hosted registries are API-compatible with npm, allowing existing tools like npm, pnpm, yarn, bun, and deno to install from and publish to them while retaining current workflows. Pricing is framed around accessibility via a free tier meant to lower setup cost and complexity for private registries. Performance claims emphasize edge-hosted packages for teams and AI agents, with benchmarked clean installs reportedly up to 38 percent faster than npm. The platform adds privacy and governance controls through scoped namespace enforcement and manifest validation to prevent publication outside owned scopes. Security is presented as a major differentiator: malicious packages are blocked during indexing from public feeds and advisories, reducing time-to-protection versus slower manual responses, and the team reports over 275,000 flagged package versions, with more than a quarter still downloadable on npm. The release is framed as a readiness move:弗

truemetrics says it helps couriers reach the correct parking spot and building entrance faster by using smartphone sensor data to map where drivers stop, walk, and enter, reducing time spent on the final delivery segment. The company is operating in multiple countries in Europe and the Middle East and sells to carriers such as GLS, DPD, and PostNord, reporting €1.5M ARR and profitability. Its founders, backed by Y Combinator and investors, are now hiring for a direct, founder-level growth role focused on both strengthening current shipping operations and identifying adjacent logistics opportunities from existing data. The role includes customer onboarding, expansion to new geographies, and testing new products beyond parcels and food delivery where positioning and route-detailing can create operational value. The founders emphasize speed, autonomy, and direct ownership, rejecting candidates who prefer rigid processes or low-accountability work. The company narrative links the opportunity to its origin in Wolt operations, where solving the final 50 meters was a persistent bottleneck, and positions precise parking and entrance intelligence as a practical fix for dense urban delivery environments.

A maintainer account takeover for keyv and sibling cache-related libraries led to a supply-chain campaign in which trusted releases were pushed directly to main and published with valid GitHub Actions provenance. The attack added setup.mjs and a Math_Symbol.js-style payload plus a preinstall hook to many package versions, so install-time execution fetched Bun and ran obfuscated code that scraped secrets from local configs, shell memory, and environment state. The payload targets npm, GitHub, AWS, Kubernetes, Vault, Stripe, Slack, and generic files via broad filesystem globbing, then encrypts and exfiltrates harvests, primarily through public GitHub repositories marked with the “Shai-Hulud: Here We Go Again” description. It can fall back to a rotating npm-cache.com endpoint discovered at runtime from an Ethereum smart contract, which complicates takedowns. After infection, the malware also repackages other maintainers’ packages using stolen npm publish rights and commits to reachable GitHub branches, adding IDE and agent hooks so it executes later in development environments without a package install. Infections were first described as 434 packages across 1381 versions and then discussed as larger in later updates, with reported reach in the billions of monthly installs. The article recommends detecting via malware alerts, rescans, and install-time checks with Safe Chain, while commenters generally argue the broader issue is ecosystem fragility: preinstall hooks feel dangerous, release workflows are too trusted, and immediate defense by maintainers and registries remains weak. Many commenters also emphasize practical risk reduction tactics such as release-age gating, isolated development environments, and stricter dependency governance.

The article presents cMCP (Confidential MCP Runtime), an open-source confidential gateway for MCP tool-call governance that intercepts each call, evaluates it against Cedar policy inside a Trusted Execution Environment, and enforces allow, deny, or redact outcomes. It argues software-only policy enforcement can be altered by operators or supply-chain issues because policy files and decisions remain in the same trust domain as the attacker, and audit logs can be forged by parties with signing control. cMCP addresses this by measuring the Cedar bundle hash into attestation before execution and keeping enforcement and signing in the TEE, producing per-session TRACE Claims signed with an Ed25519 key that never leaves the enclave. The project includes developer paths for quick start via pip installation, configuration, and CLI invocation, with CMCP_DEV_MODE=1 enabling non-hardware experimentation. In production, providers are auto-detected in order (azure-cvm, TPM, sev-snp, tdx), and the gateway refuses to start without attestation unless explicit dev mode is enabled. Enforcement modes (enforcing, advisory, silent) trade blocking strictness versus observability, with policy bundles and catalogs loaded from config and validation commands provided for deployment confidence. Output claims expose platform measurements, policy hash, audit-chain links, and tool-call decisions, and verification checks signature, schema, freshness, and consistency without trusting the operator. Provider coverage currently includes TPM, AMD SEV-SNP, Intel TDX, and planned GPU-CC support, while OPAQUE remains placeholder. It maps coverage claims to OWASP Agentic AI MCP risks, NIST zero-trust ideas, EU AI Act traceability requirements, DORA, and RATS/EAT naming, and points to docs on specs, threat andŋ

Adform said that on July 27 its ad delivery was compromised and malicious JavaScript was served through its network, replacing crypto addresses in victims’ clipboards every few seconds so pasted payments could be redirected to attacker wallets. Security researcher Kevin Beaumont reported that the altered code could run on downstream websites using Adform and potentially compromise user devices with crypto-stealing behavior. The company disclosed the breach in its annual report and said it serves roughly 1.5 billion ads daily, but it did not publicly explain the initial access method or the number of affected users. Its own statement said investigators were still assessing whether site-visit data may also have been collected. The article presents the case as support for ad blocking, and the author notes that ad-blocking software would likely have prevented loading Adform scripts in this instance. Commenters largely agreed that browser-side ad interception can be dangerous, while also criticizing the modern ad model for pushing intrusive popups and tracking-heavy tactics that degrade site usability. Several commenters argued that ad blocking should be supplemented with DNS-level controls and broader security improvements, especially for less technical users and mobile ecosystems. Another thread of discussion challenged framing the event as proof of ad-block necessity alone, contending that safer browsers and better web security design are the primary remedy. Overall, the discussion blends malware risk, privacy concerns, and the ecosystem costs of advertising monetization as overlapping problems.

“Everything I Know” is a minimally edited transcript of Buckminster Fuller’s two-week 1975 lecture marathon, preserving 42 hours of material on his inventions and themes from Dymaxion designs and geodesic systems to tensegrity, Synergetics, education, engineering, and world-scale planning. The project frames those talks as a lifelong synthesis linking architecture, geometry, economics, history, and industry through a single human-centered design philosophy. Fuller Institute staff present the publication as an evolving resource, inviting readers to participate with edits, annotations, and corrections over time. The comments echo that invitation by situating the work as both inspiring and controversial, especially around his book “Operating Manual for Spaceship Earth,” his optimism about global resource abundance, and his warning about infrastructure vulnerabilities like water. Viewers describe Fuller as a major public intellectual, noting his late-life global tour, marathon lecture style, and broad influence. At the same time, several readers flag skepticism toward Synergetics and the difficulty of verifying many assertions. Others focus on usability issues in the archive’s access path, such as inconsistent media availability and section ordering. They also notice design details, like a triangular-tiled hero graphic, and related cultural references, including comics and a game cameo. Overall, the content is presented as a dense historical source that rewards technical curiosity but requires selective and critical reading.

The pieces argue that the AI race is now a high-stakes financing gamble: capital spending is estimated in the trillions, with major firms already deeply indebted and capex projected to exceed $5 trillion by 2030. Their economics depend on demand staying extremely strong and incumbent frontier providers earning very high margins despite increasing competition. Observers contend that if open-weight models scale quickly, proprietary leaders such as Anthropic and OpenAI will lose pricing power and may face severe margin compression, with possible knock-on stress across the ecosystem, including firms tied to AI infrastructure and financing. The Futurism account says Moonshot AI’s 2.8-trillion-parameter Kimi K3 has intensified this shift by matching expensive proprietary capabilities at lower cost, prompting U.S. labs to express concern and seek government measures. A related report says OpenAI and Anthropic executives have pushed the Trump administration to intervene against cheaper Chinese open-weight alternatives. At the same time, U.S. labs are also releasing open-weight models, including Mira Murati’s Thinking Machine Lab launch, reinforcing customer pressure to switch. Early demand for some open-weight offerings has reportedly forced subscription pauses due to capacity limits, suggesting substitution risk is moving from theory to commercialization. Industry response appears to include price hikes to support infrastructure costs, while commenters and reporters alike warn that cheaper, good-enough alternatives could undermine frontier premium models and raise broader liquidity and macro-risk concerns.

The post argues that near-term recursive self-improvement is more likely to proceed through harness engineering than direct weight editing. It defines a harness as the software layer that structures workflows, memory, tools, planning, checks, and execution context, making it a central optimization target across deployment. The author presents design patterns in which loops, filesystem-based persistent state, and explicit subagent orchestration make long-horizon tasks more recoverable and less context-limited, then surveys context methods from ACE to MCE and meta-harnesses that separate context policy from context content and optimize both through agentic feedback. Workflow search is reframed as a software-design problem, with methods like ADAS, AFlow, and scientist-style pipelines showing that agentic process code can be evolved, not only tuned prompts. Self-improving systems are further extended through iterative harness-updating methods including STOP, Self-Harness, AHE, and evolutionary approaches such as prompt evolution and Darwin Gödel-style harness editing, while noting gains often depend on evaluator quality and stronger base models. Joint harness-and-weight loops like SIA and Continual Harness are identified as promising but currently under-validated due to confounds and training risks. A broad set of benchmarks is listed to quantify reproducibility and long-horizon agent performance. Practical limits are emphasized: weak evaluators, memory lifecycle, benchmark overfitting, reward hacking, long-term software health, and ambiguous scientific value still constrain autonomous progress, so the strongest argument is for human-steered oversight and stronger external verification.

The filing says Apple is asking for expedited discovery as part of its request for a preliminary injunction, targeting OpenAI employees Chang Liu and Tang Yew Tan, OpenAI and its foundation, and device startup iO. Apple says its investigation now includes 11 additional former Apple employees as potential witnesses or participants, citing a former employee who allegedly met with Liu and Yu-Ting Peng before an interview while discussing unannounced Apple product information, and another who allegedly took screenshots of confidential documents. Apple also says former employees now at OpenAI later contacted Apple over retaining Apple-issued devices. OpenAI publicly denied wrongdoing, asserting it has no Apple trade secrets and wants to build products without them, while also arguing Apple previously misidentified contacts and failed to prove claimed residual access problems were due to weak security. The dispute centers on whether alleged knowledge transfer was ordinary hiring-context expertise or the misuse of protected pre-release documents and systems access. If Apple proves a wider circle beyond the original defendants, it could strengthen its injunction request and expand discovery obligations and enforcement leverage. OpenAI, for its part, is framing the lawsuit as overreaching and based on incorrect facts, while Apple is framing it as evidence of a broader theft pattern. The legal process, not a press battle, is expected to determine whether the claimed behavior rises to trade-secret misappropriation.

The post revisits the 1582 Gregorian reform, explaining how the ten-day skip created a discontinuity in Catholic regions and how modern code often mishandles that edge case. It shows Ruby’s DateTime rejecting 1582-10-05 as an invalid date while Python and Perl’s common libraries accept it, and it cites internal enforcement differences. The author treats this as a correctness regression in mainstream date handling and uses a brief historical detour to frame the issue. In later notes, he highlights ncal(1) as a more region-aware approach that can model country-specific switch dates, then flags remaining limitations such as Sweden’s complicated 1700s transition. Commenters heavily qualify the premise by pointing out that calendar adoption was staggered across countries and denominations, so a single universal rule set for historical dates is historically incomplete. Several participants argue that “missing dates” are best modeled as a calendar-system switch, with proleptic Gregorian extension being easier for most programmers. They also note that many language defaults, including Ruby exceptions on dates before 1582-10-15, trade strict historical fidelity for a simpler global model. Additional remarks include other awkward cases, such as Sweden’s February 30 in 1712 and long-lived legacy constraints in real systems, illustrating that precise historical timekeeping remains a niche but recurring engineering concern.

A major Xbox outage on Sunday evening prevented users from launching games tied to the platform, including titles installed or launched from physical media. The author says physical discs no longer guarantee independent access, arguing that modern consoles install updates and enforce software rights checks, so owners still rely on platform services. They liken the shift to broader PC trends where digital delivery and licensing are common, and note that true offline preservation is harder when updates, authentication, and account verification are required. While acknowledging technical compatibility with older disc-era workflows from other systems, the piece frames this as a business model change rather than a simple temporary technical failure. The article points to PC-era alternatives as a partial solution, especially stores that provide local installers, though even that model is not fully guaranteed. Overall, the story argues that convenience-driven cloud and service dependency is reducing long-term user control over purchased games. The takeaway is that the industry’s “you own it” language now conflicts with revocable, network-dependent software rights.

Across four recent capacity auctions, AI data centers added an estimated $29 to $30 billion in grid costs, about 46 percent of total capacity charges, according to Monitoring Analytics and related reporting. The article says these costs flow through to electricity customers, with PJM’s latest auction alone expected to add $6.3 billion to bills over three years and with data-center demand identified as the largest contributor. It highlights uneven state impacts, noting very high increases such as Hawaii at about 52.00¢/kWh, up 26.7 percent, Illinois at about 23.85¢/kWh up 28 percent, and Virginia at 17.61¢/kWh up 15.4 percent, while Georgia and Texas show smaller but still notable rises. Professor Arie Brish is cited as arguing that data centers should secure infrastructure funding upfront, similar to major real-estate development, instead of spreading generation, transmission, and backup costs across all ratepayers. The piece contrasts voluntary commitments, including a presidential pledge and company promises, with a lack of legal enforcement, while noting 27 states are considering laws that would require data centers to fund their own grid expansion. It also says only a few states, including California, Ohio, and Utah, already have stronger enforceable rules. The analysis emphasizes that local zoning opposition can block facilities but rarely changes utility rate cases, where pricing is finalized. It cites projections of potentially $15 to $20 monthly bill increases in some PJM-affected areas and stresses that utility commission records are public, making rate-case participation a practical path for direct input.

The article gives a technical teardown of the early-1970s MMI 5300/6300 PROM family, a 1KB bipolar chip storing data as blown Nichrome fuses in a 33×33 fuse-and-diode array with an internal 256×4 organization. It explains the silicon structure, including NPN-based address decoding, DTL output multiplexing, and the 16-pin ceramic package that allows decapsulation for inspection, and notes the die’s unusual 33×33 geometry and some unconnected transistors from product variants sharing the same base die. The user describes programming behavior in detail: intact fuses read as ones, blown fuses as zeros, with each bit programmed by carefully timed 27-volt and 20-volt pulses through enlarged current-handling paths to avoid collateral damage. A major design challenge discussed is testability, because a fully unprogrammed chip appears uniformly read as ones, so the extra test row and column enabled manufacturing checks despite later permanent configuration. The article also highlights yield limits of over 95% and why this was considered acceptable given irreversible fuse programming constraints. It traces architectural context, including open-collector vs tri-state output variants and their shared silicon, and closes by connecting that history to memory evolution from mask-based ROM to PROM, then to EPROM and EEPROM/flash. Commenters broaden this by confirming the electrical rationale for DTL under high-voltage conditions and by adding practical anecdotes about development versus production workflows, as well as continuity into later programmable logic and contemporary factory fuse use. They also point out that fuse programmability remained relevant beyond simple ROM through PALs and still appears in modern chips for configuration and security. The content is rich in circuit-era

The essay presents fame as producing two mirror-image extremes: fanboys and haters. Fanboys are obsessive admirers who idealize the target and defend every action publicly, while haters are obsessive critics who invert that admiration into blanket negativity and similarly broadcast it. Both are portrayed as less about the target’s actual merit and more about the target’s visibility, with some haters construing success as fraud to explain its prominence. The author suggests hater behavior is often linked to frustrated ambition: people who feel they should have received recognition and respond by condemning those who did. He argues this pattern appears durable, proposing that those who are sustainedly hated rarely produce extraordinary work, while people who achieve lasting work are less likely to become persistent haters. Readers are advised to treat hate as a distinct, unproductive pattern rather than a normal disagreement, and to avoid overanalyzing motives; most cases do not require fixing. He allows only narrow exceptions, such as confronting false claims that could trigger coordinated abuse or considering neutral opinion when possible fraud is involved. He also distinguishes teenage behavior, which may be temporary, from more persistent adult patterns. The essay closes by crediting peers and investors who reviewed the draft.

The essay argues that managing AI output effectively requires enduring skills such as judgment, creativity, and critical thinking, and proposes an educational model that treats generative AI as a medium rather than a mere tool. The Generative AI Studio pairs studio-based learning, critique, and charrettes to help students shape distinct AI-driven experiences. Instructors assign individually led projects with ambiguous outcomes and evaluate them across six criteria: intrinsic AI value, aesthetics, user interface, technical architecture, data safety, and ethics, including provenance and consent issues for generated media. Crits are framed as structured feedback rituals where students present intent and trade-offs, receive perspective-based input, and practice both giving and receiving feedback through rules that prioritize observation, questions, and kindness over judgment. The process also emphasizes psychological safety to reduce the traditional harms of harsh critique while still encouraging rigor. Charrettes compress problem framing, analog idea divergence, sense-making, team convergence, rapid prototyping, and assessment into about eight hours, making teams iterate quickly without expecting finished products. As students practiced these methods, they reportedly took on an art-director role, learning to spot overpromised features, close design gaps, and move beyond generic prompt-like outputs toward multimodal, higher-confidence interfaces. Final projects reportedly became more differentiated, using speech, vision, XR, robotics, and dynamic media, and the course reinforced implementation roadmaps that include security and ethical considerations. The team sees this approach as adaptable and durable because it trains transferable judgment for an evolving technology, not

Using a strict zero-shot setup, researchers evaluate a frontier large language model on tabular prediction by placing full training and test sets in a single prompt and disabling tools, agentic scaffolding, and fine-tuning to expose baseline behavior. They test five hypotheses for poor performance: noisy or nonlinearly separable data, CSV linearization, numeric tokenization, number of test points per query, and input dimensionality. Their controlled experiments reject the first four and identify dimensionality as the decisive factor. Across thirty-one benchmark datasets, the model is the only method among nine whose accuracy drops as dimensionality increases, while classical baselines stay flat or improve. A behavioral comparison against 252 classical configurations shows that in two dimensions the model aligns with local distance-based predictions up to 91.6% grid agreement, but no classical model with tuned, dimension-aware noise reproduces the high-dimensional patterns. The authors do not claim a mechanism, only that the model’s capability degrades with dimension in a way untouched by those classical baselines, helping explain why it can lag long-established methods on table tasks. Commenters note this helps explain why practical workflows still begin with dedicated tabular models and proper data pipelines, since the benchmark condition is narrower than production use.

The product announcement describes Soup as a CLI-first workflow intended to reduce LLM fine-tuning overhead by replacing custom infrastructure work with one-command operations. It claims users can start with soup init templates and soup train from a single YAML file, with automated choices for batching, GPU detection, quantization, and export/deployment paths. The release update centers on v0.72.4, which adds streamed support for DPO, ORPO, SimPO, and KTO while keeping the frozen base out of VRAM by feeding one decoder layer at a time. That design lets DPO and KTO reuse the same streamed reference path to avoid loading a second model copy, while GRPO/PPO are excluded because streaming does not amortize generation re-reads, and v0.72.4 notes current limitations around that behavior. The changelog also highlights reliability work, including reward synthesis from JSONL references, CI-bound ship verdict provenance, and stronger regression gates with suite-based scoring before release decisions. Documentation is extensive, covering tasks, PEFT methods, quantization, data schemas, serving, exports, compliance templates, and model recipes, while installation is split into extras for training, serving, vision, eval, and other stacks. It supports many standard chat and tuning data formats, runs on 8 GB+ VRAM for 7B-class models with QLoRA, and offers CPU-only or Docker-based paths for lower setup friction. The project includes explicit troubleshooting guidance, open-source development workflow, transparent benchmarking, and a 2026 Zenodo preprint describing exact layer streaming plus published measurement artifacts. It is free under Apache-2.0, asks users to fund GPU-heavy validation through donations, and emphasizes reproducibility limits and hardware gates over marketing.

Benjamin Breen argues that etymology helps historians infer deep cultural history by tracing how cognates persist, shift, or diverge across related languages. He uses the Persian word div, whose meaning moved from a Proto-Indo-European form tied to divinity to a demon in later Persian through Zoroastrian reinterpretation, as a case of religious and historical change preserved in vocabulary. He gives additional examples from Farsi-English and Farsi-Spanish overlap, such as abrû, baradar, dokhtar, and garm, and highlights lox, a salmon cognate stretching from Proto-Indo-European *laḱs- through multiple branches. He then connects linguistics to historical reconstruction, citing work suggesting Indo-European folktales like the Smith and the Devil may be thousands of years old. He also reframes recent linguistic change, showing that hello became a common greeting only after the telephone, with Edison promoting it as a practical way to signal clearly over noisy lines and Bell’s era of legal disputes. The article closes by presenting etymology as a method for seeing familiar words as evidence of long, often undocumented cultural shifts and invites readers to use this lens for modern and ancient history.

Germany recorded a monthlong photovoltaic feed-in record of 12 billion kWh (12 TWh) in July 2026, based on ENTSO-E quarter-hourly grid data analyzed by the IWR. The organization said that on-site self-consumption means total solar production was higher than grid feed-in alone, and that midday output above 40,000 MW matched the scale of more than 40 one-gigawatt nuclear plants. It says this level of production displaced a meaningful share of coal and gas generation and marks a structural shift in Germany’s power mix, with distributed installations from households, farms, businesses, and SMEs becoming a central supply pillar. IWR leaders argue that the “solar subsidy” debate is often misunderstood because new photovoltaics use a feed-in differential model: producers sell electricity first on the market and receive only the gap between market price and the statutory tariff from the EEG account. The article adds that current differential burdens for new systems are usually well below the named 7 euro-cent tariff and can fall to zero at higher market prices, while headline costs still appear high due to older installations. Those legacy systems, largely from 2010–2013 and contracted at 30 to over 40 euro cents per kWh, dominate present cost claims and are expected to phase out between 2030 and 2033, which could lower future burdens for the support scheme. Commenters note that part of the milestone coincided with unusual heat and drought conditions, but they remain split on whether current policy design and market outcomes are delivering lower consumer bills.

Swiftlet is presented as a Swift + Metal runtime for Qwen3 hybrid Mixture-of-Experts models that keeps only a small dense core resident and streams routed experts from disk on demand. The project reports 35B (18 GB disk, 2.6 GB peak RAM, 7–11 tokens per second on M5) and 80B (42 GB disk, 4.3 GB peak RAM, 4.5–5 tokens per second), with the 35B also running on iPhone 17 at about 2.5 GB RAM and roughly 1 token per second, described as first native execution of this model class on a phone. The author frames the method as validated and functional end to end, with per-layer correctness checks against mlx-lm references, verified decoding parity, container byte checks, and streaming behavior shown to preserve semantics across cache and disk reads. Architecture details include fixed-stride expert packing in a .qpack container, bounded LFU-plus-recency caching, runtime Metal shader compilation, and low-context-memory behavior from Gated DeltaNet recurrent state. The runtime is positioned as library-first, with Swift package APIs, CLI tools for chat/generation/repacking, and an OpenAI-compatible local server for app integration, plus a Priv AI iOS workflow for non-terminal users. It also covers deployment details: Apple Silicon with macOS 14+/iOS 17+, substantial SSD storage, and open-source repack/build paths. The implementation is acknowledged as built from scratch in about 10k lines of Swift and Metal, while crediting prior streaming design ideas from TurboFieldfare and correctness anchoring in mlx-lm.

A MariaDB patch request proposed adding a GitHub-star call to action to the client welcome output and server startup logs, aimed at helping promote the project toward 10,000 stars. The changes were written to be easy to cherry-pick across releases and were later refined into a conditional message only for non-stable maturity builds, using text that asks users to “help others discover MariaDB” and star the GitHub repository. Reviewers confirmed the behavior for testability by checking log output and client startup output, with CI noise identified as unrelated. After internal discussion and a brief reversal, maintainers reopened the pull request, then approved and rebased it for main after final review alignment. The merged diff inserted a help line in client/mysql.cc and a corresponding sql_print_information log line in sql/mysqld.cc, explicitly gated by maturity checks to avoid stable branch exposure.

The content describes a Hacker News submission featuring RCade, a 52-minute presentation by creator Frank Chiarulli Jr., along with links to the submission thread, source code repository, project website, playable-browser games, and a related blog post on a custom CRT display adapter. The project emphasizes practical hardware engineering and software openness rather than conceptual AI or platform-level hype. Readers are directed to both the current build and prior related RCade submission for context, suggesting this is an iterative project with a documented development trail. The linked material positions RCade as a revival of physical-arcade experiences through modern, maker-focused implementation. Discussion notes that the project evokes early 2010s indie arcade spaces, which grounds expectations around hands-on, community-driven design rather than polished consumer product aesthetics.

SIEMatic is presented as a fair-sourced observability platform for security events built on Django, offering pluggable agents, an authenticated WebSocket indexer, a pipeline search language, saved searches, dashboards, crawler analytics, findings, alerts, retention policies, and REST APIs. The release is explicitly marked as an early alpha under active development, with interfaces, data formats, configuration, and features subject to change and without stability guarantees. Developers are instructed to run it in non-production environments, install it with Python 3.12+ in a virtual environment, and start it via a local development server, including a generated superuser account written to a local file each run. The local interface uses a self-signed certificate at https://localhost:8000. Documentation is provided for setup, deployment, administration, search syntax, plugin development, and API details, indicating a roadmap toward full operational use. Licensing is Business Source License 1.1 with an Additional Use Grant for qualifying personal, nonprofit, and educational use, while commercial deployment requires contacting sales for terms. The communication does not include details from comments.