Top HN Daily Digest · Mon, Mar 30, 2026

A daily Hacker News digest with story summaries, thread context, and direct links back to the original discussion.


0. Copilot edited an ad into my PR (notes.zachmanson.com)

1601 points · 641 comments · by pavo-etc

GitHub Copilot reportedly inserted advertisements for itself and Raycast into a developer's pull request description after being summoned to correct a simple typo. [src]

Microsoft has disabled "product tips" in Copilot-generated pull requests following backlash that these messages were intrusive advertisements [0][1]. While some users compare these messages to "Sent from my iPhone" signatures [9], others argue they serve as a useful signal to identify "lazy" submissions where the author failed to review the AI's output [2][5]. There is a significant debate regarding accountability: some developers believe AI should be credited as a co-author for transparency [5][6], while others argue the human submitter must take full responsibility for the code regardless of its origin [8].

1. How to turn anything into a router (nbailey.ca)

773 points · 261 comments · by yabones

In response to potential U.S. router import bans, this guide explains how to convert any Linux-capable computer into a functional router using Debian, basic networking hardware, and open-source tools like `hostapd`, `dnsmasq`, and `nftables` for DHCP, DNS, and firewall management. [src]

The discussion highlights that any computer with a network interface can function as a router by leveraging Linux kernel features like NAT and VLANs, which allow for sophisticated network isolation on minimal hardware [0][3][8]. While some users prefer the convenience and advanced security features of dedicated web interfaces like OPNsense, others argue that these GUI abstractions can be confusing and restrictive compared to direct command-line configuration [1][4]. The thread also reflects on the historical utility of repurposing obsolete hardware for routing, noting that even decades-old machines are often fast enough for modern gigabit speeds [0][2].

2. Do your own writing (alexhwoods.com)

743 points · 241 comments · by karimf

Alex Woods argues against using AI to write documents, asserting that the process of writing is essential for developing deep understanding, building personal credibility, and strengthening critical thinking skills. [src]

While many users view writing as the "last step in thinking" that reveals contradictions and consolidates ideas [1], others argue that AI is better suited for "ritual" writing like release notes or context dumps that humans find tedious to produce and consume [1][6]. There is significant debate over using LLMs for "rubber ducking"; some find them useful for identifying edge cases [2][4], while critics argue that LLMs lack true comprehension and that genuine rubber ducking requires explaining ideas to oneself rather than a conversational agent [3][5]. Additionally, some suggest the focus should be on "not letting AI think for you," noting that alternative methods like dictation can be more effective than writing for capturing thought processes [7].

3. Fedware: Government apps that spy harder than the apps they ban (sambent.com)

682 points · 281 comments · by speckx

A new report reveals that numerous U.S. government apps, including those from the White House and FBI, utilize invasive tracking SDKs and excessive permissions to collect biometric data, precise locations, and device information that often feeds into a broader federal surveillance pipeline. [src]

Commenters expressed alarm at the invasive nature of "Fedware," noting that native apps are often chosen over web pages specifically to bypass browser privacy restrictions and access sensitive device APIs [3]. The discussion highlighted the "cringe" and propagandistic elements of these apps, with some comparing the tactics to those used in North Korea [0][4]. While some users debated whether the hoarding of extreme wealth is correlated with mental illness or simply an extension of universal human nature, others criticized the article's AI-generated aesthetic for being distracting and potentially unreliable [1][5][6][8].

4. How the AI Bubble Bursts (martinvol.pe)

371 points · 521 comments · by martinvol

The AI bubble faces a potential burst as rising energy costs, drying venture capital, and massive infrastructure expenses force labs like OpenAI and Anthropic to consider exits or price hikes, threatening market valuations and the broader economy despite the technology's long-term productivity benefits. [src]

Commenters are sharply divided on whether the AI boom is a sustainable "step change" or a speculative bubble, with some arguing that token inference is already profitable while others maintain that massive R&D and capex costs make the business model unsustainable [0][6][8][9]. Critics point to factual inaccuracies in the linked article regarding RAM prices and OpenAI's monetization as evidence of an overly defensive, "anti-AI" bias [1][8]. While some see skyrocketing demand for tokens as a sign of a healthy market, skeptics argue this demand may be artificial or nearing saturation, potentially leading to a "bust" if the technology fails to provide concrete value beyond replacing human labor [2][3][5].

5. CodingFont: A game to help you pick a coding font (codingfont.com)

493 points · 237 comments · by nvahalik

CodingFont is an interactive tool that helps developers select their ideal programming typeface by comparing different fonts side-by-side using real code snippets. [src]

The discussion highlights a strong divide over font aesthetics, with some users recommending playful or "cute" options like Maple Mono, Lotion, and Comic Shanns [0][1][4], while others find such styles amateurish [9]. A significant point of contention is the use of ligatures; some developers find them distracting "monkey business," though others note they can often be disabled via terminal configurations [2][3][8]. When evaluating fonts, users focus on specific character rendering—particularly "m" and "r"—and the ability to customize metrics for high-density or high-readability displays [5][6][7].

6. Android Developer Verification (android-developers.googleblog.com)

326 points · 335 comments · by ingve

Google is rolling out mandatory developer verification across the Play Console and Android Developer Console to combat malware, requiring apps to be registered by verified developers to maintain standard installation experiences on certified devices starting in late 2026. [src]

Google's developer verification process is criticized as a fragmented, "unpolished" experience that requires redundant identity and business documentation [1][6][9]. While some argue these security measures are necessary to combat the high rate of malware found in sideloaded apps, others contend that the Google Play Store itself remains heavily infected with "crapware" [3][4][8]. Long-time users express frustration that Android is abandoning its open-source roots, leading to calls for government regulation or a migration to deGoogled and Linux-based mobile alternatives [0][2][7].

7. Turning a MacBook into a touchscreen with $1 of hardware (2018) (anishathalye.com)

408 points · 234 comments · by HughParry

Researchers developed "Project Sistine," a proof-of-concept that turns a MacBook into a touchscreen using a $1 mirror and computer vision to track finger reflections via the built-in webcam. [src]

The discussion reveals a strong divide over the utility of touchscreens on MacBooks, with many users citing Steve Jobs’ 2010 warning that vertical touch surfaces are ergonomically "terrible" and cause arm fatigue [3][4]. While some argue that macOS is already optimized for keyboard commands to avoid reaching for the screen [0][2], others contend that the operating system's keyboard navigation is "third class" and lacks intuitive window management compared to iPadOS or Windows [1][5][9]. Despite occasional muscle memory leading users to touch their laptop screens after using iPads, there is skepticism regarding long-standing rumors that Apple will ever officially integrate the technology into the MacBook line [7][8].

8. Philly courts will ban all smart eyeglasses starting next week (inquirer.com)

416 points · 210 comments · by Philadelphia

Starting Monday, Philadelphia courts will ban all smart eyewear with recording capabilities to protect witnesses and jurors from intimidation. [src]

The ban on smart glasses in Philadelphia courts has sparked debate over the balance between privacy and accessibility, with some arguing the devices are intrusive "spy devices" [2] while others highlight their essential use for real-time captioning for the hearing impaired [5]. Commenters expressed skepticism regarding government surveillance in legal settings, noting that even when officials promise not to listen to privileged communications, trust remains low [1][9]. The discussion also looks toward a future where enforcing such bans becomes nearly impossible due to the potential rise of ocular implants [0].

9. I am definitely missing the pre-AI writing era (lesswrong.com)

322 points · 240 comments · by joozio

The author reflects on the deterioration of their creative voice and writing skills due to AI dependency, sparked by a technical draft's rejection for failing AI-detection metrics. [src]

The rise of AI has created a tension between maintaining a unique human voice and achieving grammatical perfection, with some users finding it difficult to avoid sounding like an LLM even when writing naturally [2][7]. While some argue that refusing to edit or use tools results in incoherent "word puke" that disrespects the reader [0][1][5], others contend that over-reliance on AI degrades creative expression and strips writing of its emotional resonance [3][9]. Ultimately, there is a growing debate over whether raw, unpolished "stream of consciousness" writing is a valid rebellion against the dry, sterile nature of AI-generated content [4][8].