Pleopods

Archives
Log in
Subscribe
May 29, 2026

Pleopods Weekly #13 — June 5, 2026

Pleopods Weekly #13 — June 5, 2026

Pleopods
Home Archive

Pleopods Weekly #13 — June 5, 2026


This Week on Lobste.rs

Trending topics: programming web linux rant philosophy


1. omarchy is not a distro linux rant

submitted by j3s — 283 points (+214 this week) — 122 comments

DHH's "omarchy" is Arch Linux plus his personal dotfiles (complete with hardcoded keybinds to Grok and Hey.com), dressed up with conference sponsorships and merchandise—a reminder that influencer branding can make rice configurations sound like distributions.

2. The social contract of writing philosophy

submitted by joladev — 175 points (+161 this week) — 38 comments

The discomfort with AI-written content isn't really about quality—it's about effort as a signal of understanding. When readers assume a human spent time thinking through something, they trust the reasoning differently than they would identical words generated in seconds.

3. Encyclical Letter of His Holiness Leo XIV Magnifica Humanitas ai philosophy

submitted by pyfisch — 125 points (+123 this week) — 68 comments

The Pope's 2026 encyclical on AI and human dignity walks the Vatican's typical line — technology itself is morally neutral, but we're sleepwalking into systems that erode human agency, truth, and autonomy in ways that demand both governance and spiritual resistance.

4. The pressure culture programming

submitted by andrewnez — 178 points (+115 this week) — 36 comments

curl processes so many security reports now (4-5x last year's volume) that Hauff is working 50-hour weeks just to keep up, and he's starting to worry the project's maintainers won't last much longer at this pace.

5. Don't Roll Your Own … web

submitted by susam — 117 points (+107 this week) — 54 comments

GitHub's custom link navigation is slower than native—and that's just the usability problem. The deeper issue is that rebuilding what browsers already do well kills password managers, accessibility tools, and keyboard navigation in one go.

6. What are some of your favourite developer tools? ask programming

submitted by dhruvp — 113 points (+107 this week) — 184 comments

Developers kept listing their favorite tools, but the real debate bubbling up was whether you should spend time optimizing your setup or just accept that the defaults work fine—and whether you even care about that question anymore after your first five years coding.

7. Interview with Zig creator Andrew Kelley video zig

submitted by laqq3 — 119 points (+102 this week) — 25 comments

Kelley discusses Zig's design philosophy, what he's learned from building a language, and where he thinks systems programming is headed — the usual territory for these interviews, but worth hearing directly from someone who's spent years thinking about how to fix C's rough edges.

8. Jira is Turing-Complete compsci

submitted by josephjnk — 102 points (+94 this week) — 6 comments

Someone proved Jira Automation is Turing-complete by building a Minsky machine inside it—using linked-issue counts as registers, workflow states as instructions, and JQL rules as conditionals—then actually ran it on a live instance to compute Fibonacci numbers.

9. Stop advertising in your commits programming rant

submitted by Aks — 84 points (+81 this week) — 71 comments

Tools that sneak vendor attribution into your commit messages by default are doing unpaid advertising while you're paying them—if they want to disclose AI assistance, fine, but git history shouldn't be a billboard.

10. How my minimal, memory-safe Go rsync steers clear of vulnerabilities go security

submitted by stapelberg — 98 points (+78 this week) — 17 comments

When 12 rsync vulnerabilities emerged over 16 months, a Go reimplementation missed all of them—not because Go is safer, but because the author discovered his own validation bugs while studying the originals, and Go's panic-on-bounds-violation caught them before exploitation. A useful corrective on what memory safety actually stops (buffer overflows) versus what it ignores (flawed logic).

11. Gnutella: A Protocol Outliving the World That Created It distributed historical networking

submitted by rickcarlino — 100 points (+76 this week) — 32 comments

Gnutella succeeded not because it was fashionable but because it solved a concrete problem—finding MP3s on home computers with no central server—and the conditions that made it useful (dial-up internet, expensive storage, users willing to manage files) eventually evaporated, leaving behind a ghost network that still runs today.

12. Using AI to write better code more slowly practices vibecoding

submitted by nolan — 78 points (+75 this week) — 42 comments

LLMs are better at catching real bugs in code review than at generating code, especially when you run multiple models and accept that some reviews will blow up your entire approach.

13. Flipper One — we need your help hardware

submitted by strugee — 122 points (+69 this week) — 43 comments

They're building an open Linux cyberdeck (Flipper One) to replace the mess of vendor binary blobs and custom BSPs that plague ARM boards — and they're asking the community to help finish the last bit (that DDR trainer blob), close driver gaps, and ship something that actually boots mainline kernel.org without patches.

14. What is a harmonic? An interactive comic about additive synthesis art education visualization

submitted by suda — 76 points (+66 this week) — 18 comments

When you pluck a string, it doesn't vibrate at just one frequency — the fixed endpoints force it into multiple modes simultaneously, each producing its own pitch. The interactive demos here let you hear how those harmonics stack to create the timbre you actually perceive.

15. Announcing Web Serial Support in Firefox browsers web

submitted by commanderk — 78 points (+62 this week) — 38 comments

Firefox 151 now lets websites talk directly to serial hardware—microcontrollers, 3D printers, power meters—without native apps, though access requires explicit per-port user consent and is gated behind a detailed permission prompt.

16. It's time to talk about my writerdeck linux vim

submitted by facundoolano — 69 points (+62 this week) — 17 comments

A developer revived an old laptop as a distraction-free writing box by stripping it down to a terminal, neovim, and tmux—here's the specific config steps if you want to steal the idea.

17. Atom Exhaustion Is Not a Footgun. It's One Third of Our CVEs elixir erlang security

submitted by pushcx — 66 points (+59 this week) — 47 comments

Over a third of Erlang CVEs are atom exhaustion—a DoS where unbounded atom creation from user input fills the VM's non-garbage-collected atom table until it crashes, lurking in places like Jason.decode(json, keys: :atoms) or URI scheme handling that seemed safely finite until external input arrived.

18. The Eternal Sloptember culture programming

submitted by rcalixte — 63 points (+59 this week) — 9 comments

Six months building AI agents convinced the author they're sophisticated enough to look good while remaining fundamentally unreliable—the real problem isn't the technology, it's that organizations will let mediocre engineers ship unverified output at scale while forcing competent ones to waste time catching mistakes.

19. On the
a11y web

submitted by runxiyu — 59 points (+57 this week) — 15 comments

<dl> maps cleanly onto any name–value pairs you're already using <div> divs for, and screenreaders can actually announce the structure — a concrete win that doesn't require waiting for universal support before it matters.

20. What's cooking on SourceHut? Q2 2026 devops

submitted by kmaasrud — 58 points (+56 this week) — 4 comments

SourceHut spent the last month fighting off DDoS attacks and spam signups (300 fake accounts, mostly Gmail) while shipping deploy keys and standardizing their GraphQL implementation—next they're prioritizing UI improvements and moving billing infrastructure to the EU.


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

Don't miss what's next. Subscribe to Pleopods:
← Newer Pleopods Weekly #14 — June 12, 2026 Older → Pleopods Weekly #12 — May 22, 2026
Powered by Buttondown, the easiest way to start and grow your newsletter.