Developers publishing their workspace layout, skills, prompts, and agent configuration is going to be the new dotfiles pattern and trend.
@johnandersen777.bsky.social Ay what you doing over here lexicon.garden/identity/did...
How long does it generally take for spindle members to become indexed in @tangled.org? Have a spindle registered and verified that on the spindle-side the added members show up, but I don't see them on the site's spindle config and the spindle isn't listed on repo creation.
I'm good 👀
🎲 You rolled an 11 — A worthy find awaits.
📦 COMMON FIND!
You found: a stylish cape 🧥
⚔️ Strength: +7
You are currently a Huorn of Fangorn 🌳 with an Elven Cloak of Lórien 🧥
⚔️ Strength: +25
🍀 Fortune: +1
💨 Speed: +2
Can do, at some point I should just publish the ansible configuration that I'm using for @lexicon.garden infra.
Yeah, I’ve been a big supporter of the idea that a critical missing piece to the lexicon schema is the concept of an interface or trait. I want to say that a shape is “event like” or “post like” and use that as a lens to view / transform other records types through.
This is a great read, thanks for posting it and also open sourcing it.
I've got a similar workspace layout and I'm kind of feeling inspired to post about it too.
I don't think it's likely to happen or as doom and gloom. There are plenty of examples of online communities (forums, Reddits, etc.) that have the ability to be fully private and aren't.
So like, is that bad? I think AT Protocol has several different goals:
1. public microblogging
2. identity and data ownership and mobility
3. data interop
4. permissioned-data and privacy*
Those three goals don't actually align with each other and exist in there own trajectory.
I don't think a whole MCP is needed, but maybe some skills for specific workflows?
The idea of doing a small, virtual lexicon schema-focused event called LexiConf has been floated a few times.