Post

And the first such protocol, Data Passing: dasl.ing/tp-data.html. This is to pass structured clone data between tile and host. It provides a simple protocol to do that, as well as a model for other protocols that will also pass data (which they will).

The latest @dasl/tiles libraries already support this: npmx.dev/package/@das.... Notably, the webtil.es tile loading source supports the data protocol, so anything that embeds on that basis can use it right away.

If you want to play with the data protocol, you can use Blastile 💥💥💥: tangled.org/robin.berjon.... It's a (vibed) deno desktop app that can run local tiles, watch a directory to auto-refresh a tile as you're building it, emulate passing data, publish a tile to AT, etc.

Do you have concrete use cases? I can't think of any I could not implement with an intents-like system. Unless this is to accommodate the limitations of current web hosts?

Of passing data to tiles? Yeah, plenty!

But do you need an explicit channel with the host? That's what I'm not convinced about. This also makes the threat model harder to reason about because how open ended this looks.