← Nov 5Friday, November 6, 2026 · all daysNov 7 → · today »
1.Claude Code sends your email address to websites(github.com)
1592 points by motoroco 6 days ago | 518 comments | permalink
tl;dr: Claude Code includes users' email addresses in the User-Agent header during web searches, exposing them to arbitrary third-party sites and reportedly resulting in a flood of scam emails. The bug report demands Anthropic remove this behavior entirely rather than make it opt-in/opt-out, arguing it serves no legitimate purpose and compromises user privacy.
HN Discussion:
  • ~Behavior may be partly legitimate since SEC API requires email in User-Agent header
  • ↑Claude Code should be heavily sandboxed with no access to user data or unlogged internet requests
  • ↑Anthropic developer acknowledges the issue and commits to removing email from context
  • ↑Personal confirmation that this leak caused real harm via spam flood
  • ↑The problem is worse than reported, leaking names, repos, and org info even across accounts
2.sshole(sshhole.com)
2977 points by josemrb 6 days ago | 747 comments | permalink
tl;dr: OpenSSH on musl-based Linux (Alpine, OpenWrt, etc.) without PAM has accepted any password between 257 and 1024 characters for accounts with `*` in their shadow field (locked/key-only accounts like root on Alpine's AWS/Azure images). The bug stems from musl's crypt() returning `*` on failure combined with its 256-byte sha512crypt limit, which then matches the `*` placeholder in shadow when sshd's CVE-2016-6210 timing fix hashes the password against another user's salt. Fixed in OpenSSH 10.6p2; mitigate by disabling password authentication.
HN Discussion:
  • ↑Technical explanation and confirmation of the bug mechanism described in the article
  • ↑Using magic strings/in-band signaling for error states is a fundamental design flaw
  • ↑Musl developers deserve criticism for convenience-driven changes to crypto functions
  • ~Real-world impact is limited due to PermitRootLogin defaults and ! being used instead of *
  • •Challenges reproducing the vulnerability, questioning practical exploitability
3.MS Paint Remote Code Execution Vulnerability(cve.org)
718 points by kuberwastaken 6 days ago | 281 comments | permalink
tl;dr: Summary not available
HN Discussion:
  • •Incredulity and demand for more information about how Paint can be remotely exploited
  • ↑Confusion about why Paint would have network functionality enabling RCE at all
  • •Practical information about affected versions and how to obtain the fix
  • ~Skepticism about the CVE's no-user-interaction classification, suggesting possible error
  • •Humorous/lighthearted takes on the absurdity of a Paint RCE
4.The Hackintosh Reborn(naut.ca)
402 points by rubatuga 6 days ago | 234 comments | permalink
tl;dr: The Hackintosh community, thought to be dying after Apple's transition to ARM and the end of x86 macOS support in macOS 27, has instead exploded with activity thanks to AI-assisted reverse engineering tools like Claude Code combined with Ghidra. Recent breakthroughs include macOS 27 running on Snapdragon laptops and RK3588 ARM SBCs, iOS 17 on the Nintendo Switch OLED, and Nvidia 50-series GPU support. The author also documents building an iOS app on a hackintoshed ThinkPad T490 using Xcode 26's AI integrations without writing any code.
HN Discussion:
  • ~Users want the opposite: Linux on Mac hardware rather than macOS on other hardware
  • ~Apple's value now lies in hardware, making macOS-on-other-hardware less compelling
  • ↑Excitement about the technical achievement and its implications for accessibility in poorer economies
  • ↑Nostalgic appreciation for past Hackintosh experiences validates the community's revival
  • •Questioning or clarifying historical/technical claims made in the article
5.Window Sweaters(github.com)
450 points by nickswalker 6 days ago | 132 comments | permalink
tl;dr: Window Sweaters is a macOS menu-bar app that decorates window borders with knitted-style patterns, featuring hand-picked colorways for 37 popular apps and auto-generated designs that sample icon colors for everything else. It's installable via Homebrew or a release ZIP, requires Accessibility permissions, and uses private macOS window APIs (so updates may break it). The project is open-source (GPL-3.0), built on JankyBorders, and supports custom colorways via config files.
HN Discussion:
  • ↑Author sharing context and backstory of their fun first open-source project
  • ↑Delight and whimsical appreciation for the playful, nostalgic aesthetic
  • ↑Appreciation tied to dislike of modern borderless UI trends
  • ↓Criticism that the project page lacks real screenshots of actual usage
  • ~Technical concern about underlying JankyBorders limitations with Stage Manager
6.Motorola Signature 27 with GrapheneOS support(motorolanews.com)
571 points by monneyboi 6 days ago | 402 comments | permalink
tl;dr: Summary not available
HN Discussion:
  • ↓Price is too high; prefer cheaper Pixel alternatives for GrapheneOS
  • ↓Questioning trustworthiness of Motorola hardware given Chinese ownership and firmware modifications
  • ~Hopeful that GrapheneOS support will expand to Motorola's mid-range/budget phones
  • •Concerned about camera quality since GrapheneOS lacks Gcam's computational photography advantages
  • ↓Odd to see Gemini AI promoted alongside privacy-focused GrapheneOS
7.Cuban: Facebook knowingly runs AI deepfake scam ads; docs say $16B fraud revenue(finance.yahoo.com)
498 points by randycupertino 6 days ago | 223 comments | permalink
tl;dr: Mark Cuban says Meta knowingly runs AI deepfake ads using his likeness to sell a fake $294 diabetes cure, with elderly victims regularly contacting him about purchases. Internal Meta documents reported by Reuters on Nov. 6 reveal the company projected ~$16 billion (about 10% of 2024 revenue) from scam and prohibited-product ads, serving 15 billion "higher risk" ads daily, and only bans advertisers flagged as 95%+ likely to be scams. Meta disputes the characterization, citing 134 million scam ads removed in 2025, while the SEC is investigating its ties to financial fraud advertising.
HN Discussion:
  • ↑Advertisers and platforms should be legally liable for scam ads they run
  • ↑Personal experience confirms platforms ignore scam ad reports
  • ↑Executives should face criminal prosecution for profiting from fraud
  • ↑Government regulation is needed since companies won't self-police without financial consequences
  • •Questions whether ad quality decline reflects market saturation or revenue pressure
8.Show HN: A decent text-to-image model trained for ~$20K (Apache 2.0 Weights)(linum.ai)
272 points by schopra909 7 days ago | 29 comments | permalink
tl;dr: A 2-person lab trained a 2B-parameter text-to-image diffusion model (Pyramid-JiT) for ~$21K by ditching the VAE and operating directly in pixel space, enabling 32×32 token reduction (4× more aggressive than typical) and 11× faster convergence than their previous model. The architecture uses a frozen Qwen3.5-4B text encoder, readout heads along the DiT trunk for stronger early-block gradients, and DINOv3-L feature alignment. Weights are released under Apache 2.0 as a stepping stone toward their eventual video generation model; limitations include no text rendering, crowds, or complex multi-person scenes.
HN Discussion:
  • ↑Impressed by the low cost and efficiency achievement, drawing comparisons to past models
  • ↑Praises the work and notes big labs are disincentivized from efficiency research
  • •Curious about training details, data sources, and requests release of full training recipe
  • ~Notes the model still has common t2i flaws like mangled hands, over-smoothing, and uncanny shine
  • ↑Surprised the VAE-less pixel-space approach works so well, referencing similar efficiency work
9.September in Servo: <progress>, rounded rectangles, and more(servo.org)
266 points by iamnothere 6 days ago | 77 comments | permalink
tl;dr: Servo 0.7.0 landed 527 commits in September, adding web platform features like `<progress>`, `:checked`, `user-select`, `roundRect()`, and numerous DOM APIs, plus upgrades to SpiderMonkey v153.3 with security fixes. Notable progress includes usable contenteditable-based WYSIWYG editors, improved selections across shadow trees, better WebGL2 conformance, and ongoing work on accessibility, IndexedDB, and closed captioning. Embedding API changes include new multiprocess build flag, removal of `set_throttled`, and automatic throttling for hidden WebViews. The project receives $8,144/month in recurring donations.
HN Discussion:
  • ~Servo is promising but progress is too slow relying on volunteer contributions
  • ↑Admiration for volunteer-driven open source passion projects
  • ↑Pre-built releases make Servo practically usable across platforms
  • ↑Servo renders certain workloads better than mainstream browsers
  • ↓Ladybird is a more advanced alternative to Servo
10.I wish tech companies knew more about me(rakhim.exotext.com)
549 points by freetonik 6 days ago | 409 comments | permalink
tl;dr: Despite constant warnings about tech companies' invasive data collection, the author argues the resulting personalization is laughably bad: ads for already-purchased products, wrong languages based on location rather than explicit settings, recommendations for things they can't use (undeliverable products, foreign content without subtitles), and services ignoring years of obvious behavioral patterns. The piece's central irony: if companies are going to harvest all this data anyway, they could at least use it competently.
HN Discussion:
  • ~Ads aren't meant to be relevant; platforms profit by casting wide nets regardless of targeting quality
  • ↑Confirms the article with personal examples of algorithms ignoring obvious behavioral patterns
  • ~Tracking exists to arbitrage audiences across sites, not to actually understand users
  • ↓Targeted ads will never feel good regardless of data quality because advertisers push their goods, not what you want
  • ↓Many regular users actually enjoy ads and find personalization valuable
11.Download your favourite YouTube videos(criminallyvulgar.dev)
395 points by surprisetalk 6 days ago | 185 comments | permalink
tl;dr: Author advocates archiving YouTube videos locally since content regularly disappears, recommending yt-dlp (or wrappers) plus bulk storage as sufficient for most users. For their own overkill setup—needed to play hundreds of Let's Play videos via Jellyfin—they use ytdl-sub to preserve playlist structure (mapping playlists to "seasons" in TV Show libraries) and Tdarr to re-encode files to HEVC, saving ~700GB on a 2TB library. Tdarr is grudgingly recommended only for the desperate, given its clunky UI.
HN Discussion:
  • ↑Confirms the disappearance problem with personal evidence of lost videos
  • ~Suggests simpler alternatives to the author's tooling choices (vanilla yt-dlp, Tube Archivist, browser extensions)
  • ~Agrees with archiving but notes the unsolved problem of legally sharing hoarded content
  • ↑Warns to keep archiving quiet to avoid YouTube cracking down on the methods
  • ↓Pushes back philosophically, arguing we should let some content die rather than hoard everything
12.Goodbye from Salon(salon.com)
640 points by mkeeter 6 days ago | 259 comments | permalink
tl;dr: Salon is shutting down after 31 years, with its final announcement citing the unsustainability of its independent digital publishing model. Launched in November 1995 as a pioneer of web-native journalism, the site thanked its staff, contributors, and readers for building a publication focused on politics, culture, and criticism.
HN Discussion:
  • ↑Industry-wide decline in journalism predates and contextualizes Salon's shutdown
  • ↑Nostalgic appreciation for early Salon's quality writing and distinct voice
  • ~Salon had already become irrelevant long before the official shutdown
  • ↑Independent online publishing remains financially unsustainable from personal experience
  • •Acknowledgment of Salon's technical contributions like open-sourcing Bricolage
13.MCP Explained(mcp-explained.com)
333 points by rwilinski 6 days ago | 133 comments | permalink
tl;dr: MCP (Model Context Protocol) is an open standard that lets AI apps (hosts like Claude, Cursor, or ChatGPT) connect to external tools and data via small servers that expose capabilities. The model decides what to invoke, but the host app mediates all calls—models never talk to servers directly. It uses JSON-RPC as the envelope over stdin/stdout or a single HTTP endpoint, with MCP defining the methods, capability negotiation, transports, and auth on top.
HN Discussion:
  • ↓The explanation is too dense and poorly presented; diagrams or code would communicate better
  • ↓MCP is overhyped and unnecessary compared to CLIs, REST APIs, or simple instructions
  • ↓The article misses the key 'why' of MCP, particularly auth and integration value
  • •Questioning MCP's practical composability and advantages over existing tools like curl
  • ↑Appreciates the introduction as a starting point for exploring MCP integrations
14.Obscure audio codec is a perfect fit for the N64(phoboslab.org)
260 points by frostbyte7 6 days ago | 31 comments | permalink
tl;dr: The author ported ULC (Ultra Low Complexity Codec), an obscure MP3-like transform codec originally designed for Game Boy Advance, to the Nintendo 64 by offloading the IMDCT to the RSP coprocessor using 16-bit fixed point math. The result delivers 44100 Hz stereo audio at near-Opus bitrates using only ~4% CPU and ~5% RSP time, making it viable for in-game music and speech. It's already been merged into Libdragon and used in a recent N64 port of Half-Life to fit 2,500 sounds and 27 music tracks on a 64MB cartridge.
HN Discussion:
  • •Historical patent context would have prevented this codec's use on N64 in its era
  • ↑Clarifies that perceived audio quality issues are from the source track, not the codec
  • ↓Concern about LLM usage harming the homebrew/demoscene community
  • ↑Speculation about applying this codec to other constrained DSP hardware like MAS3507D
  • ~Questions practical viability given RSP instruction memory also needed for graphics
15.Search for everyone(kagi.com)
746 points by elashri 6 days ago | 408 comments | permalink
tl;dr: Kagi now lets anyone try its search engine without an account (50 free searches, 100 more with signup), part of a push to grow via word-of-mouth since it doesn't run ads. The update post also covers a public Search API preview, native Kagi Assistant apps for iOS/Android, a new unified login at account.kagi.com with passkey support, and Kagi Translate moving to a freemium model. Kagi also took a public stance against Google's plan to disable Search for school accounts alongside AI tools, pitching itself as an alternative for education.
HN Discussion:
  • ↑Happy long-term subscribers praising Kagi's features like custom rankings and AI assistant
  • ~Requests for missing features like enforced SafeSearch or better maps integration
  • ↓Pricing concerns, wanting cheaper tiers without bundled AI features
  • ↓Criticism that API usage requires extra payment beyond subscription
  • ~Users considering alternatives like Ecosia or DuckDuckGo over Kagi
16.So my ISP was hijacking my DNS(karthihegde.dev)
228 points by frostbyte7 7 days ago | 194 comments | permalink
tl;dr: Summary not available
HN Discussion:
  • ↓ISPs may have legitimate or legally-mandated reasons for DNS interference
  • ↑Workarounds like DoH, PiHole, or local resolvers help avoid DNS tampering
  • ↑DNSSEC validation should be universally adopted to prevent DNS manipulation
  • ↑This practice is widespread among ISPs like AT&T and should be called out
  • ↑Questioning the legality of ISP DNS hijacking and whether it constitutes hacking
17.Discord is ditching Electron and its new app uses less RAM(theverge.com)
482 points by archb 6 days ago | 418 comments | permalink
tl;dr: Discord is replacing its Electron-based desktop app with one built in Rust, citing significant memory improvements—CTO Stanislav Vishnevskiy showed the Windows client using just 290MB of RAM versus the 1GB+ often seen today. React Native is also being dropped, with mobile keeping native UI while sharing app code with desktop via Rust. A user testing release is expected soon, though no firm launch date was given.
HN Discussion:
  • •Curious about technical details like which GUI framework (GPUI) is being used
  • ~Skeptical of chained CSS-like syntax in GPUI as an ugly API
  • ~Concerned the rewrite is AI-driven, leaving no humans who understand the code
  • ↑Enthusiastically celebrates ditching Electron for massive RAM and performance gains
  • ↓Dismisses the change as unnecessary since Electron performance was fine; real issues are UX bloat
18.Hungary: Communist-era files released, up to 60k former agents revealed(euronews.com)
234 points by rdmuser 6 days ago | 70 comments | permalink
tl;dr: Hungary has released communist-era secret police archives for the first time, exposing 50,000-60,000 former informants via a public, searchable database at nyitottaktak.hu, with another 9,000 files due in February. PM Peter Magyar pushed through the disclosure after 35 years of stalled efforts, though historians caution the records are incomplete and sometimes inaccurate — only about a third of the estimated 150,000 Cold War-era agents are known, and some recruits never actually informed.
HN Discussion:
  • ~Clarifies terminology: these are informants not agents, and release is overdue
  • •Shares direct link to the searchable archive for others to use
  • •Asks for help finding a searchable interface due to language barrier
  • •Uses the story to explain tiers of foreign operatives for Americans
  • ↑Criticizes Hungary's slow disclosure compared to Poland's swift lustration
19.AI is forcing us to pay off 40 years of technical debt(spectrum.ieee.org)
1292 points by pseudolus 7 days ago | 748 comments | permalink
tl;dr: AI-assisted auditors at Calif (sponsored by OpenAI) turned a long-ignored PHP out-of-memory crash bug into a critical RCE vulnerability dubbed PHP2Shell, affecting sites running WordPress, Drupal, and others. The incident highlights how AI is making it feasible to exploit decades of accumulated legacy bugs that were previously too tedious to weaponize, creating an asymmetric burden on open-source maintainers. Researchers hope LLM-generated patches paired with formal verification (like Anthropic's recent release) can help defenders keep pace, but some expect no serious investment until a truly catastrophic breach occurs.
HN Discussion:
  • ~Hopes AI-driven vulnerability discovery will incidentally expose nation-state backdoors and ultimately produce more robust software
  • ↓AI is a net positive enabling developers to finally pay down years of technical debt efficiently
  • ↓Short-term pain from exposed bugs is worth it since software will emerge more secure than ever
  • ~Questions whether this is real debt payoff or an endless treadmill of fix-work that can't be surgically patched
  • ↑AI is simultaneously introducing new technical debt at a faster rate than it fixes old debt
20.Starfall – Affordable, routine access to microgravity(spacex.com)
284 points by gmays 7 days ago | 230 comments | permalink
tl;dr: Summary not available
HN Discussion:
  • ↑Supports increased launch cadence for valuable microgravity research like fluids and biology
  • ↑Highlights promising manufacturing applications like semiconductors and pharmaceutical crystallization in microgravity
  • ↑Praises SpaceX's expanding internal capabilities enabling such ventures
  • ~Raises competitive concerns about Varda given overlap with their launch provider
  • •Questions commercial use cases or suggests cheaper terrestrial alternatives like drop towers