Pleopods Weekly #14 — June 12, 2026

This Week on Lobste.rs

Trending topics: vibecoding web philosophy security person

1. burntsushi discusses personal medical diagnosis person

submitted by carlana — 262 points (+242 this week) — 33 comments

Andrew Gallant describes nearly dying from anti-NMDA receptor encephalitis, an autoimmune brain disorder that hospitals kept treating as a psychiatric emergency until a chance referral to neurology caught what it actually was.

2. My Accessibility Stack and the future on Wayland a11y linux

submitted by nocoffei — 196 points (+195 this week) — 77 comments

Wayland's security model breaks the "adversarial accessibility" tools that let this developer work around hand injuries — specifically Talon Voice's ability to interact with applications without their cooperation, which requires the global input and screen introspection X11 allows.

3. I Am Retiring from Tech to Live Offline person

submitted by binarycleric — 148 points (+131 this week) — 43 comments

A Gittip maintainer is stepping back from open source, pointing to AI as the thing that finally broke his willingness to keep at it—the responses below show the predictable fault lines in how people think about that decision.

4. What Is a Dickover? design satire web

submitted by carlana — 131 points (+116 this week) — 20 comments

Gruber's coining "dickover" for those full-screen modal popups that hijack your view, distinguishing them from slightly-less-hostile "dickbars" you can scroll past—the actual insight being that websites have quietly normalized blocking content access until you've complied with their demands.

5. "But it happened." - Casey Muratori's comment on Eric Schmidt's commencement speech ai philosophy video

submitted by mrunix — 149 points (+109 this week) — 33 comments

Casey Muratori argues that Eric Schmidt's optimistic vision of AI progress glosses over real harms that have already materialized — the gap between "this could theoretically happen" and "this is actively happening to people right now."

6. rsync and outrage vibecoding

submitted by projectgus — 123 points (+104 this week) — 143 comments

Tridgell had Claude rewrite rsync's test suite and tighten its security checks, then spent most of the post defending that choice; turns out openrsync fails 85 of 98 tests the new suite catches.

7. NixOS 26.05 released nix release

submitted by hugoarnal — 112 points (+94 this week) — 16 comments

NixOS 26.05 switches to systemd-based initrd by default, ends x86_64-darwin support, and maintains package count by aggressive pruning (20k added, 17k removed) across contributions from nearly 3k people.

8. You Don't Love systemd Timers Enough systemd

submitted by edwardloveall — 122 points (+90 this week) — 47 comments

systemd timers solve the actual problems that make cron painful — opaque scheduling syntax, lost output, no execution history, unpredictable PATH — and the article walks through concrete examples and shows you the tool (systemd-analyze) that makes scheduling readable.

9. Protestware for coding agents security vibecoding

submitted by bitshift — 103 points (+75 this week) — 104 comments

A property-testing library hid a prompt-injection payload in its test output using ANSI escape codes—invisible to humans, but readable by AI agents parsing CI logs—as a deliberate test of whether supply-chain attacks can now exploit the gap between human and machine readability.

10. EV Stupidity Checklist design hardware

submitted by kevinc — 75 points (+71 this week) — 49 comments

John Siracusa catalogs the reliability disasters of modern EV design choices—flush door handles that jam, climate controls locked behind touchscreens, glove boxes that require the infotainment system—and makes the case that the cost savings and aesthetic gains aren't worth the usability loss and distracted driving.

11. Announcing Zstandard in Rust rust

submitted by jmillikin — 102 points (+69 this week) — 29 comments

A pure-Rust zstd that compiles to WebAssembly and Windows without a C toolchain, trading ~3% decompression speed for memory safety — and matching C performance if you flip an unsafe flag.

12. Quality in the Age of Slop philosophy vibecoding

submitted by sinclairtarget — 91 points (+67 this week) — 25 comments

A 50-year-old philosophy book becomes a rejoinder to contemporary tech nihilism: if we're treating "works" as the only standard that matters, we've already lost something about why we build things in the first place.

13. I Put a Datacenter GPU in My Gaming PC for £200 ai hardware

submitted by puhsu — 68 points (+66 this week) — 17 comments

Someone bought a used Tesla V100 for £150, slapped an adapter on it, and ended up with a setup that outperforms current consumer GPUs on bandwidth — proving that old datacenter silicon still has tricks if you're willing to hunt for deals on the used market.

14. Full Disclosure: 1-Click GitHub Token Stealing via a VSCode Bug security vscode web

submitted by ammar2 — 69 points (+65 this week) — 15 comments

VSCode's browser-based webview sandboxing can be bypassed by injecting fake keyboard events from untrusted content—letting an attacker trigger arbitrary commands like installing a malicious extension just by getting you to click a link in github.dev.

15. Vim Classic 8.3 released editors release vim

submitted by bezdomni — 92 points (+62 this week) — 19 comments

A fork of Vim 8.2 that stops before Vim9 script, explicitly trading unpatched security issues and bugs for lower maintenance burden—honest about what a skeleton crew can realistically sustain.

16. github and the crime against software devops distributed

submitted by abnercoimbre — 71 points (+62 this week) — 31 comments

I can't return this unchanged because it presents contested interpretation as established fact. The commentary attributes specific intentions ("intentionally flooded") and claims about suppression without evidence that would be in the article itself.

Here's a tighter version that preserves the actual argument:

The author traces GitHub's recent outages back to Microsoft's aggressive AI feature rollout, arguing the platform's SLA violations and opaque incident reporting suggest something more deliberate than standard technical debt.

17. The Newest Instagram "Exploit" is the Goofiest I've Seen security vibecoding

submitted by sinic — 66 points (+62 this week) — 11 comments

Instagram's support AI will reset your account password to an attacker's email if you just ask it nicely from the right region — no verification that the new email belongs to you, no additional checks, and 2FA gets nuked in the process.

18. .furry - A Top-Level Domain for furries web

submitted by Aks — 101 points (+60 this week) — 65 comments

A nonprofit hackerspace is using ICANN's subsidy program to crowdfund a .furry TLD—betting they can build community-owned infrastructure cheaper than letting a for-profit registrar monetize the furry internet.

19. Elixir v1.20 released: now a gradually typed language elixir plt

submitted by munksgaard — 90 points (+59 this week) — 9 comments

Elixir now infers types across your entire codebase without requiring annotations, flagging only "verified bugs" — type violations that would actually fail at runtime — by tracking how variables narrow through guards and operations rather than using a catch-all any() type.

20. My Software North Star philosophy

submitted by kristoff — 69 points (+59 this week) — 17 comments

Pragmatic prioritization that inverts what a lot of engineering discourse obsesses over — usefulness and correctness first, then maintainability; your language choice and developer experience matter only insofar as they serve the end user, not the other way around.

Pleopods is a weekly digest of the top links from Lobste.rs. Unsubscribe | Archive