eMudhra to exit global SSL/TLS certificate business

Quad9 (DNS Resolver) to Exit France

Jailbreaking the Switch 2

WorldTUI: I trained a 360M model to pretend to be a terminal

What Is Gridifcation

What’s getting pwned right now

Woman faces six years in prison over Cash App account she never opened

Show HN: Run full iOS 16.5 firmware on Android Devices

MPs moving to restrict gambling ads in Canada

Faster than earcut: triangulating 3.7M map polygons in 489 ms

A farewell to Arc browser

I posted here about the then-upcoming PHP RCEs related to CVE-2026-109618 &amp; CVE-2026-109619. I appreciate this has had considerable knock-on effects with the schedule for co-ordinated disclosure, and created additional workload.I am truly sorry. I take full responsibility for my actions.It was not remotely my intention to cause any of the subsequent side effects.At the time of posting, I didn&#x27;t know about any embargo. My contact had told me there was no embargo, and her contact had told her the same thing.As someone who follows the 4-weekly PHP release cycle and compiles it from source, my intention was to alert others in a similar position to be aware of the importance&#x2F;urgency of the updates.That clearly backfired in a pretty wild fashion. I have learned my lesson.

Tell HN: I unknowingly broke the PHP RCE embargo. I am sorry.

OpenShell – A safe, private runtime for fleets of autonomous AI agents

Getting ready to operate GNU Taler in Germany

Startup taps underwater volcano as energy source in “proof point” test

Xbox wants you to pay 24 to 40 cents per hour to stream games you bought

Dungeon Generation in the Gnomish Mines of NetHack

The Last Museum: Semantic search across 5.8M artworks from major museums

A complete bypass of eMudhra’s 1FA OTP login system

Every AI model has the same "controversial" take on humans