There’s better ways to do this already built into HTTP.
HTTP: The Protocol Every Web Developer Must Know—Part 1
Learning the fundamentals of the World Wide Web is crucial, especially if you are planning to build web apps. And HTTP is at the heart of any web application you could build. HTTP stands for...
HTTP Semantics
The Hypertext Transfer Protocol (HTTP) is a stateless application-level protocol for distributed, collaborative, hypertext information systems. This document describes the overall architecture of HTTP, establishes common terminology, and defines aspects of the protocol that are shared by all versions. In this definition are core protocol elements, extensibility mechanisms, and the "http" and "https" Uniform Resource Identifier (URI) schemes. This document updates RFC 3864 and obsoletes RFCs 2818, 7231, 7232, 7233, 7235, 7538, 7615, 7694, and portions of 7230.
Marque · Your name, on the open web
Domains for your next idea. Built on the AT Protocol, made for the open web.
Implement QUIC and HTTP/3 in the browser for WebTransport
Requirements for HTTPS for Local Domains
When connecting to servers on their local network, users are surprised to encounter user interfaces that display errors, show insecure connections, and block some HTTP features when missing a secure context. However, obtaining PKIX certificates for those servers is difficult for a variety of reasons. This document explores requirements for authenticating local servers.
Some notes about HTTP/3
HTTP/3 is going to be standardized. As an old protocol guy, I thought I'd write up some comments. Google (pbuh) has both the most popular ...
mess with dns
It's fun to learn by experimenting and breaking things! Here you can do weird DNS experiments with no consequences if you mess something up.
Max Inden (@mxinden@mastodon.social)
We have an open position for a student worker on the Firefox Networking team in Germany. We work on the full stack, from high level HTTP all the way down to TCP / UDP. Some C++, some Rust. Help us fight for an open internet for everyone. https://www.mozilla.org/en-US/careers/position/gh/8068406/
Important piece of multi-protocol support in browsers! Thanks to much work from Javi, and funding from @ipfs.tech. HEY NOW, settle down - a ways to go: - can only redirect to URLs/paths - no Safari - off by default in Chrome (for now) - only allow-listed schemes unprefixed Step by step...
Javier Fernandez
Blog post about a new Chromium feature I've been working on to allow Web Extensions register protocol handlers just declaring them in the Manifest. blogs.igalia.com/jfernandez/2026/03/24/protoco…
was it loaded via http+dns+ssl? then it's server-first. (which is not bad. but it's not the local-first i want.)
Jake Lazaroff
this looks very cool, i mean that genuinely, but tbh i bristle a bit seeing "local-first" used as a straw man here. of course if your server is the source of truth you can eliminate a lot of local-first complexity — the entire point of that complexity is to avoid a server-authoritative architecture!
