Trust has been the defining constraint on the Web's evolution towards more powerful, more applicative capabilities. In a Web context, the user must be able to safely load any arbitrary URL, to safely click on any arbitrary link. The way in which this is achieved is that the runtime places strict limits on what a Web page can do, which in turn necessarily limits powerful capabilities. Could we get more power using a primitive that places more stringent constraints in what pages can do?
Web Tiles
Tiles are composable web docs and apps that can safely be used in arbitrary contexts and assembled from multiple sources to carry out complex user interface tasks.
DASL: Web Tiles
Tiles are composable web docs and apps that can safely be used in arbitrary contexts and assembled from multiple sources to carry out complex user interface tasks. Their composability, security, and privacy properties make them ideal for use in social media, chat, agents, and malleable software.
Web Tiles as the base for Lexicon Embeds
Now that @robin.berjon.com has released an initial spec and implementation of Web Tiles, we can see how we can use or extend this as a base for Lexicon Embeds. Lexicon Embeds is my label for how to have native ATProto content embed in different apps, from display all the way to interactivity— eg an event post in bsky with an RSVP button. Getting this as a general capability - and getting security and display right - means embeds can function in Leaflet and Bsky and anywhere else, rather than o...
Frontend Minimalism in Action: Do More With Less JavaScript | Peter Kröner | webinale Berlin 2026
HTML Can Do That
HTML has been gobbling up swathes of what used to be JavaScript’s remit. This page lists a bunch of dynamic functionality that we can now achieve with just HTML.
All you need is links
When Tim Berners Lee talks about how he designed the web, he uses an analogy from physics, describing his process as a quest to find “fundamental laws” which can generate a desired system:
New Custom Handlers component for Chrome – make everything intensely
The HTML Standard section on Custom Handlers describes the procedure to register custom protocol handlers for URLs with specific schemes. When a URL is followed, the protocol dictates which part of the system handles it by consulting registries. In some cases, handlers may fall to the OS level and and launch a desktop application (eg. mailto:// may launch a native application) or, the browser may redirect the request to a different HTTP(S) URL (eg. mailto:// can go to gmail).
Why does this new W3C specification matter for the decentrazlized Web
This video explain what FedCM is and why it can be a turning point if we want more Sigle Sign On diversity on the web
The Web Needs a Context Layer Built on a Shared Protocol
Making context a shared protocol, rather than a platform feature, would let readers see competing perspectives anywhere on the web, argue Mallory Knodel, Evan Friedman, and Brad Friedman.
How the small web is creating an anti-slop internet
What is the small web? A new crop of platforms are answering algorithmic fatigue with a return to human-curated basics.
A sufficiently detailed spec is code
Specifications do not address the limitations of agentic coding
An Ode to Links
Writing about the big beautiful mess that is making things for the world wide web.
The 49MB Web Page
A look at modern news websites. How programmatic ad-tech, huge payloads and hostile architecture destroyed the reading experience.
CSP Bypass Search
A tool designed to help ethical hackers bypass restrictive Content Security Policies
We just shipped support for the ugliest part of HTTP: Vary
Vary support is now available in Cache Rules on every plan. You can normalize known negotiation headers, pass exact values through to the origin when those small differences matter, or bypass cache when the variation is too unpredictable.
