5 posts
Web
tuios in a browser: tuios-web, sip and the browser client.
6 min readPerformance, Web
Most of the page was four fonts
A first visit to a sip page moved 11.7 MB. Most of it was four TTF files that nobody had compressed. WOFF2 and gzip took it to 4.4 MB, and dropping a fallback that no browser could reach took the binary from 30.1 MB to 24.6 MB.
7 min readWeb
The shell exited, and Firefox opened a new one
Over WebTransport, a sip session that the program ended came back as a fresh shell in 4 runs of 6. The server's last frame was a STOP_SENDING that one of my own September fixes had added, and Firefox threw away the close message it had already received.
4 min readRendering, Web
My multiplexer lied about what it could do
kitty icat drew nothing when tuios ran in a browser client, because the graphics passthrough said yes to file transmission without asking the host.
7 min readRendering, Web
The bug I closed three times: a speckled sprite in a WebGL terminal
A speckled sprite in the tuios browser terminal. Three wrong closures, a test suite blind by construction, and a browser that salted its own pixel readback.
5 min readRendering, Web
I ported a correct emoji width table and it fixed nothing
Emoji widths were wrong in the tuios browser client. I ported ghostty's per-codepoint width table and nothing changed, because a terminal gives width to grapheme clusters, not to codepoints.