|
Top-level
 Well the last blogpost was 24 pages printed and took me 8 hours to summarize and this one is definitely shorter, it's only.. oh shit it's 20 pages oh fuck okay I've been awake since 4am and getting this post ready since 5am working 12 hour days lately haha it's no problem I'm gonna need more tea. 9 comments
So anyway. We are going to get into it. And the further we go, the more serious my critiques are going to get. Just because I'm being nice doesn't mean my analysis won't be harsh at points. Nonetheless let's try to be decent to each other. We all deserve that. Thanks. 💜 If you can't tell, my narration style buries the lede quite a bit. So lemme tell you what you can expect up front: - Some fluffier bits I thought were good framing (cotd...) - A defense and analysis of my claim that Bluesky's approach explodes unsustainably ("quadratically") as you try to decentralize it (cotd ...) Oh yeah and just like last time I WILL NOT BE READING NOTIFICATIONS until I get through this Sorry, it's impossible. I'll never get through it otherwise. So see your comments on the other side! So yes, definitely burying the lede, we are now at "Interesting notes and helpful acknowledgements" Bear with me, we'll get to the deeper analysis, but this does help frame things I promise So first of all, @bnewbold was very nice: > I am so *happy* and grateful that Christine took the time to write up her thoughts and put them out in public. Her writing sheds light on substantive differences between protocols and projects, and raises the bar on analysis in this space. Aw thx 💜 WHOOPS I FRAGMENTED MY THREAD CONTINUE HERE: https://social.coop/@cwebber/113647312428959527 |
Gregory's Server
One more meta thing before we get into it. I want to say up front: working on and building systems is deeply personal, and deeply emotional.
We are talking about systems people pour their lives into. Trust me I know.
It's worth doing a critique, but it's also worth acknowledging the human aspect.