HackerNews Digest

September 12, 2026

google.com/goto: Google's anti-scraping update

Google Search now rewrites organic result links to google.com/goto?url=… instead of exposing the destination URL directly in the HTML. The url= parameter uses a proprietary encoding that cannot be decoded offline; the real target URL is provided only in the HTTP Location header of the /goto response, which must be read (e.g., via a HEAD request) without following the redirect. This change, observed consistently from late August 2026 for logged‑out and private sessions, replaces the older google.com/url?q= wrapper and forces each result to require an additional request to Google to obtain the final URL. The shift is part of Google’s broader anti‑scraping measures aimed at increasing the cost and traceability of automated SERP harvesting by AI crawlers and SEO scrapers. In response, Autom has updated its Google Search pipeline to resolve /goto links by reading the Location header and return the final URLs in its API, preserving existing integration behavior.

Read full article →

The comments express widespread dissatisfaction with Google’s shift to redirect URLs, opaque tracking, and algorithmic result shaping, which many view as a decline in transparency, user control, and search quality. Users cite nostalgia for earlier, less‑curated results and report turning to alternatives such as Yandex, DuckDuckGo, Brave, Kagi, Mojeek, and self‑hosted solutions, valuing direct links, privacy and open indexing. A minority downplay the change or see it as routine, but the dominant sentiment condemns the practice as detrimental to user autonomy and the openness of the web.

Read all comments →

Navier-Stokes Announcement

The page announces the 2026 Clay Research Awards. Recipients are grouped into three teams: Tuomas Orponen (University of Jyväskylä), Pablo Shmerkin (University of British Columbia), Hong Wang (IHES and NYU), and Joshua Zahl (Nankai University); Robert Burklund, Jeremy Hahn, Ishan Levy, and Tomer Schlank; and Yu Deng together with Zaher Hani. The award citation highlights the “remarkable” contributions of Orponen, Shmerkin, Wang, and Zahl. The page also includes four images with alt‑text captions: C. Fukushima and J. Westerweel of the Technical University of Delft; a photo of mathematician Martin Bridson; Anna Skorobogatova; and a generic image representing the Clay Research Award.

Read full article →

The comments emphasize that the claimed Navier‑Stokes solution does not yet meet the Clay Mathematics Institute’s eligibility requirements, noting the need for publication in a peer‑reviewed journal and a two‑year waiting period before evaluation. Skepticism is expressed about the certainty of the result and the neutral language of the announcement. Several remarks criticize the prize‑driven drama surrounding Millennium problems and voice concern that AI‑generated breakthroughs may diminish the traditionally solitary, personal nature of mathematical research, while acknowledging the broader excitement about accelerated progress.

Read all comments →

A misalignment of AI in mathematics

The discussion reflects widespread unease about AI‑generated proofs reshaping mathematics, emphasizing worries that rapid, incomprehensible solutions could erode traditional measures of achievement, credit attribution, and the educational value of struggle, while also prompting fears of a secrecy shift and reduced motivation for researchers. At the same time, participants draw parallels to past technological disruptions, note potential for increased collaboration and new research infrastructure, and suggest that redefining success and credit mechanisms may be necessary rather than halting AI progress. Overall sentiment is cautious, recognizing both risks and possible adaptations.

Read all comments →

Usenet rewind archive search engine

The comments express strong appreciation for non‑Google Usenet archives, noting they reliably retrieve old posts that Google Groups often blocks and serve as valuable historical resources. Simultaneously, there is notable concern about the permanence of personal information posted decades ago, with worries that preserved data can be exploited for unwanted surveillance or reputation damage. The discussion balances nostalgia for early internet culture with criticism of the inability to opt out of archival projects, highlighting both the utility and the privacy risks of maintaining these archives.

Read all comments →

I spent $220 on Google app ads and 60% of the installs were robots

The author ran a Google Ads campaign for the Android puzzle app Dayzle at CA$40 per day, targeting installs. After removing the target CPA, the campaign spent CA$80 daily and reported 21 installs, but the app’s admin panel logged only one. Raw analytics showed 21 new devices, 20 of which ran an outdated app version that Play Store no longer serves—indicating the installs came from an external source despite being credited to Google Play. These devices opened the app once, recorded zero screen time, and never returned, spanning 28 phone models across 19 US states. Over two weeks, 56 billed installs occurred: 33 matched this bot‑like pattern, 7 originated from untargeted countries, and 13 were genuine users who completed 92 games. The author attributes the fraudulent installs to a bot farm that watches the ad video, then installs a locally cached APK, exploiting Google’s install‑based optimization loop. He has filed an invalid‑traffic claim, switched the campaign goal to “won a puzzle,” and advises developers to audit install metrics for similar bot activity.

Read full article →

The comments convey strong distrust toward major ad platforms, describing pervasive bot traffic that inflates clicks and installs while delivering little genuine conversion. Many users report wasted spend, ineffective reporting mechanisms, and limited recourse, attributing the issue to systemic fraud incentivized by network operators rather than advertisers. Strategies such as extensive IP exclusions, chargebacks, and focusing on cost‑per‑acquisition rather than clicks are mentioned, while smaller businesses express frustration about the difficulty of reaching real audiences through these channels. Overall sentiment is markedly negative and skeptical.

Read all comments →

Retrospectively Reverse-Engineering Apple's Neural Engine

The article documents a reverse‑engineering effort of the Apple Neural Engine (ANE) used in M1 chips, focusing on its internal architecture rather than trying to make it a general‑purpose accelerator. The ANE comprises 16 compute cores, each with 128 FP16 (or 256 INT8) MAC lanes, giving 2 048 parallel MACs that perform fixed‑point multiply‑accumulate with a 32‑bit accumulator saturating at 2¹⁵. Dot‑product, convolution, and attention operations are distinguished only by data‑mapping and scheduling, while the post‑MAC activation is applied point‑wise via a 33‑entry piecewise‑linear lookup table (mode 2) with linear interpolation and a scaling factor R that controls knot spacing.

The driver does not issue high‑level opcodes; instead it loads a pre‑compiled command stream of fixed‑size task descriptors (TDs) into a task queue (TQ). Each TQ holds status, priority, two descriptor slots, and a 32‑entry BAR table for virtual‑address base relocation. Submission uses TM_ADDR, TM_INFO, and TM_PUSH registers, resembling a GPU push‑buffer. The hardware walks the descriptor stream, executes DMA moves, kernel configuration, and PE operations without dynamic address calculations, indicating a highly static, data‑flow‑oriented execution model. The analysis concludes that ANE’s design reflects early CNN workloads and that later integration of its cores into the GPU marks the end of the standalone NPU.

Read full article →
Read all comments →

Great Lakes sturgeon may be 400 years old:Scientists rethinking how to save them

Lake sturgeon in the Great Lakes may live 200–400 years, far longer than the previously estimated 150 years. Researchers led by Ed Baker (Michigan DNR) analyzed over 40 years of capture‑recapture data, tracking individual growth between captures and modeling time to reach adult size. A male caught in 1990 grew only 7 cm over 34 years (≈0.21 cm yr⁻¹), yielding century‑scale age estimates. This suggests many extant individuals could have been alive when Europeans first explored the region. The species, once abundant, lost ~99 % of its historic population due to overfishing and habitat loss; it is now listed as at‑risk in Ontario and endangered across the Great Lakes. Conservation plans, currently a century‑long effort, may need revision to accommodate the sturgeon’s extreme longevity. Indigenous perspectives view the fish as “grandfather” elders, reflecting its ancient lineage (>150 Myr) and cultural significance. Ongoing recovery includes hatchery releases and training programs with First Nations communities.

Read full article →

The comments express appreciation for sturgeon sightings, describing them as impressive and reminiscent of ancient creatures. Observations note clear water and size, and there is a hopeful tone regarding ongoing conservation measures. Overall sentiment is favorable, emphasizing the majesty of the fish and support for efforts to protect them in the future.

Read all comments →

A Design Space Exploration of Async/Await

The paper “A Design Space Exploration of Async/Await” analyzes straight‑line asynchrony across modern languages (Python, Rust, Swift, C#, JavaScript, Tokio, Smol, Trio). Using a simple pseudocode example—logging in a background task and awaiting it—the authors show that seven runtimes produce four distinct outputs, and no two produce the same result for all three program variants. They attribute this variance to design dimensions that affect observable semantics rather than performance. Nine dimensions are identified and grouped into three lifetime phases: Start of Life (e.g., eager vs. lazy task creation), End of Life (e.g., dynamic vs. indefinite extent, destruction policy such as cancellation or awaiting), and Cancellation (e.g., propagation direction, cancellation awareness). Two dimensions—Dynamic Extent and Destruction—explain why Swift prints “AC” while Trio prints “ABC”. The authors formalize the space with a core calculus and small‑step semantics, highlighting rule choices that cause divergent executions. The work demonstrates that async/await designs are far from uniform, each reflecting trade‑offs in ergonomics, memory, and semantics.

Read full article →

The comments broadly praise the comprehensive taxonomy of async/await design dimensions as a valuable, clarifying resource that aids understanding across languages and informs language design decisions. Readers note its usefulness for navigating trade‑offs, comparing frameworks, and teaching. Critiques focus on omissions such as JavaScript’s AbortSignal, Zig, and stack‑ful coroutine models, and on perceived biases in the quiz’s developer categorization. Several contributors reflect on the complexity of async versus threading, emphasizing the need for nuanced choices tailored to specific use cases. Overall sentiment is appreciative yet calls for broader coverage and finer granularity.

Read all comments →

Show HN: Bodily Oddities

  • Jamais vu: feeling that a familiar word, face, or place seems new; opposite of déjà vu; >50 % of participants experience it after ~30 repetitions in lab; prevalence unknown, thought rarer than déjà vu.
  • Prosopagnosia (face blindness): difficulty recognizing faces, congenital or acquired after brain injury; estimates 1–2.5 % (≈1 in 100–1 in 40) depending on testing.
  • Aphantasia: lack of visual mental imagery; ~1 % report no images, ~4 % have faint or no images, a minority have hyper‑ vivid imagery.
  • Clinodactyly: permanent forward bend of the middle joint of a finger, usually the little finger; occurs in <1 % of people; mild cases are asymptomatic but may progress with growth.
  • Accessory thumb‑index tendon: when the thumb flexes into the palm, the index fingertip bends simultaneously; prevalence averages ~20 % but reported ranges span 5–60 %.
  • Oculocardiac reflex: pressure on the eyeball or traction on an eye muscle can induce bradycardia; observed in 14–90 % of eye‑muscle surgeries, especially in children; not a safe method for self‑induced heart‑rate reduction.
Read full article →

The comments collectively express enthusiasm for the site’s collection of bodily oddities, with many users sharing personal experiences such as visual phenomena, ear movement, hypnic jerks, and other rare sensations. Contributors frequently suggest additional entries, request clearer images, and note occasional inaccuracies. A notable portion critiques the reliance on AI‑generated text and visuals, describing the execution as weak or careless, while still acknowledging the concept’s appeal. Overall sentiment is supportive yet mixed, combining appreciation for the resource with calls for improved curation and higher‑quality content.

Read all comments →

Designing for Dual Screen and Foldable Devices with CSS (2023)

  • CSS provides two media queries for foldable devices: @media (horizontal-viewport-segments: <count>) targets side‑by‑side screens (book mode); @media (vertical-viewport-segments: <count>) targets stacked screens (laptop mode).
  • A set of CSS environment variables (viewport-segment-width, viewport-segment-height, viewport-segment-top, viewport-segment-left, viewport-segment-bottom, viewport-segment-right) return the dimensions and position of each display segment using a 0‑based (x, y) coordinate grid.
  • These variables let developers create responsive layouts that adapt to any foldable geometry without hard‑coding device‑specific sizes. Example: using grid-template-columns: env(viewport-segment-width 0 0) 1fr; inside a horizontal‑segments media query creates a two‑column grid where the first column fills the left screen.
  • Adoption should be guided by user analytics; forecasts predict >21 M foldable devices shipped in 2023.
  • Current browser support: Microsoft Edge stable implements both media queries and environment variables; Chrome stable lacks support, requiring the experimental flag (chrome://flags) or the Surface Duo emulator.
  • The article serves as a concise overview; a deeper implementation guide is available on Smashing Magazine.
Read full article →

The comment expresses skepticism about automatic UI splitting, arguing that users should retain control over when and how panes are divided, even on devices with wide or foldable displays. It stresses that a larger screen is typically sought for viewing existing content rather than having applications impose a dual‑pane layout. Compatibility concerns are also raised, noting that current browsers such as Safari lack support for the relevant viewport‑segment features.

Read all comments →