A DOOM vector engine for rendering in KiCad, and over an audio jack
mikeayles.com
Space Truckin' – The Nostromo (2012)
alienseries.wordpress.com
Brand New Layouts with CSS Subgrid
joshwcomeau.com
A new bridge links the math of infinity to computer science
quantamagazine.org
Show HN: We built an open source, zero webhooks payment processor
github.com
The fall of Labubus and the mush of modern internet trends
michigandaily.com
Google Antigravity exfiltrates data via indirect prompt injection attack
promptarmor.com
Trillions spent and big software projects are still failing
spectrum.ieee.org
Reinventing how .NET builds and ships (again)
devblogs.microsoft.com
FLUX.2: Frontier Visual Intelligence
bfl.ai
How to repurpose your old phone into a web server
far.computer
Launch HN: Onyx (YC W24) – Open-source chat UI
Jakarta is now the biggest city in the world
axios.com
Unifying our mobile and desktop domains
techblog.wikimedia.org
1,700-year-old Roman sarcophagus is unearthed in Budapest
apnews.com
Someone at YouTube Needs Glasses: The Prophecy Has Been Fulfilled
jayd.ml
Ilya Sutskever: We're moving from the age of scaling to the age of research
dwarkesh.com
Space: 1999 – Special Effects Techniques
catacombs.space1999.net
CS234: Reinforcement Learning Winter 2025
web.stanford.edu
Surprisingly, Emacs on Android is pretty good
kristofferbalintona.me
The Generative Burrito Test
generativist.com
Constant-time support coming to LLVM: Protecting cryptographic code
blog.trailofbits.com
Show HN: A WordPress plugin that rewrites image URLs for near-zero-cost delivery
wordpress.org
Hi HN,
I built a WordPress plugin called Bandwidth Saver. It takes the images your site already has and serves them through Cloudflare R2 and Workers, which means zero egress fees and extremely low storage cost. The goal is to make image delivery fast and cheap without adding any of the complexity of traditional optimization plugins.
The idea is simple. WordPress keeps generating images normally. The plugin rewrites the URLs on the frontend so images are served from a Cloudflare Worker. On the first request, the Worker fetches the original image and stores it in R2. After that, Cloudflare’s edge serves the image from its global cache with no egress charges. There’s no need to preload or sync anything, and if something fails, the original image loads. That’s the entire system.
I built this because most image CDN plugins try to do everything: compression, resizing, AI transforms, asset management, custom dashboards, and monthly fees. That’s useful for some users, but it’s unnecessary for most sites that just want their existing media to load faster without breaking the bank. Bandwidth Saver focuses only on delivery, not transformations. It’s intentionally minimal.
There are two ways to use it. The plugin is completely free if you want to run your own Cloudflare Worker. I included the Worker code and the steps needed to deploy it. If you don’t want to deal with any Cloudflare setup, there’s a managed option for $2.99 per month that uses my Worker and my R2 bucket. I’m trying to keep it accessible while also covering operational costs.
The plugin works with any theme or builder and doesn’t modify the database. It only rewrites URLs on output. WordPress remains the system of record for all media. R2 simply becomes a cheap, durable cache layer backed by Cloudflare’s edge.
I’m especially interested in feedback about the approach. Does the fetch-on-first-request model make sense? Is the pricing fair for a plugin of this scope? Should I prioritize allowing users to connect their own R2 buckets or the managed service? And for those with experience in edge compute or CDNs, I would love thoughts on how to improve the Worker or the rewrite strategy.
Thanks for reading, happy to answer any questions.