Pleopods Weekly #23 — August 14, 2026

This Week on Lobste.rs

Trending topics: rant design release vcs privacy

1. tl;dv (Too Lazy; Didn't Validate): 181,874 Meetings Left Wide Open privacy security

submitted by yoelcabo — 187 points (+160 this week) — 47 comments

A researcher discovered tl;dv's Firestore database was wide open, allowing any free user to see 181,874 meetings from government and corporate accounts across 35 countries and crash live calls, but the CTO ignored six months of escalation attempts.

2. I'm leaving OpenAI to build Jurassic Park satire

submitted by j11g — 156 points (+139 this week) — 16 comments

A sustained satire using dinosaurs as the solution to AI misalignment to expose the logical gaps in actual safety discourse and startup pitch frameworks.

3. I'm done using AI rant vibecoding

submitted by untrusem — 137 points (+115 this week) — 78 comments

A 20-year programmer tried AI coding tools seriously for a year, then quit: velocity went up but so did autopilot mode, and he stopped absorbing how things actually work. He also got a jolt when the chatbot confidently handed him incorrect medical advice that landed him in the ER.

4. How Tailscale helped find the SQLite WAL-Reset bug databases

submitted by pushcx — 124 points (+114 this week) — 13 comments

Tailscale spent six months debugging random database corruption before learning the bug lived in SQLite's write-ahead log reset logic, not their own code—a discovery that only came after getting the SQLite developers involved directly.

5. i wonder if you could make a useful DOS executable with just emoji retrocomputing

submitted by thisalex — 114 points (+109 this week) — 11 comments

Someone reverse-engineered a working DOS .COM file built entirely from emoji characters — UTF-8 emoji bytes happened to encode valid x86 instructions, a collision exploit more than clever design.

6. Toggles Considered Harmful design

submitted by wezm — 104 points (+97 this week) — 35 comments

Toggle switches look neutral by design, which means they fail at the most basic job of a UI control: making the current state obvious without prior knowledge of the convention. The post walks through why this matters and what works better.

7. Am I the problem? Interviewing another team to find out practices

submitted by cetera — 101 points (+96 this week) — 21 comments

The author went looking for dysfunction at ngrok's infrastructure team and found something more unsettling: a group that actually disagreed on technical merits, understood each other's positions, and resolved it without drama—which made him reconsider his own team's conflicts.

8. The "Disability Dongle": Why Silicon Valley Hates Me and you a11y rant

submitted by FedericoSchonborn — 145 points (+95 this week) — 22 comments

A disabled engineer argues that tech's obsession with accessibility products misses the point: the industry doesn't actually want to hire disabled people in the first place.

9. The Nixpkgs core team has disbanded nix

submitted by kevinc — 105 points (+95 this week) — 16 comments

The Nixpkgs core team quit after ten months, citing a Steering Committee that either micromanaged their work or disappeared entirely—creating a governance structure where conflict pays better than collaboration.

10. They don’t make ’em like Sublime Text anymore editors

submitted by diktomat — 104 points (+91 this week) — 53 comments

Sublime Text does one job without the constant churn — no forced updates, no release notes theater, no AI sidebar begging for attention — and that simplicity has become genuinely rare enough to feel transgressive.

11. Chicken Scheme 6.0 released lisp release

submitted by eatonphil — 85 points (+82 this week) — 7 comments

Major overhaul toward R7RS compliance and UTF-8 everywhere: strings are now UTF-8 by default, process operations return proper objects instead of bare PIDs, and whole swaths of the API have migrated to standard modules (with several legacy ones removed). The build system switched to autoconf and the mingw support now requires POSIX utilities — a breaking change that trades flexibility for simplicity.

12. a pure css implementation of some sunlight streaming in through the window css design web

submitted by juliethefoxcoon — 88 points (+81 this week) — 6 comments

Builds convincing sunlight and shadow effects using layered CSS blur masks, SVG displacement filters for leaf motion, and a homography matrix to skew the light as it transitions from day to night—basically solving for a perspective transform the hard way because CSS's affine transforms weren't enough.

13. Tracking down a Zsh history data loss bug debugging

submitted by stapelberg — 74 points (+73 this week) — 15 comments

Stapelberg uses inotify, fatrace, and bpftrace to track down why his Zsh history file kept losing years of entries — and finds that the winning move was patching Zsh itself to crash loudly so he could analyze the core dump and see exactly what went wrong.

14. some software talks i like programming

submitted by hugoarnal — 89 points (+72 this week) — 18 comments

A curated collection of talks on how programming jargon shapes thought itself—tracing concepts like "complect" through layers of system design to show why the words we use for complexity actually matter.

15. Who Should Pay For Source Code Availability? vcs zig

submitted by hugoarnal — 89 points (+72 this week) — 54 comments

GitHub's outages aren't the real issue; the architecture is. Radicle flips the model by making repository hosting a peer-to-peer network where participants seed the code they depend on, distributing infrastructure costs instead of funneling them to a single company.

16. IRC technology news from the first half of 2026 networking

submitted by donio — 87 points (+72 this week) — 15 comments

IRC's still picking up steam in 2026: IRCv3 is adding AI disclosure markers to flag lazy implementations, while the community's focusing on practical wins like mobile UX, WebSocket support, and threaded replies.

17. I hate packaging my software for Linux linux

submitted by mtlynch — 101 points (+70 this week) — 83 comments

One developer tried to ship across 15+ Linux package formats and hit a wall anyway—deb demands bundling dependencies, AppImage runs slow, Flatpak's sandbox broke their TUI tool, and AUR went read-only right when they needed it. The fragmentation problem isn't theoretical.

18. Dithered QR codes art graphics

submitted by lyall — 76 points (+69 this week) — 3 comments

Error-diffusing QR codes spreads quantization error from the forced data pixels into surrounding areas, keeping the embedded photo readable instead of noisy — you lose some error correction but QR codes have enough redundancy to handle it.

19. jujutsu 0.44.0 release vcs

submitted by olex — 72 points (+69 this week) — 32 comments

Jujutsu stabilizes tag support with some breaking changes: remote tags now track locally by default, and jj git push --all now includes tags alongside bookmarks.

20. A shell exclamation mark is not for yelling. Be lazy unix

submitted by seb — 74 points (+67 this week) — 54 comments

The ! syntax in your shell has layers beyond !! — you can extract specific arguments from previous commands, modify paths on the fly, and compose chains without retyping, which adds up to real ergonomic wins if you're at the terminal all day.

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