I found 10k GitHub repositories distributing Trojan malware

.gitignore Isn't the only way to ignore files in Git

<a href="https:&#x2F;&#x2F;web.archive.org&#x2F;web&#x2F;20260618212028&#x2F;https:&#x2F;&#x2F;www.thatprivacyguy.com&#x2F;blog&#x2F;elkjop-forced-consent-fine&#x2F;" rel="nofollow">https:&#x2F;&#x2F;web.archive.org&#x2F;web&#x2F;20260618212028&#x2F;https:&#x2F;&#x2F;www.thatp...</a><a href="https:&#x2F;&#x2F;archive.ph&#x2F;I4zjA" rel="nofollow">https:&#x2F;&#x2F;archive.ph&#x2F;I4zjA</a>

I told them forced consent was unlawful. 5 years later it cost Elkjop €1.8M

CS 6120: Advanced Compilers: The Self-Guided Online Course (2020)

With more traffic moving off-web and into LLMs, I got curious about what traces we leave &quot;in the weights&quot;. My design partner and I built a site in the past few weeks that checks recognition across frontier and small models. It queries many of them in parallel, clusters the responses, and tells you how strongly they recognize you. Happy to answer any questions here!

Show HN: Are You in the Weights?

Ubiquiti: Enterprise NAS, Built on ZFS

Hospitals and universities repurposing drugs at lower cost

W Social, public institutions and the theater of European digital sovereignty

Zero-Touch OAuth for MCP

To study how chips work, MIT researchers built their own operating system

DuckDB Internals: Why Is DuckDB Fast? (Part 1)

Many Let's Encrypt renewals had errors today

Ice water drowning survival of young patient (2025)

Cell-based architecture for resilient payment systems

Hey HN - we’re Oskar, Szymon, and Piotr, and we’re building TesterArmy (<a href="https:&#x2F;&#x2F;tester.army">https:&#x2F;&#x2F;tester.army</a>). TesterArmy is an agentic testing platform that runs end-to-end checks before deployment and in production. Instead of wasting hours on manual testing or maintaining static scripts, we let you specify your tests in natural language and handle everything in between. We&#x27;ve built the platform fully around agents. Our agent will reliably execute the tests, but your coding agent can manage everything in our platform, from defining tests in natural language to running them on your behalf.Check out our demo video: <a href="https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=291IkUbPrlk" rel="nofollow">https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=291IkUbPrlk</a>.We started TesterArmy because testing is still far too painful. AI coding tools have made it dramatically faster to write and ship code, but testing is still a bottleneck. Traditional E2E tests are slow to set up and expensive to maintain. Managing auth and test users is painful. Setting up staging environments is painful. Running tests reliably is painful.We think most teams do not actually want to spend their time writing selectors or maintaining test infrastructure. They just want confidence that their core flows work. With TesterArmy, an engineer can sign up, give an agent our CLI, and let it handle creating tests and running them on schedule or on GitHub.When something breaks, TesterArmy alerts your team through Slack or Discord.Over the past few months, we scaled from 0 to 30+ teams using our product every day. We caught bugs in critical flows, including onboarding, checkout, and AI chat. We&#x27;ve got many of our customers migrating from already established competitors to us because of the quality and reliability of our agents.Here are a few of the recent bugs that our agent found (there were quite a lot of them!):1) Timezone bug that affected the booking flow in one of our clients&#x27; apps, the dashboard was very complex and hard to catch by a human. 
2) Regression in agent orchestration that caused a sandboxed environment to be stuck on loading, thanks to TesterArmy, the team was able to resolve it before it hit production.
3) Incorrectly counting the order amount in a complex dashboard flow with checkout, thanks to TesterArmy, the team was able to resolve it before it affected revenue
4) Catching a regression in an AI chat flow that would result in a user not being able to retrieve their data due to broken tool calling.And many more, mostly related to some incorrect API calls, 404s, unhandled errors, etc.If this sounds useful, we would love your feedback at <a href="https:&#x2F;&#x2F;tester.army">https:&#x2F;&#x2F;tester.army</a>. We have a bunch of free test runs for you to try. And don’t worry, we won’t make you do sales calls, and we don’t have long onboarding or annoying setup. Our goal is an it-just-works experience.If you&#x27;re looking for an end-to-end testing solution, we&#x27;d love to hear your feedback!

Launch HN: TesterArmy (YC P26) – Agents that test web and mobile apps

<a href="https:&#x2F;&#x2F;web.archive.org&#x2F;web&#x2F;20260618100028&#x2F;https:&#x2F;&#x2F;www.wired.com&#x2F;story&#x2F;sk-telecom-anthropic-mythos-export-controls&#x2F;" rel="nofollow">https:&#x2F;&#x2F;web.archive.org&#x2F;web&#x2F;20260618100028&#x2F;https:&#x2F;&#x2F;www.wired...</a>

The Korean telecom giant at the center of Anthropic's Mythos controversy

How Japan's railways stayed one while splitting apart

The AirPods Effect

Quick framing, since the post is long: I did robotic manipulation research at OpenAI from 2017–2020, and the tabletop setup back then cost roughly 10x this one and took a team to run. This project is me testing whether a single person can now do meaningful work on the same class of problems: starting with physical and software setup.A few decisions I&#x27;m least settled on, and would love some pushback&#x2F;feedback on:- single arm vs. bimanual (I went single for cost&#x2F;space, knowing it rules out things like folding cloth)- not calibrating camera extrinsics&#x2F;intrinsics for now- RGB vs. RGB-D for from-scratch policies (ACT &#x2F; Diffusion Policy)And one I&#x27;m more confident about but expect disagreement on: not building on ROS 2 &#x2F; LeRobot, and writing my own stack instead. Happy to get into the reasoning.

Building a robotics research setup that lives next to my desk

If your product is Great, it doesn't need to be Good (2010)