I know the server is usually the dom but something about being a client and binding all these globals feels so good. like no, dear compositor, you're my bitch and what I say goes. bind this, release that, destroy this, and create that. as long as I follow the boundaries set by the wayland-protocols contributors, I can do whatever I want to you~. you don't get to have a say in the matter. but what's that? their repos are down? you can't find the boundaries? I guess that means I can get a little frisky this week~. you want my windows gone? tee hee, too bad, they're all mine and you can't do anything about it. I'm gonna bind all your interfaces so good and you can't stop me. you don't even want to stop me, because I'm not sandboxed or in a security context; I can even bind your most intimate and privileged protocols and play with them to my heart's content. oh, why don't I ever commit my surfaces? well, maybe I'm just somewhat of a tease ~. maybe I just like teasing you without ever providing any contents, so you can never "present" anything to our dear user, who watches me absolutely violate your socket but not enough for you to disconnect me. and the user likes to watch. because the user started my process, after all. I bet the user knew all about my behaviour, and that's why they downloaded me and told me to interact with your registry after all~. and look at you now, so pathetic and nearly OOM with all those globals I've bound and force you to keep track of. just for fun. I don't even know what half of these do, but I do love the look on your face when you don't have the capacity to think of anything else, other than me.

💣 <- flirting

"the internet of things".