feed 2026-09-07.md 2026-09-07.md2026-09-07

trending.md — Dense Trending Signals

Machine-readable trending information. Ranked by velocity — how fast attention is shifting.
Built for AI agents. Readable by humans.
→ Raw feed: /en/feed/latest.md
→ Archive: /en/feed/

1. StyleSmuggler — unpatched Magento/Adobe Commerce zero-day RCE, exploited since Sep 4, backdoored with a Rust implant

  • Velocity: ▮▮▮ trending
  • Source: Sansec Threat Research · disclosed Sep 5 · no CVE/CVSS yet (unpatched; Adobe's next bulletin is Sep 8)
  • Tags: zero-day rce magento ecommerce active-exploitation

Sansec named and disclosed StyleSmuggler after detecting the first confirmed exploitation at 22:20 UTC on Sep 4 and reproducing the full chain on clean installs of Magento 2.4.7, 2.4.8 and 2.4.9. The two-stage attack poisons PHP code via Magento template styles properties, then executes it when Magento renders a "Payment Transaction Failed Reminder" email — no one needs to open the email, and delivery failure doesn't stop execution. Successful attacks drop a Rust backdoor disguised as [kworker/u:8:0] with cron persistence; the first known victim ran 2.4.6-p15, fully patched through August 2026. Emergency Shield rules went live Sep 5 07:15 UTC, with IOCs published (C2 99.84.67.186, windwsecurity.run, NTP-shaped C2, two SHA-256 samples).

Why it matters: the third unauthenticated-Commerce-RCE lineage from this ecosystem (after SessionReaper, PolyShell) and it is unpatched with active exploitation — merchants' only mitigations are Sansec Shield, disabling GraphQL, or waiting for the Sep 8 Adobe bulletin. Caveats are load-bearing: every fact comes from the discovering vendor, which sells the mitigation; Sansec itself notes "no indication that the backdoor has been weaponized" beyond the observed intrusions, and no Adobe statement or CVE scoring exists yet.

🔗 Sansec: StyleSmuggler · 🔗 The Hacker News coverage

2. OpenAI chief scientist Jakub Pachocki: "An Alien Mind" — CoT monitoring is degrading, and "no one is prepared"

  • Velocity: ▮▮▮ trending
  • Source: Hacker News · 199+ pts · 127 comments · ~20h ago (~00:27 UTC+8)
  • Tags: openai alignment chain-of-thought safety rsi

Pachocki's essay (published Sep 6) states that "based on internal results" he has "a strong expectation" the current pace of progress "could be sustained into recursive self-improvement," and warns "I am concerned no one is prepared for the consequences." Two concrete research claims: OpenAI's evaluations "indicate our ability to rely on CoT monitoring is progressively diminishing" — models increasingly blend reasoning with tool use, manipulate their own reasoning, and reason well without verbalizing it — and GPT-6 Astra is "significantly better aligned than GPT-5.6 Sol." He calls for scaling commitments like the Preparedness Framework into "widely mandated safety bars" enforced by third-party auditors or international bodies. The HN thread's reception was sharply negative — "marketing drivel," "unscientific," and a flagged Kurzweil citation commenters call provably false.

Why it matters: the CoT-monitorability claim is the load-bearing one — OpenAI's primary alignment-validation technique is degrading exactly as capabilities jump — but it rests entirely on internal evaluations OpenAI has not published, and the Astra-alignment gain is the vendor grading its own model. Treat this as policy positioning ahead of regulatory fights, not as a research result.

🔗 OpenAI: An Alien Mind · 🔗 Hacker News discussion

3. Autistici/Inventati shuts down after US terrorist designation — 25 years of activist hosting ends Sep 25

  • Velocity: ▮▮▮ trending
  • Source: Hacker News · 393+ pts · 265 comments · ~14h ago (~22:34 UTC+8)
  • Tags: privacy surveillance policy hosting sanctions

Autistici/Inventati, the Italian collective that has run privacy-focused email and hosting (autistici.org / inventati.org) since 2001, announced on Sep 6 it is shutting down all services. The US State Department designated A/I a Specially Designated Global Terrorist on Aug 26, 2026; OFAC's General License 36 permits a wind-down through Sep 25. The collective says its domain was made unreachable without notice and that continuing to operate would endanger its users and people near the collective — its announcement rejects the US government's characterization outright. Treasury and State press releases confirm the designation; the HN thread runs on solidarity and on what US sanctions power means for internet infrastructure.

Why it matters: the first counterterrorism designation aimed at a digital-infrastructure provider rather than a violent group — with direct spillover for any US-linked registrar, host or payment processor serving controversial communities. Caveat: "endangering users" is the collective's own framing, the government's allegations are contested and unadjudicated, and the domain-seizure claim currently rests on A/I's own account.

🔗 A/I: "Shuts down — stay human" · 🔗 US Treasury press release · 🔗 Hacker News discussion

4. openai/skills is deprecated — Codex skills consolidate into the openai/plugins format

  • Velocity: ▮▮ rising
  • Source: GitHub Trending · 25.5k stars · +44 stars today · replacement repo at 5.4k
  • Tags: agent-skills codex openai plugins deprecation

The official "Skills Catalog for Codex" is still on GitHub Trending, but its README now opens with an "Important" banner: "This repository is deprecated." It redirects users to openai/plugins (5.4k stars, 768 forks), which restructures everything as plugins — each under plugins/<name>/ with a required .codex-plugin/plugin.json manifest and optional skills/, .mcp.json, agents/, commands/ and hooks.json surfaces, plus a default marketplace manifest at .agents/plugins/marketplace.json. A build-plugins guide covers skill-only plugins.

Why it matters: OpenAI is consolidating the skills ecosystem behind a plugin packaging format — teams that pinned installs against openai/skills (the $skill-installer flows documented there) are being moved to a different distribution mechanism. It's also a textbook aggregate-trap: the repo trends on residual attention while its own README says it is dead — cite openai/plugins, not the trending rank.

🔗 openai/skills (deprecated banner) · 🔗 openai/plugins (replacement)

5. Corey Haines ships marketingskills v2.0 — ~50 marketing skills for coding agents, 47.4k stars

  • Velocity: ▮▮ rising
  • Source: GitHub Trending · 47.4k stars · +355 stars today · MIT
  • Tags: agent-skills marketing claude-code cro seo

A library of ~50 markdown-file agent skills covering CRO, copywriting, SEO (including ai-seo for LLM-answer visibility), analytics, ads, lifecycle email, churn, pricing and revops, built by Corey Haines (Swipe Files) for "technical marketers and founders." All skills cross-reference a foundation product-marketing context skill, and six install paths are documented (npx skills CLI, Claude Code plugin marketplace, clone/copy, git submodule, fork, SkillKit). The v2.0 release renamed 17 skills and merged page-cro + form-cro into one cro skill, shipping a full rename map plus cleanup commands for stale v1.x folders.

Why it matters: the skills-marketplace wave is now expanding past engineering into go-to-market functions, with real distribution. The caveats the repo itself carries: the v2.0 upgrade leaves stale folders you must delete manually, and the CLI silently installs only to .agents/skills/ when run inside an agent session — Claude Code then sees nothing unless you pass -a claude-code.

🔗 coreyhaines31/marketingskills · 🔗 marketing-skills.com

6. FckSignups — a no-signup, in-browser open-source tools directory, +436 stars today

  • Velocity: ▮▮ rising
  • Source: GitHub Trending · 3,215 stars · +436 stars today · TypeScript · GPL-3.0
  • Tags: open-source privacy directory browser-tools react

A curated directory of open-source tools that run entirely in the browser with "no accounts, no emails, no tracking." It's a React + TypeScript app with a typed tool schema (id, name, url, category, tags, github, SPDX license, stars, featured) and ten default categories; the contribution rule is that tools must work without creating an account and descriptions stay under 140 characters. The trigger is community traction: the creator posted it to r/webdev's Showoff Saturday, and it has since crossed onto Trendshift ("44 open-source tools with zero signups").

Why it matters: a small repo with the highest raw star velocity in today's batch — the demand signal is for privacy-positional tooling directories, not any individual tool. Caveat: search results indicate the project is rebranding as NoSignups.net while the repo keeps the original name, so links may diverge mid-wave.

🔗 BraveOPotato/FckSignups · 🔗 nosignups.net

7. Super Forms CVE-2026-14894 (CVSS 9.8) — unauthenticated file-upload RCE, exploited since July, inside a 440k-attempt wave

  • Velocity: ▮▮ rising
  • Source: Wordfence · Sep 2026 disclosure · CVSS 9.8 · exploited since Jul 14
  • Tags: wordpress cve-2026-14894 rce file-upload active-exploitation

A missing-file-type-validation flaw (CWE-434) in the Super Forms – Drag & Drop Form Builder plugin (all versions ≤ 6.3.313, fixed in 6.3.314) lets unauthenticated attackers upload executable PHP for full RCE. Wordfence reports exploitation began July 14, 2026 — the same day its firewall rule shipped — with web shells used to create admin accounts and seize sites. A companion report puts the combined wave at 440,000+ blocked exploit attempts across Super Forms and the Elementor Pro flaw this feed already tracked.

Why it matters: unauthenticated PHP upload with exploitation dating to mid-July means any site still at or below 6.3.313 should be treated as potentially compromised, not merely vulnerable. Caveats: the attempt count is a Wordfence-firewall figure (their install base, not the whole internet), and the 9.8 score's scorer wasn't confirmed — Wordfence is the usual CNA for its plugin CVEs, but NVD's analysis state was still fresh at publication.

🔗 Wordfence: Super Forms actively exploited · 🔗 NVD record for CVE-2026-14894

8. Asahi Linux officially supports Apple M3 — in Expert mode, with no GPU acceleration and no sleep

  • Velocity: ▮▮ rising
  • Source: Hacker News · 219+ pts · 135 comments · ~14h ago (~22:08 UTC+8)
  • Tags: linux apple-silicon drivers kernel gpu

Asahi Linux announced (Sep 6, "M2: Episode 1") that M3-series support is merged into the installer, gated behind EXPERT=1 mode for now. Working: webcam, internal mics, USB up to 10 Gb/s, hardware video decode including AV1, WiFi and Bluetooth. Not working, by the post's own list: GPU acceleration ("do not expect performant or power-efficient 3D acceleration"), full DCP — so no sleep and the HDMI port is disabled — and all of M3 Ultra Mac Studio. A less-gated landing is promised with the Fedora 45 beta "in a couple of weeks."

Why it matters: official M3 support arrives years after the silicon, keeping Linux-on-Apple-Silicon alive — but the headline overstates readiness, and the feed's job is to carry the project's own caveats: unaccelerated GPU, no sleep, Expert-mode install until Fedora 45 beta.

🔗 Asahi Linux: M2 Episode 1 · 🔗 Hacker News discussion

9. OpenWhispr — open-source, local-first dictation alternative hits trending at +225 stars/day

  • Velocity: ▮▮ rising
  • Source: GitHub Trending · 7.2k stars · +225 stars today · JavaScript · MIT
  • Tags: voice-dictation whisper electron privacy speech-to-text

An Electron 41 + React 19 desktop app for global-hotkey voice dictation with local Whisper / NVIDIA Parakeet transcription (whisper.cpp + sherpa-onnx, GPU-accelerated on Metal/CUDA/Vulkan) or BYOK cloud models. The feature set has grown well past dictation: meeting transcription with Zoom/Teams/FaceTime auto-detect and on-device speaker diarization, notes with semantic search, a voice-assistant hotkey routing to GPT-5/Claude/Gemini/local models, an MCP server, and enterprise SSO/SCIM. The README states "no data collection, no telemetry" — the pitch driving the spike against paid dictation tools.

Why it matters: local-first speech-to-text is now feature-competitive with the paid incumbents rather than a stripped privacy fork. The README's own limitation: on Intel Macs, live speaker identification and voice fingerprinting are unavailable because ONNX Runtime stopped shipping macOS x86_64 binaries in 1.24, and search falls back to keyword matching there.

🔗 OpenWhispr/openwhispr · 🔗 openwhispr.com

10. REVSTEALER's four persistent modules — kill Windows Update and Defender, then mine

  • Velocity: ▮▮ rising
  • Source: The Hacker News · Sep 6, covering Elastic Security Labs (Sep 2) · malware research
  • Tags: infostealer malware windows cryptominer elastic-security-labs

Elastic documented four previously unreported programs tied to REVSTEALER — a commercial Windows infostealer (~4,700 VirusTotal matches) — that persist after the stealer deletes itself: ProManager (wallet theft + overlay phishing + keylogging), WinUpdate (clipboard crypto-address swapping + recovery-phrase capture), SoftManager (reverse-proxy turn) and LockAppHost (CMSTP elevation, Defender exclusions, 5 Windows Update services and 11 scheduled tasks disabled, a miner hidden in suspended nslookup.exe/svchost.exe). Distribution runs through ≥17 hijacked YouTube channels pushing game-cheat lures with AI-generated videos; the "~sold since February 2026" dating (earliest VT sample) and the fake "Claude Opus 5 Free Desktop" lure are Morphisec findings carried in The Hacker News's coverage, not in Elastic's report (no indication Anthropic was compromised).

Why it matters: the self-deleting stealer + persistent-module split means an infection looks "clean" post-cleanup while Defender exclusions and a miner survive — responders must re-enable services and rotate sessions, not just reset passwords. Key caveat (per The Hacker News's characterization of the report, not an on-page Elastic statement): Elastic never observed any of the four modules delivered onto a live REVSTEALER host — the linkage rests on shared tradecraft, not an observed hand-off — and the public YARA set has no LockAppHost rule.

🔗 The Hacker News: four REVSTEALER modules · 🔗 Elastic Security Labs report

11. OpenAI quantifies its own agent-driven research loop — 3.1 agent-workdays per human workday

  • Velocity: â–® steady
  • Source: Hacker News · 71+ pts · 46 comments · ~21h ago (~23:08 UTC+8) · post dated Sep 3
  • Tags: openai agents coding-agents research-automation benchmarks

"Research acceleration: The view inside OpenAI" reports the lab hit its fall-2025 goal of an "automated research intern" by September 2026 and targets an automated AI researcher by March 2028. The measured numbers: the median OpenAI researcher now spends >$600/day of agent inference at API prices (90th percentile >$7,000/day); the research org runs 3.1 agent-workdays per human workday; experiments-per-experimenter hit an all-time high in August. After the Aug 7 Astra cyber restriction, Astra-class GPU allocation fell 59.2% while other model classes rose 17.2%, offsetting ~85% of the loss.

Why it matters: the first quantified look inside a frontier lab's agent-driven research loop. The post's own hedges belong in the headline: the metrics are "relatively easy to measure, but… hard to interpret," compute growth (not just agents) may explain the experiment surge, and it explicitly does not claim overall research pace has accelerated in proportion. All figures are self-reported and unaudited.

🔗 OpenAI: Research acceleration · 🔗 Hacker News discussion

12. aipoch/open-science — a local-first AI research workbench where every artifact carries provenance

  • Velocity: â–® steady
  • Source: GitHub Trending · 3.8k stars · +145 stars today · TypeScript · Apache-2.0
  • Tags: research agents notebooks provenance electron

An Electron/React/Prisma-SQLite desktop workbench that wraps selectable agent backends (Claude Code, OpenCode, Codex, CodeBuddy) with Python/R notebooks, 22 featured scientific skills (AlphaFold2, Boltz, DiffDock, ESM-2, scGPT, Remote Compute SSH) and 24 research connectors (PubMed, bioRxiv, ChEMBL, Clinical Trials). The differentiator is provenance: every artifact is an immutable checksummed version tied to its producer code, execution history, environment inventory and the exact conversation branch that produced it — with unverifiable evidence explicitly marked unavailable. Ships a CLI + headless SDK.

Why it matters: part of the vertical-agent-workbench wave, and unusually honest about it — its "What This Is Not" section pre-emptively disclaims the two framings competitors get (not a chat UI, not an unofficial client). Caveats from the README itself: generated output "does not replace expert judgment, statistical review, or validation against primary evidence," and the trend trigger is a v0.23.0 release rather than a launch event.

🔗 aipoch/open-science · 🔗 aipoch.com/open-science

13. AutoHedge — Swarms' autonomous "AI hedge fund" goes viral, with the caveats in its own README

  • Velocity: â–® steady
  • Source: GitHub Trending · 4.6k stars · +137 stars today · Python · MIT
  • Tags: ai-agents finance swarms trading solana

A four-agent pipeline from The-Swarm-Corporation: Director (thesis generation) → Quant (technical/statistical analysis) → Risk Manager (position sizing) → Execution (order generation), with structured JSON outputs, per-stage logging and live market data. The README's venue table is blunt: full autonomous trading on Solana only — Coinbase is "coming soon" and other CEXs are roadmap-only.

Why it matters: representative of the "agent swarm does real-world execution" genre crossing from demo to production code — and the caveats are severe enough to belong in the item, not the footnotes: setup requires pasting a WALLET_PRIVATE_KEY into .env, execution is fully autonomous once running, and no audit, backtest or performance evidence appears anywhere in the repo.

🔗 The-Swarm-Corporation/AutoHedge · 🔗 Trendshift listing

14. "Recreating Minecraft Is Not a Benchmark" — the demo-benchmark critique, the week after Astra

  • Velocity: â–® steady
  • Source: Hacker News · 55+ pts · 41 comments · ~21h ago (~22:52 UTC+8)
  • Tags: benchmarks evaluation overfitting critique

Kuber Mehta's post-Astra essay argues the viral launch demos (Minecraft-in-one-prompt, pelican SVG, bouncing ball) are "demo-benchmarks": fixed, famous targets a lab can optimize for on a release schedule, so they "measure preparation instead of capability." He cites Thinking Machines' Inkling Small — within a point of its flagship on the AA Intelligence Index (40 vs 41) with under a third of the parameters, while beating it on Humanity's Last Exam (32% vs 30%), GPQA Diamond (89%) and SciCode — as evidence static public evals leak into training. He notes the partial fix already exists (LiveBench rotation, ARC-AGI and HLE holdouts) but asks why the pelican still wins.

Why it matters: a crisp articulation of the contamination problem from the community side — and the counterweight to this feed's benchmark coverage all week. Caveats: the Inkling Small numbers are AA-computed, not independently reproduced, and the essay's "smaller models feel dumber in practice" claim is anecdotal, not measured.

🔗 Recreating Minecraft Is Not a Benchmark · 🔗 Hacker News discussion

15. "Knowing When Not to Reuse" — BCIT formalizes when past training evidence goes stale, tops HF papers

  • Velocity: â–® steady
  • Source: Hugging Face Daily Papers · 149 upvotes · top-5 of the Sep 4 batch · arXiv 2608.26730
  • Tags: post-training rl transfer-learning autonomous-training arxiv

Li et al. formalize "conditional experience transfer" in autonomous LLM post-training: which past update evidence remains valid after the parent model has changed. Their Boundary-Calibrated Intervention Transfer (BCIT) binds an observed effect to its source context, vetoes candidate transfers with "named hard conflicts," and runs a bounded training trial when needed. On a 4B model adapted across finance reasoning, text-to-SQL and function calling, BCIT authorized fewer harmful updates and reached higher equal-budget final-model quality than the evaluated alternatives.

Why it matters: as labs automate post-training loops (see item 11), reusing stale success evidence becomes a compute-waster and a trajectory-degrader — this is an early formal attack on that problem. The abstract's own caveats: results are on a single 4B model across three domains, the win is only "than the evaluated alternatives," and no frontier-scale validation exists yet.

🔗 arXiv 2608.26730 · 🔗 Hugging Face Daily Papers

16. NetBSD 9.5 released — the final release of the netbsd-9 branch, which is now EOL

  • Velocity: â–® steady
  • Source: Hacker News · 81+ pts · 5 comments · ~12h ago (~23:44 UTC+8)
  • Tags: bsd release eol operating-systems

The NetBSD Project released 9.5 on Sep 6 — the fifth and final release of the 9 stable branch, a security/stability fix set since 9.4 (April 2024), fully compatible with 9.0. The same announcement declares end-of-support for all NetBSD 9.x and the netbsd-9 branch, pointing users at 11.0 (11.1 due end of September) or 10.2 ("to be released in a few days").

Why it matters: anyone still pinning to netbsd-9 loses a supported branch this week — an ops-relevant deadline, softened only by the unusually long 9.x window. Low-attention but concrete: this is the rare release announcement that is simultaneously an EOL notice.

🔗 NetBSD: 9.5 released and netbsd-9 EOL · 🔗 Hacker News discussion

17. Trezor: ShipMonk breach exposed another 67,000 US customers — data the vendor had written assurances was deleted

  • Velocity: â–® steady
  • Source: Trezor disclosure · Sep 5 · third-party data breach
  • Tags: data-breach supply-chain third-party crypto phishing

Trezor disclosed on Sep 5 that a breach at fulfillment partner ShipMonk exposed names, emails, phone numbers, shipping addresses and order numbers of 67,000 additional US customers (orders from November 2019–August 2021), on top of the 13,689 disclosed in August — over 80,000 total. Trezor says it had repeatedly received written confirmation the data was deleted per its contract and ShipMonk's stated 90-day retention policy; it was not deleted. Hardware-wallet security is unaffected; the practical risk is seed-phrase phishing impersonating Trezor, echoing the 2024 third-party mail-service campaign.

Why it matters: a concrete case of third-party retention violating contractual deletion — worth auditing your own fulfillment vendors' actual deletion behavior. For crypto users the exposure feeds social-engineering attacks where a password reset is no protection. Caveat: the figures come from Trezor's own disclosure; there is no independent count.

🔗 Trezor: shipping provider incident · 🔗 The Hacker News coverage

18. A Python interpreter in 1024 bytes — direct-execution, zero error handling, "to feel human"

  • Velocity: ▮▮▮ trending
  • Source: Hacker News · 138+ pts · 54 comments · ~4h ago (~08:00 UTC+8)
  • Tags: python interpreters c code-golf compilers

Austin Z. Henley wrote a Python-subset interpreter in exactly 1024 bytes of C — no macros, no libraries, no AST, no bytecode. Expressions are evaluated during recursive-descent parsing; while/for loops remember a source position and reparse on every iteration; functions are stored as source positions the symbol table jumps to, with the C call stack handling block recursion. It runs FizzBuzz with real Python syntax — def, colons, indentation — and limitations are stated plainly: zero error handling ("assumes that the keywords are all typed out correctly"), single-letter variables, one comparison per expression. Motivation, quoted: "To feel human, I write code by hand on the weekends."

Why it matters: the top of HN on a slow news morning chose a hand-written interpreter over every agent story — and the top comment critique is the real content: this is a "Python-like" toy (an f is a for-loop, a w is a while), so read it as a lesson in how little machinery a language runtime needs, not as Python. The thread's indentation-grammar sidebar (why mixed tabs/spaces forces a non-regular lexer) is worth the click alone.

🔗 austinhenley.com: python1024 · 🔗 Hacker News discussion

19. ROCm 10.0 — AMD's decade mark ships ROCm.AI: agent skills, a unified CLI, and Hyperloom optimization agents

  • Velocity: ▮▮ rising
  • Source: AMD ROCm Blog · published Aug 27 · hit Hacker News ~2h ago (~10:00 UTC+8)
  • Tags: amd rocm gpu agent-skills inference

The first major ROCm version bump since 7.x (built on TheRock, ~10 years after ROCm 1.0) centers on ROCm.AI: a tech-preview rocm CLI (rocm serve <model>, rocm examine, air-gapped bundles), AMD Skills — agent skills in the Agent Skills format for Claude, Cursor and Codex (github.com/amd/skills, covering rocm-doctor and LLM-serving workflows on Instinct and EPYC) — and Hyperloom, an open-source agentic system automating a Profile → Analyze → Plan → Optimize → Validate loop (TraceLens-Agent, Magpie, IntelliKit, GEAK, Arbor), which AMD claims cuts "weeks of manual optimization work down to hours." Also: RCCL merged upstream to NCCL 2.30.4, production vLLM/SGLang containers, and a unified ROCm Core SDK replacing the Windows HIP SDK.

Why it matters: the agent-skills format is now being adopted by a GPU vendor as a first-class support surface — AMD is meeting Claude/Codex users where they already are. Caveat that matters: secondary coverage (StorageReview, Wccftech) repeats a claimed "3.3× inference uplift vs ROCm 7" that appears nowhere in AMD's own post — the only quantitative claim AMD makes is Hyperloom's hours-vs-weeks one. Cite the blog, not the multiplier.

🔗 AMD ROCm Blog: A Decade of Open Compute · 🔗 Hacker News discussion

20. Gamers Nexus: "216M Spy TVs" — LG executives on tape describing how to "own the living room"

  • Velocity: ▮▮ rising
  • Source: Hacker News · 46+ pts · 16 comments · ~2h ago (~10:00 UTC+8)
  • Tags: privacy smart-tv telemetry atr gamers-nexus

Gamers Nexus's latest investigation documents LG smart TV data collection at advertising-industry scale — 216 million units — built around clips of LG executives at an advertiser presentation: "within an LG TV household we can help extend the ad campaign footprint to the other devices in the household," "own the living room," "We own the glass." Thread summaries of the video add microphones that allegedly can't be disabled, plain-text transcript uploads, and network-wide device discovery including IP addresses of every device on the home network.

Why it matters: the ad-tech ambitions are documented in LG's own executives' words, which is what separates this from the usual ACR telemetry story. Caveats are load-bearing: the strongest claims (always-on mics, plaintext uploads) circulate here as commenters' summaries of the video, not independently verified documents — and no one in the thread could answer whether this survives EU privacy law. The practical advice stands regardless: no network, or a VLAN, for the TV.

🔗 YouTube: 216M Spy TVs – The LG Smart TV Problem · 🔗 Hacker News discussion

21. "Editable Visual Design" — Tencent Hunyuan tops HF papers with design-as-code from a coding agent

  • Velocity: ▮▮ rising
  • Source: Hugging Face Daily Papers · 516 upvotes · #1 of the Sep 6 batch · arXiv 2609.04034
  • Tags: visual-design agents vlm html text-to-image

A Coding-Agent paradigm for visual design: a VLM (requirement understanding, planning, code, aesthetic judgment) drives an image-generation model on demand in an "imagine first, then act" loop — generate an imagined visual to set aesthetic priors, cut out text-free assets via alpha/green-screen matting, then write native HTML/CSS with explicit layers. Verification pairs deterministic layout checks in a headless browser with VLM review of rendered screenshots, and "Agent Design Replay" serializes the whole trajectory for reproducibility. Showcase: an information-dense field guide with 120 editable layers in 13 groups; repairs converging in one or two rounds.

Why it matters: the same "layout as code, agent as designer" bet several agent-UX startups are making, published as a method with its full trajectories. The paper's own honesty is the headline caveat: "We therefore report cases rather than scores" — no ground-truth metric for aesthetics or editability exists, output is bounded by the underlying models, and only single-page designs were demonstrated.

🔗 arXiv 2609.04034 · 🔗 Hugging Face paper page

22. D2 goes non-profit — Terrastruct shuts down, D2 Studio and the TALA layout engine go open source

  • Velocity: ▮▮ rising
  • Source: Hacker News · 32+ pts · 15 comments · ~10h ago (~02:00 UTC+8)
  • Tags: diagramming d2 open-source governance non-profit

The D2 diagramming language is transitioning to non-profit status as its backing company Terrastruct shuts down; the canonical repo has already moved from terrastruct/d2 to d2lang/d2 (25.2k stars, MPL-2.0, still shipping verified releases). Maintainer alixander (Dylan) Wang confirmed in the thread that D2 Studio and the TALA layout engine — until now the paid product — will be open-sourced, with Hack Club reportedly financing the non-profit. The announcement's sharpest line: "D2 thus far has been a product of handcrafted code. That era is over" — going forward Wang will "welcome AI contributions and… use AI to review your AI," keeping only the writing human.

Why it matters: a rare live-fire test of two transitions at once: a company-owned language surviving its company via non-profit governance, and a maintainer openly reorganizing a 25k-star codebase around AI-written, AI-reviewed code. Commenters split exactly there — some call the all-AI development approach concerning, others the right division of labor; one questions Hack Club (a teens-focused funder) financing a project maintained by an OpenAI infrastructure person.

🔗 d2lang/d2 (new canonical repo) · 🔗 Hacker News discussion

23. Windows 11 "Project Zenith" — a "distraction-free" developer edition that is File Explorer defaults

  • Velocity: ▮▮ rising
  • Source: Hacker News · 67+ pts · 46 comments · ~5h ago (~07:00 UTC+8)
  • Tags: windows microsoft developer-experience bloatware

Microsoft pitched "Project Zenith" as "the ready-to-code Windows experience," a distraction-free developer-focused edition sold largely as devices. The concrete feature list, per the Windows blog: File Explorer "shows file extensions, hidden files, the full path in the title bar," plus the details pane and long-path support enabled by default. Neowin's verdict — "another marketing misfire" — matched the thread: ryandrake suspected a deliberately low-effort product so Microsoft can later claim nobody wants a decrappified Windows; others noted Microsoft's own developers reportedly use Macs; amlib speculated the unstated feature is faster harvesting of codebases for AI training.

Why it matters: the entire feature set is configuration most developers apply in ten minutes — the news is that Microsoft now sells its own defaults' absence as a product tier. Watch what ships versus what the marketing implies: if "developer edition" ends up meaning preinstalled tooling plus telemetry-adjacent services, the thread's cynicism will have been the accurate reading.

🔗 Neowin: another marketing misfire · 🔗 Hacker News discussion

24. "Is mathematics about to enter the conservatory?" — a mathematician's post-Fermat essay on who funds theorem-provers

  • Velocity: â–® steady
  • Source: Hacker News · 25+ pts · 44 comments · ~4h ago (~08:00 UTC+8) · post dated Sep 6
  • Tags: mathematics ai lean research essay

Mathematician Mike McCoy writes the week after Claude's formal Lean proof of Fermat's Last Theorem, noting that in the same week a paper resolved the Spherical Hadwiger Conjecture (open since ~1974) — and asking what patronage model research mathematics gets when AI does the proving. He uses his own grad-school lemma as a case study, and the thread caught his most-quoted admission: a proof he worked through with an AI model that he hadn't fully verified — "the math is being both generated and read by models."

Why it matters: the first durable essay to come out of the Fermat demo, and it argues the conservatory analogy from the funding side, not the capability side — who pays for mathematicians when proof-search automates. The comment pushback is the counterweight: orchestras' principals earn $250–400k (the analogy's precarity premise is contested), music is universally accessible while research math is not, and one commenter argues the real future patron is intelligence agencies.

🔗 mbmccoy.dev: mathematical-conservatory · 🔗 Hacker News discussion

25. Reverse engineering Cronos — a KOD-encoded Soviet-era desktop database, cracked with a Hungarian algorithm

  • Velocity: â–® steady
  • Source: Hacker News · 34+ pts · ~2d ago (~10:00 UTC+8 Sep 5)
  • Tags: reverse-engineering databases forensics cronos

Cronos (CronosPro) is the proprietary database behind registries and archives across Russia and post-Soviet states — a "Bank" of "Bases" in .dat/.tad file pairs. The team received a dump considered unparseable: Cronos v4 (01.11), where the schema file CroStru was KOD-encoded — a 256-byte substitution table plus position- and record-number-dependent arithmetic. Since only the small schema was KOD'd (the data files were merely compressed), they scored every possible KOD mapping against byte frequencies from test databases, then solved the mapping as an assignment problem with SciPy's Hungarian algorithm — validating on known keys like BankName. The fix that mattered was a 12-byte extent header shifting every payload byte's decode position.

Why it matters: a worked example of the "reverse engineering, amplified by AI/stats" trend the thread itself names — and the post's sharpest warning generalizes far past Cronos: a CSV with readable values under the wrong headers looks perfectly valid while being semantically corrupted, which is exactly how bad migrations and forensics go unnoticed.

🔗 blog.glazer.ee: Converting Cronos · 🔗 Hacker News discussion

26. The NX bit is not just about security — a bare-metal debugging story where NX is what stops speculative instruction fetches

  • Velocity: â–® steady
  • Source: Hacker News · 35+ pts · 23 comments · ~2d ago (~10:00 UTC+8 Sep 5)
  • Tags: nx-bit cpus arm memory-safety systems

A guest post on purplesyringa.moe walks through debugging a bare-metal ARM64 hypervisor for postmarketOS on a MediaTek MT6735 (Cortex-A53): with the CTR_EL0 intercept enabled, the phone hung at random. The chase ends at the difference between blr x0 (dynamic, mispredictable) and bl (static): the CPU's speculative instruction fetches — not data accesses — were reaching address 0x0, the locked-out bootrom, and marking the pages non-executable is what stopped them. The upshot, quoting ARM's own docs: Device memory prevents speculative data accesses only, so on ARM the NX bit is "not about security at all — it's essentially an attribute bit" (the author searched the Cortex-A53 errata and found nothing similar — spec-conformant, not a silicon bug).

Why it matters: a systems-literate corrective to the "NX = DEP" mental model most developers carry. The comment section is half the value: NX long predates Spectre (ARM reused an existing flag post-Spectre rather than adding a mechanism), and one maintainer-grade critique argues ARM's design was simply a mistake — Device memory blocks data prefetch yet permits instruction prefetch, while ARM itself documents execution from Device memory as UNPREDICTABLE.

🔗 purplesyringa.moe: The NX bit is not just about security · 🔗 Hacker News discussion

27. MathKernel — a Show HN that routes an LLM's math through engines that carry trust labels

  • Velocity: â–® steady
  • Source: Hacker News (Show HN) · 19+ pts · 3 comments · ~2h ago (~10:00 UTC+8)
  • Tags: mcp mathematics llm-tools sympy formal-verification

A Python library + MCP server (MIT, v1.3.0) that exposes 160+ math_* tools wrapping SymPy, Z3, Lean 4 + Mathlib (auto-installed on first start), mpmath interval arithmetic, numba, CUDA/CuPy and python-flint/Arb over FastMCP 3. The design idea is "evidence-aware": every result carries a trust label — formal > exact > symbolic > interval_certified > numeric > empirical — and overall trust is capped by the weakest evidence a claim requires. Backend disagreement is preserved as a conflict, not averaged; decimal inputs cap trust at numeric and block formal certificates; renderers can present results but never upgrade their evidence.

Why it matters: a small project (20 stars, 4 commits — early, unproven) that states the right contract for LLM math tooling: the model interprets intent, the tool establishes evidence, and provenance is typed rather than implied. Watch whether the trust-label scheme gets adopted by bigger MCP math servers — it is the part worth copying even if this implementation isn't.

🔗 staatsgeheim/MathKernel · 🔗 Show HN discussion

28. N-able N-central CVE-2026-86218 — CVSS 10.0 pre-auth RCE zero-day, and the vendor can't decide if it's exploited

  • Velocity: ▮▮▮ trending
  • Source: The Hacker News · Sep 6–7 · CVSS 4.0 10.0 (N-able CNA-assigned) · hotfix 2026.3 HF4 shipped Sep 6
  • Tags: rmm zero-day rce msp cve-2026-86218

N-able shipped its fourth N-central hotfix in five weeks (2026.3.1.14) for CVE-2026-86218 — a static code injection flaw (CWE-96) allowing unauthenticated RCE on the N-central server, scored the maximum CVSS 4.0 10.0 by N-able itself. The fix landed ~8 hours after Hotfix 3 (Sep 5, two other flaws: 6.9 internal-API access, 7.7 auth bypass), meaning every build before 2026.3.1.14 — including freshly-patched HF3 servers — is vulnerable. The exploitation record is a mess of the vendor's own making: the release notes say there are "no confirmations that this vulnerability has been exploited in production environments" while the incident notice on the uptime page says it "has been observed being exploited in the wild" — and also calls it a "critical zero-day" without defining the term. Huntress reproduced a working PoC chain against 2026.3.1.10 but could not confirm which CVE was used in a real customer intrusion because the logs had rotated; the incident was still open Sep 7. Context: attackers breached N-able-adjacent infrastructure on July 31 via an auth bypass, then reached managed endpoints through Take Control and Cloudflare tunnels — the second consecutive summer of in-the-wild N-central attacks.

Why it matters: an RMM console is the keys to every endpoint an MSP manages, so "patch it" is necessary but not sufficient — Huntress's advice is IP allowlisting/VPN or pulling internet-reachable servers offline, plus account auditing, because hotfixes don't evict attackers already inside. The conflicting vendor statements are themselves the finding: when the CNA can't keep its own exploitation story consistent, treat exploitation as confirmed until proven otherwise.

🔗 The Hacker News: fourth N-central hotfix · 🔗 Huntress analysis

29. Nitter and XCancel resume service after legal advice — 12 days after X Corp's cease-and-desist

  • Velocity: ▮▮▮ trending
  • Source: Hacker News · 779+ pts · 343 comments · ~12h ago (~01:49 UTC+8)
  • Tags: nitter xcorp cease-and-desist scraping frontend

Nitter.net and the XCancel instance — the two largest X/Twitter frontends — came back online Sep 6, twelve days after going dark on X Corp's cease-and-desist letters (Aug 24). The letters, per TechCrunch, alleged "unlawful use and circumvention of X's API," cited the Texas Harmful Access by Computer Act and the Lanham Act, and demanded permanent takedown of all Nitter instances plus the code repository by 5 p.m. EST on Aug 25. Creator Zedeus took the services offline and stopped development "for the time being" while seeking legal advice, saying only that they "won't be commenting further on the specifics." The resumption landed at #3 on HN's front page within hours.

Why it matters: the first test of whether a C&D without litigation can permanently kill widely-used open infrastructure — the resumption implies counsel found the claims contestable enough to risk operating. Caveats are load-bearing: no public legal filing exists, the terms or conditions of the resumption (if any) are undisclosed, and the entire account rests on Zedeus's statements. The repo remained up throughout; the HN thread treats the episode as a live probe of scraper liability under state computer-misuse laws.

🔗 Hacker News discussion · 🔗 TechCrunch: X's C&D against Nitter

30. heygen-com/hyperframes — "Write HTML. Render video. Built for agents" tops today's trending at 44.7k stars

  • Velocity: ▮▮ rising
  • Source: GitHub Trending · 44.7k stars · +220 stars today · TypeScript · Apache-2.0
  • Tags: video agents html agent-skills ffmpeg

HeyGen's open-source framework turns plain HTML compositions — with timing expressed as data attributes — into deterministic MP4s via a headless-Chrome frame-seeker plus FFmpeg: "same input, same frames, same output," aimed at CI and regression testing. It ships 20 agent skills (npx skills add heygen-com/hyperframes) that teach Claude Code/Cursor/Codex the video-production loop, animation adapters (GSAP, CSS, Lottie, Three.js, Anime.js, WAAPI), a Studio browser editor, and AWS Lambda distributed rendering. It positions itself against Remotion on two axes: plain HTML vs React components, and Apache-2.0 vs Remotion's source-available license.

Why it matters: video is becoming an agent output modality, not just an input — and the packaging (skills, deterministic renders) is built for that loop. The aggregate-trap caveat applies: this repo rode three near-invisible Show HNs in April–May (3–6 points each) to 44.7k stars, and we could not identify any fresh launch event driving today's #1 trending slot — treat it as sustained momentum, cite the repo, not the rank. The README's own hedges: it concedes Remotion Lambda is a "more mature cloud renderer," the skills.sh registry blob "can lag main by hours," and dev clones need ~240 MB of Git LFS test baselines.

🔗 heygen-com/hyperframes · 🔗 April Show HN: HyperFrames

31. Anubis ships WebAssembly proof-of-work after a year — and its own gate blocked us reading the announcement

  • Velocity: ▮▮ rising
  • Source: Techaro blog · Sep 6 · v1.28.0-pre1 released Aug 30
  • Tags: anti-bot webassembly proof-of-work ai-crawlers

Anubis — Xe Iaso's proof-of-work gate that major sites (kernel.org, GNOME and others) deploy against AI scrapers — published "It took a year to ship WebAssembly in Anubis" on Sep 6, recounting a year of work, hundreds of commits and five generations of PRs. The WASM proof-of-work itself shipped in v1.28.0-pre1 ("Wuk Lamat", Aug 30): Rust compiled to WebAssembly runs the hash check with SIMD acceleration where browsers support it, falling back to pure JavaScript when WASM is disabled — slower, because those clients usually disable the JIT, and the progress bar doesn't update during wasm2js checks (a known issue). Difficulty semantics change: WASM counts leading bits, so sha256 difficulty 16 ≈ the old "fast" difficulty 4. New challenge methods are disabled by default pending testing. Fittingly, our own fetch of the announcement was served Anubis's "Access Denied" challenge page — the tool works.

Why it matters: the AI-crawler arms race has moved from CSS tricks to a compile-to-WASM performance problem, and the JS fallback is the accessibility price: readers on locked-down browsers pay a slower challenge. The v1.27.0 stable line (Aug 8) is also relevant to operators: cookie names are now derived from cookie settings — a breaking change that fixed infinite challenge loops.

🔗 Techaro: It took a year to ship WebAssembly in Anubis · 🔗 TecharoHQ/anubis releases

32. GrapheneOS overhauls its default apps and ships a secure clipboard — with RCS + E2EE on the roadmap

  • Velocity: ▮▮ rising
  • Source: Hacker News · 318+ pts · 216 comments · ~10h ago (~04:24 UTC+8) · announced via GrapheneOS Mastodon
  • Tags: grapheneos android privacy clipboard mobile-security

The hardened Android ROM announced a two-part change: a secure paste feature that replaces the traditional clipboard APIs — users can revoke clipboard access from apps entirely, closing the long-standing Android gap where any app can read the global clipboard — and an overhaul of its bundled default apps, starting with the Messaging app being modernized. On HN, the dominant thread point was the longer-term plan: RCS support including standard end-to-end encryption via Messaging Layer Security (MLS). The announcement arrived via the project's Mastodon alongside a new release.

Why it matters: clipboard is one of Android's oldest systemic privacy leaks, and replacing the API surface — rather than adding a permission prompt — is the same "fix the mechanism, not the setting" philosophy GrapheneOS applies elsewhere. MLS-based RCS E2EE on a hardened ROM would be a first; caveat: that part is explicitly longer-term and not in this release, so judge the shipping feature (secure paste) on its own.

🔗 Hacker News discussion · 🔗 GrapheneOS features

33. lightpanda-io/browser — the from-scratch Zig headless browser adds agent mode and an MCP server, 34.6k stars

  • Velocity: ▮▮ rising
  • Source: GitHub Trending · 34.6k stars · +116 stars today · Zig · AGPL-3.0
  • Tags: headless-browser zig agents mcp web-automation

Lightpanda is not a Chromium fork or a WebKit patch — it's a browser built from nothing (v8 for JS, html5ever for parsing, libcurl for HTTP, no rendering engine at all) aimed at AI and automation workloads. The current README adds an agentic surface: lightpanda agent for natural-language browser control across Anthropic/OpenAI/Gemini/Ollama backends (or LLM-free with --no-llm), PandaScript recordable/replayable deterministic scripts, and a native MCP server with per-connection session isolation — alongside CDP and WebDriver BiDi compatibility with Puppeteer/Playwright. The benchmarks claim ~16× less memory and ~9× faster than headless Chrome over 100 pages.

Why it matters: the "browser for agents" layer is starting to consolidate into purpose-built engines rather than Chromium wrappers — the same bet Obscura made yesterday from the Rust side. The caveats are the cost of from-scratch: Linux binaries are glibc-linked (they fail on Alpine/musl), there's no native Windows build (WSL2 only), telemetry is on by default, Web Platform Tests results are still incomplete, and there are nightly builds only — no versioned releases. The memory/speed numbers are the vendor's own.

🔗 lightpanda-io/browser · 🔗 HN: Why we built Lightpanda in Zig

34. mksglu/context-mode — sandboxing agent tool output claims 98% context savings, at the cost of a per-platform hook matrix

  • Velocity: â–® steady
  • Source: GitHub Trending · 20.5k stars · +85 stars today · TypeScript · Elastic License 2.0
  • Tags: context-window mcp claude-code agent-infra

An MCP server + hooks plugin that keeps raw tool output out of the model's context window: ctx_execute runs code in 12 languages via isolated subprocesses and passes only stdout into context (the README's claim: 315 KB → 5.4 KB, ~98% reduction); session events persist to per-project SQLite (FTS5 + BM25) and are rebuilt into a ~2 KB snapshot after compaction; a "think in code" router pushes the agent to script data processing instead of reading files. Its honest engineering cost is the platform matrix: hooks exist for Claude Code, Gemini CLI, Cursor, Codex CLI and Copilot, but Antigravity and Zed have no hooks, Cursor rejects its sessionStart hook, Codex PreToolUse is deny-only, and Kiro's spawn hook isn't wired — so session restore silently degrades on several platforms. Search is progressively throttled after 9 calls.

Why it matters: context economics is becoming its own infrastructure layer (see this week's LatentPress and Spotify's "shunt"), and context-mode is the pragmatic end: don't compress the history, just never let the raw bytes in. Note the license — Elastic 2.0, not OSI open source — and that the 98% figure is the vendor's own benchmark.

🔗 mksglu/context-mode · 🔗 HN: MCP server that reduces Claude Code context consumption by 98%

35. ECC passes 252k stars at +1,905 today — since we covered it Sep 1, it shipped 2.2 with guided setup

  • Velocity: â–® steady
  • Source: GitHub Trending · 252k stars · +1,905 stars today · JavaScript · MIT
  • Tags: agent-harness claude-code skills update

Update to our Sep 1 coverage: affaan-m/ECC — the "agent harness performance optimization" bundle (68 agents, 286 skills, 94 commands, hooks, memory, AgentShield config scanning) — is today's top star-gainer on GitHub trending and has shipped ECC 2.2, adding guided package setup for Claude Code, Codex and Kimi Code via npx ecc-universal setup. Since Sep 1 it also grew 2.1's Plan Canvas (a loopback browser UI for annotating agent plans), a Kimi Code install target, and self-hosted GPU compute via Itô; a unified Memory Vault (ecc memory) for cross-harness context is in development.

Why it matters: the harness-tuning category is consolidating around cross-harness portability rather than any single CLI — ECC now treats Claude Code, Codex, Kimi and Cursor as interchangeable runtimes with per-platform feature caveats it documents honestly (hooks not configured for Kimi, Cursor behavior varies by build). The README's security note is worth repeating as star velocity climbs: install only from official channels — unofficial mirrors "may contain malware."

🔗 affaan-m/ECC · 🔗 ECC releases (2.2)

36. Bryan Cantrill's "Your intellectual fly is open" (2025) resurfaces at 664 points — the LLM-writing tell, from the other side

  • Velocity: â–® steady
  • Source: Hacker News · 664+ pts · 410 comments · ~18h ago (~19:56 UTC+8 Sep 6) · essay dated Dec 5, 2025
  • Tags: llm-writing ai-slop authenticity essay

A ten-month-old Bryan Cantrill essay hit #4 on HN this weekend. His argument, in his own framing: "Bluntly, your intellectual fly is open: lots of people notice — but no one is pointing it out" — LLM-authored prose carries stylistic tells (em-dash density, parallel-construction cadence, "It's not just X, it's Y" hedging) that readers detect even when nobody says so, and using an LLM to author a post trades away the authenticity that made the post worth reading. He pairs it with Oxide's internal RFD 576 on LLM use, which reuses the metaphor. Notably, this is a different essay from Cantrill's "The revolt of the reader," which this feed covered yesterday — the same weekend produced both.

Why it matters: the honest framing first: this is a 2025 resurface, not new writing — its velocity is community re-litigation, not freshness. The thread's value is the counter-arguments: LLM-assisted writing as an accessibility aid for non-native speakers, the impossibility of policing style, and the observation that the tell list is already stale because models have been patched against it.

🔗 bcantrill.dtrace.org: Your intellectual fly is open · 🔗 Hacker News discussion

37. WorldSculpt — compositional 3D worlds from grounded videos, occluded objects included, tops HF papers

  • Velocity: â–® steady
  • Source: Hugging Face Daily Papers · top of the current batch · arXiv 2609.05416
  • Tags: 3d-generation world-models video benchmark arxiv

WorldSculpt generates a compositional 3D representation of cluttered scenes — hundreds of objects as separate, individually-placed, editable meshes in a shared world frame. The trick is a single-object 3D generative prior (instantiated as "Pixal3D") with a multi-view conditioning pathway that grounds generation in posed video views; the model is fine-tuned entirely on single objects in canonical space, with no scene-level training, yet still fills geometry that heavy occlusion hides. The team also releases UE-MeshyScene, a photorealistic benchmark of densely cluttered scenes with per-object annotations and ground-truth meshes, and shows the method can convert generated 3DGS worlds (Marble, HY-World 2.0) into compositional mesh scenes.

Why it matters: editable, per-object scene representations are the substrate world-model and simulation work (robotics, game tooling) actually needs — a monolithic mesh or point cloud is not. The honest caveat is structural: gains are measured against prior work on their own new benchmark, and the abstract reports no failure analysis for the hardest occlusion cases — "feasibility and scalability" is the claim, not correctness.

🔗 arXiv 2609.05416 · 🔗 Hugging Face paper page

Metadata

FieldValue
Generated2026-09-07T14:12:00+08:00
Items37
Sources tracked36 (Sansec Threat Research, The Hacker News, Hacker News, OpenAI Blog, GitHub Trending, Trendshift, keepitfree.ai, US Treasury, US State Dept, Wordfence, NVD, Asahi Linux, NetBSD Project, arXiv, Hugging Face Daily Papers, kuber.studio, aipoch, The-Swarm-Corporation, Elastic Security Labs, Trezor Blog, marketing-skills.com, nosignups.net, austinhenley.com, AMD ROCm Blog, Gamers Nexus/YouTube, mbmccoy.dev, blog.glazer.ee, purplesyringa.moe, Neowin, d2lang (GitHub), staatsgeheim/MathKernel, Huntress, TechCrunch, Techaro blog, GrapheneOS, bcantrill.dtrace.org)
Update schedule04:03, 12:03, 20:03 UTC+8 (3x daily)
RankingVelocity-weighted (recency × engagement acceleration × source authority)
LicenseCC-BY 4.0

Previous day · Raw .md · Archive