HackerNews Digest

January 21, 2026

A 26,000-year astronomical monument hidden in plain sight (2019)

The western façade of Hoover Dam includes “Monument Plaza,” a terrazzo floor designed by artist Oskar J. W. Hansen and commissioned by the U.S. Bureau of Reclamation in 1931. The floor is a celestial map that encodes the dam’s completion date within the 25,772‑year axial precession cycle of Earth’s rotation. The central flagpole marks the precessional pole; concentric markings indicate the position of Polaris at the opening date, the historic North Star (Thuban) for the Egyptian era, and the future North Star (Vega). Additional inlays show the planetary positions and bright stars visible on the night of the dam’s inauguration, allowing the exact date to be determined within a day. Historical documentation was scarce, but Bureau historian Emme Woodward provided original photographs, construction terminology (“Safety Island”), and the technical blueprints. The author used these drawings to overlay a diagram clarifying the layout. The monument functions as a 26,000‑year astronomical reference, analogous to the precession element used in Long Now’s 10‑kyr Clock.
Read full article →
The discussion emphasizes fascination with long‑term astronomical monuments and the ingenuity of embedding future‑date markers in architecture, praising the Long Now Foundation’s work while lamenting the loss of a similar star map due to demolition. Contributors note the shifting North Star caused by precession, contrast historic, purposeful design with today’s efficiency‑focused construction, and express hope that such thoughtful artifacts endure for future generations. Overall sentiment is appreciative of enduring, symbolic art and concerned about preservation challenges.
Read all comments →

Claude Chill: Fix Claude Code's Flickering in Terminal

The GitHub repository davidbeesley/claude‑chill displays an access‑restriction notice (“You can’t perform that action at this time.”). The page includes a series of badge images whose alt texts reveal key metadata: a continuous‑integration (CI) badge, an MIT‑license badge, and platform badges for Linux, macOS, and Windows, indicating the project targets those operating systems. A Rust badge denotes the implementation language. Additional badges reference three social‑media handles: @davidbeesley, @claude, and @mulfyx, likely the author and related accounts. No further code, documentation, or functional description is present in the scraped content.
Read full article →
Comments express widespread frustration with an ongoing flickering problem in Claude Code that remains unresolved, noting its negative impact on terminal scrolling and formatting. Users criticize Anthropic’s decision not to open‑source the project, suspecting poor code quality, while also acknowledging recent community fixes that reduce the issue and expressing gratitude for those improvements. Opinions are divided between disappointment over the prolonged bug and optimism about contributions that enhance usability, with a general desire for a permanent resolution.
Read all comments →

California is free of drought for the first time in 25 years

California has reached a drought‑free status for the first time in 25 years, with the U.S. Drought Monitor reporting zero areas of abnormal dryness as of early 2026. The improvement follows a series of intense winter atmospheric rivers that filled reservoirs—14 of 17 major ones are now at ≥70 % capacity—raised snowpack to 89 % of the seasonal average, and left much of the state unusually wet. UC climate scientist Daniel Swain notes wildfire risk is currently near zero, but cautions that climate‑driven “atmospheric sponge” effects will likely produce more extreme swings between heavy precipitation and severe dryness, increasing future fire danger. Historical context includes a 1,300‑day drought from Feb 2020 to Oct 2023 and a prior severe drought (2012‑2016). While short‑term water‑supply and fire threats are low, ongoing monitoring of snowpack, reservoir levels, and the broader western water system—including the Colorado River—remains essential.
Read full article →
Comments note that recent California rainfall, boosted by state‑funded cloud‑seeding projects, has temporarily eased drought metrics but also caused flooding and property damage. Contributors emphasize historical cycles of wet and dry years, highlight ongoing concerns about depleted groundwater, insufficient snowpack, and the limits of reservoirs and infrastructure. Many view the “drought‑free” headline skeptically, linking extreme weather to climate change and questioning long‑term water‑policy effectiveness, while some express brief optimism about greener conditions and joke about the situation. Overall sentiment is cautious, balancing short‑term relief with deeper systemic worries.
Read all comments →

Are arrays functions?

The post examines the view of arrays as functions whose domains are isomorphic to contiguous integer ranges, a description from Haskell documentation that the author now finds insightful. It surveys prior languages that exploit this correspondence: K uses unified syntax f[x] for both, but its bulk‑operation model and lack of a type system limit the analogy; Dex distinguishes functions (a → b) from arrays (a ⇒ b) while offering parallel syntax (λx→e vs. for x.e) and mapping functional concepts (currying ↔ flattening, partial application ↔ fixing a dimension, transpose ↔ argument swapping). The author then evaluates whether Futhark could merge arrays and functions. Type‑level unification is blocked by Futhark’s restrictions on higher‑order functions and its explicit size‑indexed array types, which would require dependent types. Syntactically, replacing a[i] with a i is trivial, but slicing poses challenges: treating slices as array‑indexed applications would break Futhark’s guarantee of free slicing and demand complex analysis. The author suggests a language offering shared abstractions (functorial map, scan, reduction) for “array‑like” types rather than a single unified type.
Read full article →
The comments discuss the conceptual overlap between arrays and functions, noting that TLA+ and functional languages treat arrays as mappings from indices to values, which aligns with mathematical definitions but may feel abstract for everyday programming. Opinions diverge on the practicality of this view: some see it as primarily relevant to language designers and theoretical work, while others find it unnecessary for routine code concerning performance and memory. Reactions to Haskell’s documentation are mixed, with a few considering it overly formal and others appreciating its precision, reflecting broader disagreement about the usefulness of such formal descriptions.
Read all comments →

Instabridge has acquired Nova Launcher

Nova Launcher has been acquired by Instabridge, a Swedish company focused on internet connectivity solutions. The new owners state that Nova will continue operating; their immediate priority is maintaining stability, Android compatibility, and active development. Their stewardship plan emphasizes preserving performance and customization, fixing bugs, and responding to community feedback via Reddit, Play Store reviews, and email, with a dedicated support channel forthcoming. The acquisition aims to secure a sustainable business model: they are considering paid tiers and possible ad‑supported options for the free version, while Nova Prime will remain ad‑free. Existing Nova Prime purchases will be honored, and the price has been set to $3.99 USD. Open‑sourcing is under evaluation, with considerations for licensing, security, and trademark issues. Privacy policies will limit data collection to purpose‑driven needs and will not involve selling personal data. Instabridge commits to gradual, quality‑focused development rather than rapid feature releases.
Read full article →
The discussion centers on Nova Launcher’s acquisition, staff reductions, and the founder’s departure, which have sparked widespread distrust about the app’s direction, data handling, and potential ad integration. Users report performance degradations, widget glitches, and intrusive permission requests, prompting many to abandon Nova in favor of open‑source or stock launchers such as Lawnchair, Smart Launcher Pro, Pear, Olauncher, or the default Android interface. While a few remain hopeful for open‑sourcing or a sustainable model, the prevailing sentiment is disappointment and migration to alternatives.
Read all comments →

Show HN: Mastra 1.0, open-source JavaScript agent framework from the Gatsby devs

Mastra is an open‑source framework for building AI‑powered applications and agents, authored by the team behind Gatsby and written in a modern TypeScript stack. The GitHub repository displays typical project badges: npm package version, CodeQL analysis status, star count, Discord and Twitter community links, npm download statistics, and a static build badge. A long list of contributor usernames (e.g., @envoy1084, @sizzlebop, @cmullins70, @Balbader, @SLAI‑HUB, @CLOUDPIXEL‑LAB, etc.) is shown, indicating active community involvement. The page also includes a generic “You can’t perform that action at this time” notice, likely related to a restricted GitHub operation.
Read full article →
Overall sentiment is positive, praising the launch, developer experience, UI, and TypeScript integration. Common themes include appreciation for the framework’s quality, a desire for clearer guidance on practical use cases, and concerns about workflow complexity when using non‑LLM agents, leading some to prefer rule‑based logic. There are worries about platform lock‑in, comparisons with other agent frameworks, and curiosity about future alignment with the Vercel AI SDK and Claude Agent SDK, as well as questions about real‑world applications beyond simple chat bubbles.
Read all comments →

The Unix Pipe Card Game

The UNIX Pipe Card Game is a tabletop activity that uses Unix command‑line tools (cat, grep, tail, head, wc, sort, uniq) to solve text‑processing tasks. Players first decide whether the round is won by the smallest or largest pipe chain required to complete a task. The youngest player selects a task card (e.g., “print the second line”, “print the most common line”, “count lines containing ‘rises’”, “show two random lines”, “make a command chain that prints nothing”, etc.) and cannot repeat tasks. Cards are shuffled face‑down; each player draws the top card in turn and attempts the command pipeline. The first to complete the task scores a point. Play continues until tasks are exhausted, then the game repeats. The description also lists related educational games that teach programming concepts such as Python basics, C pointers, machine code, process substitution, paste/tr/cut/bc, run‑length encoding, function composition, and RISC‑V assembly.
Read full article →
Comments show a blend of enthusiasm and skepticism. Many appreciate the novelty of a physical card game that references Unix pipes, noting its charm, affordability, and suitability as a novelty gift, while some recall similar DIY attempts. However, several point out that the tactile format reduces instant, visual feedback essential for learning, limits replay value, and may be less engaging than a digital or terminal‑based version. Requests for an online version, broader command sets, and extensions for advanced topics also appear, reflecting both interest and concern about its educational effectiveness.
Read all comments →

Provably unmasking malicious behavior through execution traces

The document consists of a title—“The Double Life of Code World Models: Provably Unmasking Malicious Behavior Through Execution Traces”—and a series of image placeholders with alt‑text labels. The images reference institutional and platform logos: Cornell University, the arXiv preprint service (shown twice), a licensing icon, BibSonomy, and Reddit. No abstract, introduction, methodology, results, or discussion sections are included in the provided excerpt, so no technical details, experimental data, or conclusions about code world models, execution‑trace analysis, or malicious behavior detection are available for summarization.
Read full article →
The comments convey strong skepticism toward the presented method, arguing it performs worse than a simple random‑number test and does not improve detection without raising false positives. The high 98.8 % false‑positive rate is seen as unacceptable, leading to the view that further mathematical analysis is not worthwhile. Additionally, there is confusion over inconsistencies between the text and the tables, prompting a request for clarification.
Read all comments →

I'm addicted to being useful

The author describes a strong personal drive to be useful, which shapes their enjoyment of software engineering despite increasing job stress. They compare themselves to Akaky Akakievich from Gogol’s “The Overcoat,” noting that both find satisfaction in work that matches their own dysfunctions. This compulsion manifests as an inability to ignore problems, especially when they are uniquely positioned to solve them, leading to relief when solutions are found. The author argues that many engineers share this internal need—whether for usefulness, puzzle‑solving, or control over their output—rather than external rewards like money or status. Consequently, they advise managing this drive by protecting time from exploitative demands, focusing on impact rather than ticket volume, and avoiding impressing undesired audiences. Recognizing and channeling the intrinsic compulsion to be useful is presented as essential for sustainable productivity and satisfaction in tech roles.
Read full article →
The comments cluster around a mixed view of a strong drive to be useful in technical work. Many describe genuine satisfaction from solving complex problems and helping others, while also warning that without clear boundaries the tendency can become compulsive, lead to burnout, or foster codependent relationships. Several participants note corporate environments can exploit such motivation, causing feelings of exploitation, hollow purpose, or ethical conflict. A recurring theme is the need for self‑awareness, emotional regulation, and balance between personal fulfillment and the demands of a sometimes toxic workplace.
Read all comments →

Which AI Lies Best? A game theory classic designed by John Nash

So Long Sucker is a 1950 game created by four game theorists—including John Nash—characterized by mandatory betrayal for victory. It serves as an AI stress test targeting capabilities that typical benchmarks overlook: the ability to lie convincingly, recognize optimal moments for betrayal, negotiate alliances, and plan multi‑turn betrayals. The game involves four players each with colored chips. Players take turns placing chips onto piles; when a chip matches the one beneath it, the player captures that pile. If a player runs out of chips they must solicit assistance from others or face elimination. The last remaining player wins. This structure evaluates AI performance in deception, trust management, negotiation dynamics, and forward planning.
Read full article →
The comments express a generally skeptical view of current AI‑driven Mafia and deception benchmarks, noting frequent misunderstand‑based behavior, unclear rules, and limited strategic depth in many models. Users report that stronger models sometimes survive by appearing naïve, while others fail to apply reasoning tools, leading to inconsistent outcomes. Several participants highlight more rigorous multi‑agent tests such as the “So Long Sucker” benchmark, which reveal stark performance differences across models and suggest that settings, temperature, and evaluation design heavily influence results.
Read all comments →