Leaking pixels: cross-site data vapor

UpdatedMay 12, 2026

•1 min read

For the past several years I built and ran Better Than Unicorns (immersive/XR collaboration). That meant I did the whole thing: prospected, sold, onboarded, set up accounts/devices, ran live sessions, troubleshot remotely, built enablement, monitored engagement, and turned feedback into product improvements. I am at my best in the messy middle where customers are excited… and the reality of rollout, behavior change, and technical friction shows up.

Part of seriesdarketype devlog

The problem

My portfolio needs to be professional, but my soul is chaotic. How do i bridge the gap without scaring off recruiters?

The solution

CSLP (Cross-Site Leakage Protocol). A localStorage handshake.

If you play long enough on the portfolio, you get "infected". The infection creates "vapor" (particles) that mutate from binary to "darketype" text. Eventually, physical pixels accumulate on the edges of your screen.

The glitch

When you move your mouse near these accumulated pixels, your cursor starts to disintegrate. It's a subtle warning: you are too close to the edge.

Code note

Doubled the proximity check to 300px for a wider "danger zone" and slowed the jitter transition to 0.3s to make it feel like the pixels are breathing rather than seizing.

View this post with the full interactive/glitchy experience on darketype.

#cslp #glitch #localstorage

Comments

Join the discussion

No comments yet. Be the first to comment.

darketype devlog

Part 23 of 25

the design lab. HUDs, chromatic experiments, particle systems, pixel manipulation, and the visual tools i build because i can't stop thinking about how interfaces should feel. this is where the weird creative code lives — per-character effects, viscous LCDs, OG pictogram generators, brett-hud, the melt. i ship these because building them teaches me something i couldn't learn any other way.

Up next

The loop engaged: v0.1.1

The problem The portfolio was static HTML soup. The darketype was a ghost town. We needed to connect them. The learning Building a "universal reader" (entry.html) that fetches markdown via JS is way faster than building a complex SSG for now. It feel...