Article URL: https://vincent.bernat.ch/en/blog/2026-http-over-ssh Comments URL: https://news.ycombinator.com/item?id=49958569 Points: 14 # Comments: 3
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
AI agents are changing the way the web is used. usage limits analytics rate policies usage-based pricing paid routes agent-to-service commerce Instead of treating monetization as a separate system, the economic decision can follow the access decision. Build I'm also working on Wayleave Build to make it easier to create and deploy applications with Wayleave's control layer built into the workflow. The broader goal is simple: Developers should be able to build for an internet where humans and autonomous agents coexist. Why not just use Cloudflare, AWS, Stripe, or x402?
oc-mirror CVE-2026-75939: A Signature Check That Runs in the Wrong Order Red Hat disclosed CVE-2026-75939 on 21 September 2026 with a CVSS v3.1 score of 7.4. The affected component is openshift4/oc-mirror-plugin-rhel9 in Red Hat OpenShift Container Platform 4. The tool that syncs release images, operator catalogs and related content into a private registry can be made to accept a forged PGP message, and the defect is one of ordering. According to the vendor advisory, oc-mirror has a validation order defect when processing PGP-signed release images. The tool performs the signature error check b
This is a submission for the Sanity Challenge, Path Two: Vibe-Code Something Strange A project of mine runs on Railway: frontend, backend, websockets, Postgres and Redis in one place. Then I needed user images, avatars first, that load fast for everyone. Railway's storage buckets are private. Public buckets aren't supported, so every image read means a presigned URL or a proxy through my backend. The usual fix is object storage behind a CDN.
Most developers stop at squishing a JPEG and calling it done. Run it through ImageOptim, drop it into the public/ folder, ship it. Job done. Except it's not — because image optimization in 2025 is a multi-layered problem that spans format selection, delivery strategy, browser rendering behavior, and server-side generation pipelines. Get any one of those layers wrong and you're leaving real performance on the table, even if your file sizes look great.
Discussion (0)
Log in to join the discussion and vote.
Log in