blackle mori

@jk we're in a real grandmother perturbation moment

@hellgnoll_firstletterless@slime.global we tried one of those dorito chips, the ol' rodentpuppy of mine didn't like them, but I thought they were just fine

@jk also josef, appropos of nothing I think you would enjoy the posts made by this user named "@grobiansyboe.bsky.social" on bluesky. they tickle me in a similar way that yours do

@jk I forgot about superthoughts

@nolan@toot.cafe I tried to leave a comment on this, but wordpress seems to eat my comments, so I'll send it here: I still use Pinafore as my main fediverse client. Not Semaphore, not Enaphore, and not any other fork that was made since. Admittedly, part of why I still use it is because I don't want to go through the admittedly easy process of logging into my accounts again. But the other reason is sentimentality. Pinafore, in my opinion, is the best fediverse client. I think that, becuase it the product of being very mindful about what should or shouldn't be used in the code, what features should or shouldn't be implemented, and even just the simple fact that the person who worked on it cared. You showed that you cared by maintaining it. By adding accessibility features and performance improvements. I think you showed care through your labor by making pinafore run well on KaiOS—I still remember that, I think that was cool as hell. I still remember the first of just two small commits that I contributed to pinafore. This was to allow you to switch instances quicker by adding a "star" button to each item in the instance list. You took the time to review it, even fixing my code after merging, and made sure I was credited in the release notes. I've contributed to a number of FOSS projects, usually drive-by commits, and very few of them have been as welcoming as how you'd managed pinafore. That sticks with a person. Sure, maybe in six months I could vibe-code my own pinafore. Maybe I could do that now. But I would never have met you, and you would never have met me. The craft gave us the opportunity to work together, however briefly, on something shared. I think that matters. I got to see what kind of developer I want to be in you. I want to value performance and accessibility. I want my open source projects to be welcoming and enriching to whoever contributes. I want to learn from others what their wants and needs are for software, and to work with them to make that shared vision real. I just don't see how we'll ever be able to achieve this if all we're doing is toiling, quietly and alone, in front of an LLM's text prompt. I don't know how we can ever learn what is valuable, what we should even type into that text prompt, if we hadn't already done some of that menial labour ourselves. I don't know how we could ever learn what matters if we don't talk to each other, work with each other, raise each other up, etc.. etc.. All I really want to say to you is this: don't lose sight of what code actually is. It is a model of reality. It's a representation of our wants and needs. You can't make a model of reality if you don't know what reality is, and we only have two eyes and two ears, and there's much more to reality than we can ever observe or experience ourselves. We have to learn from each other, learn how to listen, learn how to distill all those wants down into code, into those sets of instructions for the silicon to run. That is the craft. And you can't do it alone.

hey it's me!

Bored? Why not play around with this web-based drum machine I made which uses randomly-generated opus audio codec packets to procedurally generate samples! https://suricrasia.online/opus-databending-drumkit/