HNHacker News
TopNewBestAskShowJobs

Onplana

14 karma · joined May 13, 2026

submissionscomments
Onplana··on Only 33 days left in project online retirement
Access your project online real estate for free.
Onplana··on How I Read Books
I like to listen instead of reading books.
Onplana··on SparrowMap – Cameras that watch government vehicles
Most of the cameras are showing offline.
Onplana··on Project Online End of Life – Sep 30th, 2026
Check a free tool to see migration preview here. https://onplana.com/tools/migration-preview
Onplana··on Project Online End of Life – Sep 30th, 2026
Onplana is an alternative to Project online.
Onplana··on GrapheneOS user reported to authorities for using GrapheneOS
The question is which category of justice does it qualify?
Onplana··on CSS-Native Parallax Effect
I was expecting a demo on the linked page itself. Interesting to let Codex or Claude Code do it :)
Onplana··on Incident with Actions and Pages
Is it about funds? Why Github is not catching up with the traffic? I know there's a mass rush on Github recently specially due to Claude Code leading users to use Github. sometimes even persuasive.
Onplana··on Antigravity 2.0 Tops the OpenSCAD Architectural 3D LLM Benchmark
Going to try it. just downloaded. will see how it is compared to Claude Code
Onplana··on GitHub confirms breach of 3,800 repos via malicious VSCode extension
If they tighten up things, it would impact the ease of use.
Onplana··on Dumb ways for an open source project to die
A pattern that's gotten worse in the last year or so: drive-by PRs from third-party "security scanners" trying to plant their badge in your README. Got one last week — single-line diff adding a markdown image link back to their scanning service, with a body formatted as a "94/100 Verified Safe" audit report. The "high severity finding" they flagged turned out to be the section of our README explaining how we defend against prompt injection. They were scoring legitimate documentation as a vulnerability so the report would look thorough.

The economics make sense if you squint: each accepted PR is a permanent backlink on a real OSS repo, and most maintainers don't have time to review carefully. Close one, see five more.

Combined with the Dependabot avalanche (a small repo I check in on has 15+ open dep bumps, half with stale merge conflicts because they touch the same workflow file), the modern maintainer tax isn't writing code — it's triaging bots and growth-hackers who treat your contribution policy as an SEO funnel.

Zero-dep philosophy doesn't fully escape this; the PRs come for your README badges and your transitive scanners regardless.