I just shipped a small change I wanted to blog about, because it shows off why building this way matters imo.
There's a sibling app called rpg.actor. It's the RPG-character cousin of rolld: you keep your tabletop characters there, a little pixel sprite and a stat sheet per system, and just like rolld, those characters live as records on your own PDS.
So now, when you visit someone's rolld profile and they also keep a character on rpg.actor, you'll see a slim card under their profile header: their character's sprite, the systems they play (D&D, Cyberpunk 2020, whatever they've got going), and a link out to their rpg.actor profile.
Here's the part I like. rolld doesn't call rpg.actor's server to do any of this. It reads the records straight from the person's own PDS, actor.rpg.sprite for the sprite and actor.rpg.stats for the systems. It grabs what's public on your PDS and link out. If you're not on rpg.actor, the card simply doesn't appear.
Small caveat: rpg.actor's schemas aren't frozen, so I treat this quite defensively. If a field goes missing or a shape changes, the card should quietly render nothing rather than breaking your profile.
I'd love to do more of this. If you're building on ATproto and there's some overlap with rolld, let me know! :)