The newest HackerNews stories, desensationalized.

The Map is a long-running, hand-made imaginary city project spanning roughly 60 years across more than 4,000 8x10-inch panels arranged in a fixed coordinate field around a circular layout. Jerry began the work in 1963, shelved it for two decades, then resumed and expanded it with a custom instruction deck of about 100 cards that now drives each work cycle. Each card defines specific tasks such as painting, collage work, panel creation, color mixing, copying, retiring cards, archival steps, documentation, and even sales accounting, with red and black card colors setting directional flow. The system measures work in units of covered one-inch squares, while each drawn card can be modified before it appears again, turning the process into a mutable but persistent execution engine. A helper may copy and retire panels, scan assets, and maintain inventory, so the piece evolves through continuous versioning rather than isolated edits. New panels are added from an existing parent-centered coordinate, and their placement follows nearest-edge rules to keep growth roughly circular; work builds on fresh versions rather than overwriting originals. Artistically, the piece advances through multiple abstraction layers, from initial paint and collage to void, red, black, ziggurat, flood, and re-birth phases, with a 42-color palette that shifts over time. Over its history, materials and operations moved from notebooks and hand logs to spreadsheets, printer-based reproduction, and museum exhibition workflows, while guest contributions and archived generations expanded its ecosystem. The result is less a single finished drawing than an evolving generative system where rule sets, chance, and manual observation produce a decades-long map universe.

The writer argues that while open-source teams historically treated vulnerability reports as exceptional—requiring fast acknowledgment, investigation, updates, and credit for researchers—the rise of LLMs has weakened that model in 2026. They note that large language models can now find security issues broadly, making discovery less scarce and insight less exclusive than it once was. As a result, triage quality and prioritization have become the real constraint, because separating real vulnerabilities from noise is difficult whether reports come from people or models. They also contend that strict disclosure secrecy, embargoes, and coordination add less defensive value because attackers can run their own analyses and face similar filtering burdens. The author concludes that open-source security should focus on rapid triage, quick remediation, and preventive engineering, with maintainers using LLM-driven analysis pipelines in continuous integration. They acknowledge complexity in edge cases like reporter behavior and conduct conflicts, and they flag evolving norms around disclosure, while a sponsor section notes ongoing paid maintenance support for secure open-source work through Geomys, including backing from firms in infrastructure and developer tooling, as the practical context for sustaining this labor.

The article argues that the well-known social-engineering burglary of Novell was central to Kevin Mitnick’s reputation and to a later reconciliation between him and former target Shawn Nunley. In the 1990s, while probing Novell’s NetWare-heavy network, Mitnick used war dialing and pretext calls, impersonating an employee as Gabe Nault to request policy-breaking inbound modem access, a move that Nunley recognized as suspicious from abnormal phone behavior and internal signals. Nunley asked for a callback, captured the voicemail, and later said the cassette recording became the primary evidence supporting the felony wire fraud case. After lengthy delays, Nunley withdrew cooperation, Mitnick accepted a plea, and the matter ended with release. Although barred from profiting publicly from his case for seven years, Mitnick later built a security-consulting business and became influential in defensive security training. Their relationship reportedly shifted from prosecution and deception to friendship, with Nunley describing Mitnick as a meaningful figure in his life. On Mitnick’s death in 2023, Nunley said he had been left enough money to buy a Porsche 911 Carrera 4 GTS, closing the story’s gift-car theme with an unusual coda. The narrative blends historical case detail, cybersecurity methods, and ethical complexity by showing how early social-engineering failures and personal trust failures can shape both criminal outcomes and later redemption.

FUTO collected over a million voluntary QWERTY English swipe samples in 2024 and released a cleaned 1-million-entry dataset under an MIT license on Hugging Face in March 2025. The data was gathered from mobile users swiping word-by-word over Wikipedia-derived prompts, then filtered for quality, and was used for both training and evaluation of swipe systems. Community reaction centers on practical performance: many report the new model narrowing the gap with leading proprietary keyboards and improving local dictation quality, including punctuation and batch-speed transcription. Others describe remaining prediction limits such as similar-looking words, doubled-letter ambiguity, punctuation oddities, and contextual suggestion failures that still cause awkward edits. Commenters also link swiping quality to keyboard layout design, arguing that QWERTY is not ideal for gesture typing and that a layout optimized for swipe ambiguity reduction could improve accuracy substantially. Some praise the move toward open models and reproducible data, while others are cautious about real-world polish gaps and platform constraints, especially the absence of iOS support and imperfect feature parity. The thread reflects strong demand for faster, private, and customizable keyboards but also skepticism that speed gains alone will solve all ambiguity and UX issues.

An author described receiving a custom insect print from crysta.ai and testing a Gaussian-splat workflow in which each voxel carries mixed ink and transparency values before being printed layer by layer, producing a clear resemblance to transparent amber-like encapsulation. The author notes they trained the splat at level 0 and in linear color space to preserve physically plausible transparency, but later suspected this may have darkened tones and made adjustments harder for the company’s pipeline. The resulting object looked realistic enough to resemble a real specimen, with realistic light transmission that appeared to reveal internal structure, yet retained visible artifacts and clumpy fur-like detail that made the print feel imperfect. They praised the overall material effect but flagged color and fidelity tradeoffs as current quality limits, including a too-brown, too-dark appearance in their sample. The company is still developing its platform and has recently introduced an alpha editor for placing and scaling splats, which the author welcomes while also requesting better voxelization previews and direct voxel import support, including round-tripping with tools like MagicaVoxel. Overall, the piece reflects meaningful progress in high-detail fabrication while exposing gaps in control, color workflow reliability, and creator-friendly tooling.

Tony Krueger, who worked on many early versions of Word across Windows, OS/2, and Mac, helped change the product from batch-oriented spell checking to live, on-the-fly feedback by adding unobtrusive squiggling under probable mistakes. In early Word, spell checking was a blocking, manually triggered process, and even the first auto mode interrupted user workflows at inconvenient moments. His redesign reduced that interruption and eventually expanded from red spelling marks to green grammar indicators, making error detection a background service. The post also links his impact to a wider audience memory: a friend reportedly introduced him to Penn and Teller after a show, and the duo responded enthusiastically to his feature, and “Weird Al” later included Word squiggles in a parody screenshot. The piece highlights that today nearly every word processor and many other apps show colorful squiggles, implying this interface pattern became a foundational part of writing software. The author notes that Krueger achieved parts of this by reverse-engineering DOS Word because source code was unavailable. A short footnote frames this as evidence that his contribution was unusually technical despite limited visible credit.

The announced London Climate Action Week session on extreme-heat governance and the Adeline Stuart-Watt Award was canceled after a red extreme heat warning from the UK Met Office. The event was to open with the award presentation honoring climate adaptation research from postgraduate students and was hosted by the LSE Grantham Research Institute with the Zurich Climate Resilience Alliance. It was planned to include partner organizations such as Mercy Corps, Practical Action, the IFRC, and speakers from the UN climate resilience community, the UK Climate Change Committee, and HERA. The program intended to review heat governance progress and limits across countries linked to the Zurich alliance, with case studies and a final discussion on practical pathways for stronger global action. The cancellation converted an exchange on adaptation into an immediate signal of heat stress in practice, while also emphasizing that planned institutional dialogue depends on physical conditions. The source framing kept attention on policy relevance, research visibility, and cross-sector coordination across adaptation and resilience communities.

Researchers from Paradigm Shift describe usbliter8, a proof of concept that exploits a DesignWare USB controller bug in iPhone SecureROM to break the boot chain on A12, A13, and S4/S5. The exploit abuses the USB Setup DMA sequence: when a fourth Setup packet arrives, the controller resets DOEPDMA by 24 bytes while only advancing by the actual written size, so short packets create a 12-byte underflow primitive into adjacent memory. A11 is unaffected because its USB driver resets DMA each packet, while A14 and later are protected by SecureROM DART configuration, though A12/A13 still allow exploitable writes through DART bypass. On A12, control is achieved by corrupting stack-adjacent USB task state and pivoting through a saved LR overwrite, then using a ROP-style sequence to jump into the A12 boot path. On A13, pointer authentication prevents direct LR abuse, so the team bypasses heap checks, task context constraints, and panic flow to preserve execution context, then overwrites a USB IRQ handler to gain code execution. With full access established, they switch to EL1 via an in-ROM SVC path and jump through the boot trampoline, handling A12 and A13 differences such as stack-gated validation behavior and PAC-authenticated branching behavior. Post-exploitation includes restoring runtime state to avoid instability, patching DFU handlers, injecting the PWND marker into USB serial data, and adding commands to demote product mode and boot unsigned iBoot images. On A13, corruption is broader, so they restart SecureROM from SRAM after remapping MMU tables so execution can continue from relocated, patched ROM code. The authors stress this is coordinated disclosure and that affected A12/A13 hardware is effectively unpatchable in firmware, so long-lived devices stay exposed for life

The post critiques what it calls selfish LLM use: writing that saves the author time but shifts review and interpretation cost onto others. It defines the term as AI-generated or AI-heavy output that reduces net productivity and proposes covert social feedback using emojis to signal low-quality or overly generated content while preserving plausible deniability. Passive-aggressive options include an amphora, paperclip, minus sign, and slot-machine motifs; stronger options include a crutch, parrot, sparkle, and biohazard; positive replies include human-effort markers such as brain, palette, and green heart. The author admits the scheme is partly satire, then recommends less punitive alternatives: engage with decent human work, ask short reflective questions, and treat overreliance on AI as often time-pressure driven rather than malicious. Practical social norms are then suggested, including a PR checklist in software teams and a tool to truncate verbose comments to reduce review noise. Commenters generally accept the premise but caution that style alone is a weak signal, warning that dismissing em-dash and general writing quality as "obvious AI" can be unfair and even insulting. They also suggest older language conventions should not be equated with AI use and cite false positives where unchanged pre-ChatGPT pages were mislabeled. Another comment frames the idea as a lightly serious joke born from a family discussion, reinforcing a tone that is half satire and half social experiment.

The interview frames Xerox PARC as a research culture built on radical freedom paired with annual accountability, where useful outcomes mattered more than rigid definitions of success. It contrasts research and engineering as different risk models and shows Interlisp as a rare environment that matured from a live production system into a research platform, making software a living workspace rather than a file-and-build pipeline. The guests describe “residential programming” as editing and evolving a running system directly, which enabled rapid iteration, broad introspection, and immediate fixes but also encouraged internal coupling that later constrained maintainability. They argue this mode produced breakthroughs in systems like NoteCards, while requiring stricter interfaces and product discipline once scale and collaboration expanded. The conversation places PARC’s later commercial gap in context: many inventions assumed networked infrastructure and expensive hardware that the market had not yet adopted, so even strong technical ideas could miss adoption windows. Their modern parallel is cautious but concrete: web stacks, microservices, and interactive scripting echo parts of the model, yet few tools match its deep live-patching transparency across layers. They also point to Medley’s revival as active software preservation, with interlisp.org offering documentation, project history, and runnable environments so obsolete systems can be studied by use, not just description. The AI section warns against conflating fluent output with understanding, distinguishing past symbolic work from today’s machine-learning systems and arguing for practical skepticism. Commentary-like reflections in the piece extend this to broader research history, including FGCS as an example of unf

The post argues that harness-level loops now shape modern agentic coding: a machine queue manages tasks, re-prompts itself, and keeps working past the model’s internal “done,” which is useful for experimentation, porting, benchmarking, and research workflows. But for durable code, the author reports poor outcomes: models tend to over-defend, overfit local failure cases, duplicate logic, and rely on defensive patterns instead of strong invariants, making systems less deterministic and harder to reason about. He frames this as a shift from software as a machine toward software as an organism and says this weakens code comprehension, accountability, and the ability to explain design decisions under pressure. The post highlights that security and competitive pressure already force everyone into this cycle, so teams may need to respond with loops of their own even when they dislike the direction. It also warns about dependency risk: if access to frontier models, budgets, or geopolitical continuity changes, teams may struggle to maintain code that silently assumes machine participation. The piece is not anti-agent; it accepts looping value where output is temporary, mechanical, or well scoped, while rejecting blind reliance for judgment-heavy code. It calls for better tooling and process so agents become constrained collaborators, with clearer contracts for completion and human-readable evolution instead of opaque, machine-native complexity. Overall, it positions the coming years as a tradeoff between velocity and maintainability and urges redesigning engineering practices before the model-driven pattern becomes irreversible.

The essay argues that vitamin D is neither a placebo nor a panacea, framing the strongest evidence as severe deficiency prevention rather than universal disease prevention. It distinguishes observational findings—often showing strong health correlations—from randomized evidence, noting that those early correlations are vulnerable to confounding from lifestyle, sunlight exposure, adiposity, and socioeconomic factors. Biological sections describe a plausible signaling role across many tissues, while also acknowledging that mechanistic findings do not yet prove broad clinical benefit. Three large trials (WHI, VITAL, D-Health) and multiple meta-analyses are reviewed, with most outcomes near null and no consistent mortality or cardiovascular advantage. It highlights methodological limits: low baseline deficiency prevalence, self-supplementation in controls, varying adherence, low doses in early trials, and underpowered subgroup analyses for low baseline vitamin D. The piece concludes that a modest mortality benefit is plausible but uncertain, with some signal that daily dosing may outperform bolus schedules, though this could reflect noise or post hoc pattern selection. It also raises the practical implication that fortification and existing population-level supplementation reduce the marginal impact of trials that mainly raise already adequate levels. The practical takeaway is that supplementing to correct low levels can be reasonable, but expecting large all-cause gains is not supported. Overall, the argument leans toward Bayesian caution: weak evidence plus plausible biology may justify limited use, not universal megadosing.

The project is a desktop app called y that lets users reshape its own interface while they code, with changes made through a protected Modify workflow and then kept or discarded based on a diff review. The app is positioned as a local, chat-first front end for existing coding agents, including Claude Code and OpenAI Codex via their official CLIs, rather than a new model. Its design separates a protected Kernel, which owns authentication, local engine adapters, safety boundaries, terminal access, and rollback state, from a mutable Userland UI that can be modified live. It supports parallel chats with isolated workspaces, visible model and effort settings, and explicit compile/render checks for UI edits to prevent broken flows. The current macOS Apple Silicon release is available on GitHub, with local setup and release commands documented, while generated artifacts are placed in app/dist and not committed. Product analytics are limited to usage health signals and missing-feature reports, with explicit guidance that private prompts and source files should not be collected. The team describes active development toward launch readiness, focused on packaging, authentication, durable local state, and reliability of the Modify self-edit workflow. A key tradeoff is that users gain interface flexibility but no control over protected core logic, preserving local trust boundaries. The discussion in the submission is minimal, with early-stage commentary mostly indicating general approval.

Rhombus version 1.0 is presented as a general-purpose functional language that aims to balance everyday readability with deep extensibility. The project’s goals emphasize conventional, approachable syntax for non-macro users while preserving Racket-like macro and metaprogramming power through an open-compiler model. It is built on Racket, integrating with existing tools such as DrRacket and raco, and is described as closer to Racket than a separate ecosystem, though it adds redesigns including better defaults for functional data structures, a new class system, pervasive pattern matching, and hierarchical namespace organization. A bicameral syntax using shrubbery notation is introduced to keep Lisp-style metaprogramming expressible without forcing S-expression-centric code everywhere. The FAQ frames DSL support as a way to avoid brittle language silos, and argues that compile-time metaprogramming supports documentation, analysis, and tooling rather than only language-hacking. It is positioned for production use, with explicit caveats about a smaller library universe, but with the expectation of long-term stability from Racket’s ecosystem. Example code ranges from early real-world uses such as game logic, HTML parsing, animated evaluation visualizations, and drawing packages to educational and experimental language projects, including a proposed ICFP paper artifact. The post also addresses AI coding assumptions by noting coding agents already perform well with Rhombus and arguing that higher-level DSL support remains valuable.

The post shows a practical NixOS optimization workflow that starts from a default ISO built via nixos-rebuild build-vm and quickly switches to nixos/modules/installer/cd-dvd/iso-image.nix to produce a bootable .iso for non-Nix hosts. It then profiles the image, showing 458 MiB initial size with most bytes concentrated in nix-store.squashfs, and uses nix-build, mount, du, and nix why-depends to trace bloat, including nix, boost, and systemd-related paths. The first pass disables nix.enable and documentation, reducing size to 384 MiB, then removes lingering nix paths by overriding systemd.services.register-nix-paths. A subsequent pass drops programs/ssh effects by disabling the module and stubbing programs.ssh, though this requires care because many modules assume the option exists. Additional reductions target system.extraDependencies and kernel baggage, including removing bootloader redundancy and runtime kernel modules, while accepting lower display options and reduced module-loading flexibility. The image is further reduced by moving /etc and user handling to experimental paths via overlay and services.userborn.enable, which removes some Perl-related weight. The final shown result is about 183 MiB, down from 458 MiB, and the author frames it as a “proof-of-concept” rather than a general-purpose desktop strategy. They note that nix, system-level assumptions, and shared module coupling make deeper minimization difficult. The post closes with caveats: some removals break normal workflows, and the exercise remains open-ended with opportunities for safer, cleaner refactors.

Baidu announced Unlimited-OCR as a model extension of Deepseek-OCR, adding an arXiv paper, a ModelScope release, and reproducible setup guidance. The release targets long-document OCR by combining image-conditioned OCR with inference pathways for single-image and multi-page inputs, including PDF handling via page-image conversion. The team published dependency pinning and environment instructions for Python 3.12.3 with CUDA 12.9, including specific torch, torchvision, and transformer versions and an SGLang serving stack. It also provided example code for direct Hugging Face inference, streaming API requests, custom no-repeat n-gram logit control, and batch processing through infer.py with concurrency options. Comments frame this as a practical attempt to control context growth while preserving document-level consistency during OCR generation. Overall, the post combines a research claim with end-to-end deployment recipes and citation details rather than just model-level description.

The post introduces ffs, a C-based file-search utility that bypasses the VFS and buffered read() path by reading disk blocks directly and parsing filesystem structures in user space, including detached volumes such as .dmg and .iso images without mounting. The author highlights speed behavior, claiming it progressively outperforms ripgrep as data volume grows because it avoids repeated kernel cache overhead, but can be slower on small or already-cached trees. The implementation supports multiple filesystems manually, with ext4 and btrfs handling straightforwardly while APFS support exists but requires disabling SIP on main macOS disks, and it uses manual sync calls to reduce stale-result risk. The tool requires elevated permissions only for raw device nodes, while searching image files can be done without root, and it may miss very recent writes if the kernel still holds dirty cache data, so fsfreeze or detached volumes can improve reliability. It can detect and skip binary files, compile with minimal dependencies, and scale across cores via OpenMP, but only for filesystem types implemented in the project. The post also provides benchmark-style timing on a btrfs-mounted drive showing ffs overtaking ripgrep on 1.5M and 3.25M file sets under equivalent matching settings, while acknowledging ripgrep’s more advanced SIMD matching and file traversal internals.

Germany’s national rail network was broadly halted after a nationwide GSM-R communications outage disrupted coordination between train crews and control centers, forcing staff to hold trains at stations and causing long queues at information desks. Deutsche Bahn said the outage began about two and a half hours before service resumed step by step near 1 a.m., and that it had stabilized the system with an emergency backup while investigating the underlying cause. The operator issued apologies and offered taxi and hotel vouchers where possible, and in some locations left trains available for stranded passengers to wait. Officials and passengers described recurring reliability concerns: travelers reported little real-time clarity, and comments around the event tied this disruption to frequent recent delays in German rail travel. Deutsche Bahn has been rebuilding major routes after years of underinvestment, while the outage contrasted with earlier German-wide stoppages that were mostly weather-related. GSM-R, adopted as a Europe-wide railway standard since 2000, supports both voice and data for train operations, so the failure illustrates the dependency of modern rail systems on shared digital control layers.

The post describes testing Pangram’s signup validation endpoint by POSTing an email to a public API and immediately receiving unsolicited mail from a domain tied to unknown senders, including an encoded HTML message about magnetic domains. The author lists dozens of sender domains and server logs showing repeated connection attempts from multiple mail hosts, with some attempts blocked by reputation DNSBLs and one host successfully accepted and queued, which they interpret as a spam-like validation workflow. They argue this undermines common advice that email checks should avoid heavy-handed pre-validation, because the behavior confirms addresses and can expose recipients to junk even before account ownership is proven. The post also notes Pangram’s transactional mail uses Mailgun, which raises the possibility that a third-party validation layer may be responsible. The core claim is that the validation logic appears to trade false certainty and privacy for anti-fraud intent by causing external traffic that looks like spam delivery. The framing suggests the pattern is either a serious implementation mistake, a compromised integration, or aggressive third-party tooling.

Quaise Energy reported a 100-meter field drill at Central Texas using its millimeter-wave geothermal drilling system, describing it as a significant step beyond prior lab-scale demonstrations that had only reached only centimeters. The company argues the hard granite test is relevant because it matches basement-rock conditions expected in deep geothermal settings, though it notes that commercial geothermal depths remain much greater. The firm is developing the system around a gyrotron and expects a 10x-power upgrade ahead of a planned U.S. pilot plant by around 2028. Its statement contrasts millimeter-wave ablation, which avoids downhole bits, with conventional bits that lose performance in very hard, very hot rock. The result supports the claim that the approach may access superhot formations near 752°F (about 400°C) more directly, but it is still early relative to power-scale deployment. Overall, the update confirms progress in deep-geothermal tooling while leaving key metrics and economics to future milestones.

Dirty Little Zine is a free, browser-only zine maker that arranges an eight-page booklet layout on a single US Letter or A4 sheet and exports print-ready JPG or PDF files at 300 DPI. The app preserves privacy by keeping all work in the browser and avoids uploading content to a server, targeting people who want quick, local publishing workflows. It handles the folding logic automatically, including panel rotation and ordering, so the booklet pages align correctly after one central fold and one cut. The piece frames the format as a practical replacement for heavyweight design tools, with use cases including photo zines, sketchbook compilations, and short written publications. Comments reinforce that niche by treating it as a lightweight, practical alternative to desktop software for small-format print distribution.

The post argues that FromSoftware’s Elden Ring AI is implemented with a stack of parameterized Goals written largely in Havok Script, where each frame updates the top goal and can push sub-goals, with results reported as continue, success, or failure; failures may unwind back to a parent goal. In this design, core AI behavior is driven by callback functions such as Activate, Interrupt, and Update, with Activate selecting actions through weighted random choice, cooldown checks, distances, and random seeds, while sub-goals like approach-and-attack chains implement combat structure. Interrupts let enemies react immediately to events such as damage, item use, burn effects, and spatial triggers by clearing or replacing queued sub-goals, and timeouts provide a safety valve for stuck states. The article notes actor-level state as lightweight arrays plus initialization callbacks, while most behavior execution is animation-driven, with animation events handling timing, hitboxes, effects, and projectiles, and it distinguishes logic scripts from bespoke battle scripts for reuse and maintainability. It also highlights that Havok middleware still underpins animation and physics, with some heavy goals implemented in C++ to balance scripting flexibility and performance. In its conclusion, the author contrasts this approach with FSMs, BTs, and planners, claiming the explicit stack reduces state explosion and avoids costly top-down re-planning, though this applies to the observed architecture rather than modern LLM-style AI. The update section expands the comparison to event-based behavior trees, acknowledging structural overlap but defending the clarity of imperative stack construction as simpler for authors and better suited to large-scale production constraints than verbose tree hier

The post says a long-tenured Google engineer built and released a Google Workspace command-line tool that quickly became popular, reaching the top of Hacker News with thousands of GitHub stars and users. The project was later challenged by legal over the use of Google branding and color schemes in Google-hosted repositories, and the engineer was terminated shortly before an official Workspace CLI announcement. The author frames the decision as cultural resistance to agent-driven change inside the platform team, while noting a complex mix of support and uncertainty from management during the final months. The comments largely question whether the firing was a proportional response, with many readers arguing that trademark and channeling concerns could have been fixed by removing official branding and renaming the repo. Others argue Google has historically tolerated open-source side work, especially 20%-time style initiatives, so the action signals stricter enforcement or internal politics. Several participants call the decision risky for talent retention and product quality, while also acknowledging the need for policy compliance and clear pre-release approval. The thread reflects broader skepticism about whether innovation and governance can coexist in large platform organizations.

A project called Fast Ubu provides a high-performance mirror of UbuWeb’s film and video archive, offering faster loading and search across 3,205 avant-garde films and videos that are free to stream. The mirror presents the entire collection as an independent, unaffiliated effort rather than an official UbuWeb operation. The content is attributed to the original artists, with a clear statement that all works remain their own, and access controls may hide explicit films by default based on user content settings. Users interested in these works can benefit from improved discoverability and speed, while still navigating rights expectations set by the artists and uploader context.

At the 2026 VLSI Symposium, Samsung Electronics’ Semiconductor Research Center presented a paper on a 3D stacked FET with 42 nm gate pitch and triple-stacked nanosheet channels, and it received an 8.29 review score, Best Paper recognition, and inclusion in the symposium technical highlights. The work is presented as the next stage after planar, FinFET, and GAA scaling, arguing that high-density logic now requires better n- and p-transistor placement in addition to stronger electrostatic control. Vertical stacking is used to raise transistor density by placing n-type and p-type devices above each other rather than only side by side, while preserving logic footprint. Three major implementation barriers are identified: maintaining current conduction, ensuring uniform multi-layer channel quality, and preventing electrical coupling between stacked devices. The study addresses current conduction by using triple nanosheet channels in both transistor types, and channel quality by tightly controlled epitaxial growth for uniform, low-defect silicon layers across stacked sheets. The isolation problem is solved with a Middle Dielectric Isolation layer that physically and electrically separates upper and lower devices with controlled thickness and alignment so each gate stack can be formed correctly. The team also claims a 42 nm gate-pitch process, then reports turn-on/off behavior and wafer-level device uniformity for both polarities, signaling manufacturing-oriented progress rather than only a proof of concept. This result was interpreted as a plausible path for next-generation logic because it links density, drive capability, and process uniformity in one architecture. The write-up treats vertical integration as a long-term scaling direction, while discussion around it introduces

California’s AB2047, written as a public-safety measure focused on 3D-printed firearms, has passed the Assembly through Public Safety, Judiciary, Appropriations, Suspense, and then floor passage with 33 amendments, and now sits before the Senate Judiciary and Public Safety committees. The campaign text argues that the bill effectively forces all 3D printers sold or transferred in the state to use a DOJ-certified detection mechanism, a requirement viewed as technically unstable because intent is not inferable from printer data once files are converted to G-code and altered through scaling, splitting, or re-exporting. It also argues the law burdens lawful use because firmware can be modified and detection can be bypassed. Legal objections raised include prior-restraint and compelled-speech concerns, broad sweep into legitimate tools, interstate hardware-listing and constitutional issues, and potential conflicts with existing federal firearms frameworks. The page directs action through committee and legislator contacts, emphasizing constituent phone calls over emails and encouraging personal letters and petitions. It also highlights coverage across tech outlets and maker-network commentary that frames the measure as a precedent-heavy, potentially overbroad policy response. Overall, the article links the policy path to immediate advocacy, arguing this is a moment to influence whether it advances before full Senate action.