HackerNews Digest

September 21, 2026

Grim Fandango Puzzle Document (1996) [pdf]

Comments express strong appreciation for Grim Fandango’s distinctive art, music, and writing, noting its lasting impact and iconic status among adventure games. Many recall personal nostalgia, discovering the game in youth and sharing it with younger players. Opinions on gameplay are mixed; while the atmosphere and style are praised, puzzles are described as both brilliant and frustrating. Additional discussion highlights Tim Schafer’s influence, interest in development documentaries, and admiration for the detailed design documentation accompanying the title. Overall sentiment is positive with some criticism of difficulty and bugs.

Read all comments →

Kev: Tiny Jev-like family of decision models built on top of Qwen3.5

Kev is a family of compact decision‑making models built on Qwen 3.5 (and earlier Qwen 3) that support yes/no (noul), multiple‑choice (choice), and rating (score) questions in a single API call. Three model sizes are released—0.8 B, 4 B, and 9 B—each with LoRA adapters and a pointer head; the 4 B and 9 B variants run in bf16 on a 32 GB Mac, while all sizes run on CUDA. The API matches TypeSafe’s System One, enabling use of the provided Python SDK or a local HTTP endpoint. Requests encode the state text once and attach independent question blocks; isolation is enforced by attention masks (or row‑wise processing for DeltaNet layers). Training uses cross‑entropy on public datasets and generated policy examples (≈10 k decision‑v7, 1.6 k rule‑structure samples) for two epochs with rank‑16 LoRA. Benchmarks report accuracy, Brier score, and calibration across development (decision‑v7) and out‑of‑domain (transfer‑v4/v9) suites; Kev‑9B approaches Jev but shows calibration gaps on new sources. Fine‑tuning on custom JSONL data (few hundred labeled examples) is supported via --init_from to retain base knowledge. Serving on Apple Silicon is slower than on GPU; caching and optional flags (KEV_MERGE, KEV_ATTN) adjust performance. All code, weights, and licenses (Apache‑2.0) are publicly available.

Read full article →

The comments show strong interest in Jev‑style decision models, highlighting their appeal for quick, one‑shot classification and potential to streamline tasks such as frontend styling enforcement, routing logic, spam filtering, and simple game agents. Contributors note impressive community effort on open‑source variants and appreciate the models’ low latency on modest hardware, while also pointing out limitations like lack of tool‑calling, knowledge‑cutoff issues, and the need for continuous fine‑tuning or updates. Overall sentiment is enthusiastic yet cautious about practical constraints.

Read all comments →

AX – Google’s Open Agentic Orchestrator

AX is an open, declarative control plane for executing agentic workloads, originating from Google research on agentic runtime systems and large-scale compute. It targets a new computing paradigm characterized by stateful, bursty, long‑running actors that perform intensive computation for brief periods before pausing for model, tool, or human inputs. Traditional orchestrators for stateless microservices or batch jobs are inefficient for such workloads due to idle sandbox costs and lack of sub‑second suspend/resume capabilities. AX abstracts tasks, workspaces, network policies, and models into core primitives, enabling developers and researchers to manage massive fleets of agents without rebuilding infrastructure. The platform builds on Google DeepMind’s agent runtime research and leverages existing isolation, resumption, and scheduling expertise, while providing agentic abstractions and generative runtime components.

Read full article →

Comments show a largely skeptical view of Google’s Agent Substrate, questioning its purpose, labeling it as over‑engineered and unnecessarily complex, especially given its reliance on Kubernetes and extensive YAML configuration. Many note that similar sandboxing and orchestration solutions already exist, and they doubt Google’s backing or widespread adoption. A minority express interest in its security and isolation features, but overall the consensus points to disappointment with the perceived mis‑marketing, lack of clear use cases, and preference for simpler, more integrated or established alternatives.

Read all comments →

Samsung is expected to more than double output of its HBM4 and HBM4E DRAM

  • Samsung Electronics plans to more than double output of its HBM4 family (sixth‑gen HBM4 and seventh‑gen HBM4E) in the coming year.
  • Glass‑carrier usage, essential for thinning HBM DRAM wafers, will rise 2.5 ×, with outsourced cleaning volume increasing to 50 000 sheets/month (from 20 000 this year).
  • HBM4/4E chips target 12‑layer and higher stacks; analysts infer at least a two‑fold rise in overall HBM4 output despite carrier reuse and yield variations.
  • Mass‑production shipments of HBM4 began in February, using 10‑nm‑class sixth‑gen DRAM and a base die on a 4‑nm process; 12‑layer HBM4E samples were delivered to customers such as Nvidia in May.
  • Expected wafer input will grow ~40 % to ~250 000 wafers/month next year (up from ~180 000).
  • By product mix, HBM4’s share should increase from ~40 % to ~80 % as HBM4E ramps up, positioning HBM4 as Samsung’s core high‑value memory offering.
Read full article →

The discussion highlights concerns that complex manufacturing steps such as die thinning enable high‑volume HBM production, but current bottlenecks—especially sanctions limiting equipment for Chinese fabs—keep yields low and keep HBM prices elevated. This scarcity is seen as driving up consumer DRAM costs while AI data‑center demand absorbs most new supply, leading to worries that the market favors well‑funded AI buyers over everyday users. Some optimism remains that increased HBM availability could eventually lower cloud GPU prices, yet overall sentiment is that the AI‑driven memory surge worsens affordability for consumer memory products.

Read all comments →

What happened to the Snowden archive

The Snowden archive was fully distributed by mid‑2013. The Guardian, Der Spiegel, the New York Times, ProPublica and later The Intercept published documents until early 2015; The Intercept’s final batch was released on 29 May 2019, after which no outlet has published any further material. Snowden first contacted Glenn Greenwald (Dec 2012) and then Laura Poitras, who teamed with Barton Gellman. Encrypted bundles (“astro_noise”, “Pandora”) were handed to Poitras, Gellman, Greenwald, Ewen MacAskill (Guardian), Trevor Timm (Freedom of the Press Foundation) and others; many copies remain encrypted and inaccessible. The Guardian destroyed its London hard‑drives in July 2013 under government pressure but retained a copy in New York; it published ~30 of its ~58 000 documents (0.05 %). The paper ceased releasing documents in February 2014 despite continuing analysis and sharing with the New York Times. The Washington Post stored its copy in a hardened, air‑gapped facility, now in “cold storage.” Both Poitras and Greenwald assert that full copies still exist, but none have been disclosed since 2019.

Read full article →

The comments acknowledge that the Snowden archive offers detailed reporting and recommend reading it, but note that public attention and outrage have waned as the revelations became normalized and Snowden’s exile in Russia reduced his visibility. Many observe a shift in the Overton window, seeing former scandals as routine and questioning the current relevance of undisclosed material. There is skepticism toward ongoing leaks, concerns about “responsible disclosure” losing meaning, and a broader cynicism that institutional turmoil benefits entrenched interests, while newer privacy debates receive more focus.

Read all comments →

Qwen Image 2.1

Comments highlight that the 7 B Qwen‑Image 2.1 model is praised for its compact size, native RGBA transparency, fast inference, and notably strong text rendering compared with other open‑weight generators. Users also value the diversity of Chinese open‑source releases. However, the restrictive commercial‑use license draws consistent criticism, and many note practical shortcomings such as inconsistent prompt adherence, artifact patterns, bias toward Asian appearances, limited video‑editing reliability, and occasional instability. Overall sentiment is cautiously optimistic about the technical progress but tempered by concerns over licensing and reliability.

Read all comments →

The Effect of CRTs on Pixel Art (2024)

The article examines how cathode‑ray tube (CRT) displays influence the perception of pixel art and how artists compensated for hardware limits.
CRTs introduce scanlines, color‑bleeding, and slight blur, which can mask blocky edges but do not eliminate visible pixels; cheap PAL/NTSC sets produce more fuzziness than high‑quality RGB monitors.
Early 8‑bit systems (C64, NES) were constrained to low resolutions (e.g., 160×200) and fixed 16‑color palettes, prompting programmers to employ dithering (pixel‑level patterns to simulate intermediate colors) and anti‑aliasing (intermediate‑color pixels to smooth edges).
16‑bit platforms (Amiga 500, SNES, Mega‑Drive) expanded to 32 selectable colors from larger palettes and modest resolutions (~320×240), allowing richer graphics and more extensive use of dithering/AA.
Signal quality matters: separate RGB (SCART) yields the sharpest image; composite or RF adds additional blur and color artifacts. CGA color‑blending exploits NTSC composite artifacts to create extra colors, unrelated to the CRT itself.
Aspect‑ratio handling differs: CRTs supported non‑square pixels (e.g., 320×200 vs 640×480), while modern flat panels enforce square pixels, causing distortion when old assets are displayed 1:1.
Modern pixel‑art creators often omit dithering/AA, resulting in overly blocky images, despite the fact that these techniques improve visual quality on any display, including CRTs.

Read full article →

Comments express a mixed view of pixel art’s evolution: many acknowledge that modern high‑DPI displays define a separate aesthetic and should not be judged by CRT standards, while also recognizing the nostalgic appeal and creative constraints of older hardware that shaped classic pixel art. There is agreement that CRTs contributed specific visual artifacts—often misattributed to the technology itself—and that modern screens can simulate some of these effects but lack the “warmth” of original CRTs. Critics note a trend toward intentionally blocky modern art that neglects dithering and anti‑aliasing, contrasting it with the more nuanced techniques forced by past hardware limitations.

Read all comments →

Amiga Unix, Again

Amix (Amiga Unix) is a community-driven revival of Commodore’s System V Release 4 for Amiga, originally released 1990‑92 on A2500UX and A3000UX. The project provides a modernized system for 68040/68060 machines and contemporary accelerator hardware, using an open development process documented in “the grimoire.” Installation is available via bootable floppy and CD‑ROM images for real hardware, with emulation support; a classic tape installer is planned. A remote package client, apkg, accesses a hosted repository (pkg.amigaux.org) delivering GNU/BSD tools such as grep, gzip, less, patch, and zlib, and will later include X11R6.3, Mesa, and a native gcc. Current achievements include kernel ports for 68040/68060 (MMU required), Z3660 accelerator drivers (SCSI, Ethernet), Zorro III SCSI drivers, an OpenLook desktop, and a functional Quake benchmark. Ongoing work covers RTG graphics for Z3660, accelerator Ethernet throughput, read‑only CD filesystem, and installer polishing. Future goals are native gcc, full X11/Mesa stack, firmware Ethernet fixes, and a complete release of packages, source, documentation, and manuals. Development combines generative‑AI assistance for reverse‑engineering binary kernels with manual review and hardware testing.

Read full article →

Comments express mixed feelings about heavy reliance on LLM assistance, recognizing LLMs as useful tools but urging less dependence and more authentic author voice. There is notable annoyance toward AI‑generated prose, contrasted with appreciation for its capabilities. The discussion shifts to retro computing, noting historical NetBSD runs on Amiga hardware, questioning the practicality of choosing System V over BSD, and recalling past Debian support for Amiga. Concerns about potential trademark issues and a skeptical “pet‑cemetery” vibe toward AI‑driven project revivals also appear.

Read all comments →

Show HN: Mini-AGI – Dynamic continual learning model trained on 8GB VRAM

mini‑AGI is a byte‑level continual‑learning language model designed to train from scratch on a single consumer GPU with ≥8 GB VRAM. Weights reside on disk and are paged into VRAM as needed, allowing the parameter count to be limited only by available storage. The architecture processes each byte through two dense prelude blocks followed by a recurrent block applied up to 24 times; each application selects its own top‑8 experts from a shared pool, with adaptive depth governed by a PonderNet‑style halting head. Trunk components (embeddings, attention, routers, halting head) run at 0.1× the expert learning rate, drastically reducing catastrophic forgetting (≤0.01 nats loss increase after 524 k characters of single‑subject training). The expert pool grows or prunes based on demand, using recombination of hidden units for new experts and retaining Adam moments per expert. Training uses batch‑1 streaming of raw bytes (256‑byte alphabet), no tokenizer, and rotary positional encodings. The model runs on an RTX 3070‑laptop GPU, occupies ~540 M parameters (≈32 experts resident at a time), and achieves ~2.4 GFLOP/byte training cost comparable to a dense 400 M byte‑level transformer.

Read full article →

The comments convey overall curiosity and optimism about the new approach, with many expressing enthusiasm for its potential to reduce costs, enable local deployment, and more closely emulate brain‑like learning while avoiding catastrophic forgetting. Several users ask about concrete performance, specifically memory retention after topic shifts and ability to generalize beyond memorization, requesting simple tests such as arithmetic. A few playful remarks add a light‑hearted tone, but the dominant view is positive interest coupled with demand for clearer evidence of generalization.

Read all comments →

Spain orders blocks on Archive.today and its mirrors

Spain’s Second Section of the Intellectual Property Commission, within the Ministry of Culture, issued a resolution ordering the blocking of several Archive.today domains and related mirrors. The order required no judicial ruling; it was based solely on a complaint and an internal censorship protocol designed for rapid implementation. Spanish users attempting to reach the service are redirected to a government notice stating the site is “illegal” and accusing them of “facilitating illegal access to content protected by intellectual‑property rights.” The notice warns that such access contributes to criminal activity and may jeopardize the user’s security, data, and devices. The action illustrates an administrative approach to enforcing intellectual‑property enforcement online, bypassing court involvement and applying nationwide DNS or ISP-level blocks.

Read full article →

The comments express strong frustration with governmental and ISP restrictions that block access to archival services and other online content, especially during events like soccer matches, viewing such measures as infringements on a basic right to information. Critics denounce copyright enforcement that hampers large‑scale data collection for AI, labeling it counterproductive and politically motivated. There is widespread support for preserving web history through services like archive.today, with calls for technical workarounds such as VPNs or proxies, while also questioning the role of authorities and private interests in shaping internet accessibility.

Read all comments →