Rust: subtyping, variance and coercions
The past few weeks I've wanted to do a little post on subtyping and coercions in rust and how the difference between those two might make some type relations a bit confusing for many a novice rustacean coming from a language with less restrictive subtyping. With the exciting news of !, the never type, getting stabilised* (go thank waffles and everyone else who has been involved with that!!) I have the perfect excuse to do so! Especially since I've already seen a bit of confusion around what the never type actually, technically is. This is a bit of a "I think you should know this stuff if you write rust" moreso than a coherent message or opinion i want to convince you of. Trying to strike a more educational tone than this blog usually does ... also I just want to ramble about this stuff cause it's cool.
You don't need nixpkgs overlays
no seriously
atproto and IPFS
that damn block size limit ...
Tests vs Checks: CI/CD task type theory
CI/CD has become a standard tool in every modern software developers day to day experience. We demand a lot from our CI/CD systems! and our software is all the better for it. But I think a lot of us have a slightly under-principled way of talking and thinking about it. Specifically I want to talk about how we tend to lump two very different types of tasks under the banner of "tests" or sometimes we don't even talk about one of these types of tasks but we still have them sitting in our pipelines and workflows and what have you.
Account delegation for atproto: orgs, aliases, alts and more
Organisational accounts are something that keeps coming up from time to time in the tangled discord. Way back when in the somewhat early days of tangled during and since September and November of 2025* I came up with what I think is the way forward for org accounts on atproto in general: Account delegation. Fast forward to today and I've managed to nerdsnipe the lovely Lewis into implementing my idea in Tranquil and I now co-maintain Tranquil with him! Not only that, we actually use account delegation for the tranquil.farm org account! So I want to take an opportunity to flesh out the idea in one place that people can reference, as well as try and get a few more eyes on this and, I hope, blaze the trail a bit more for this kind of account becoming a more generally supported feature.
Identities, accounts and profiles
Profiles and specifically global profiles are a thing that atmosphere devs have discussed over and over again. We all agree that there is an issue here but people seem to disagree what to do about it. So I've come to settle this once and for all with the one true, correct opinion! ... err no of course not. But I figured I'd throw my perspective into the ring as I feel there are some things that the discussion has been missing.
The AT Protocol has an authorisation issue. Part 1
atproto has an authorization issue. Not in the traditional sense, we have OAuth and service auth and they work great! but for the case of app level actions taken by making records.
A varied ecosystem and terminology.
As soon as you have an open protocol you will have an ecosystem building up around it, and soon as you have an ecosystem you have people doing stuff differently. This is especially true when dealing with an open protocol built on a set of distributed pieces working together to create a whole.