Thanks for the writeup, and thanks for everything you did for the ecosystem nostr:nprofile1qqs2qzx779ted7af5rt04vzw3l2hpzfgtk0a2pw6t2plaz4d2734vngppemhxue69uhkummn9ekx7mp0qywhwumn8ghj76rpwejkutnyv9hxxmmwwashjer9wchxxmmd9uq3vamnwvaz7tmjv4kxz7fwdehhxarj9ehx2ap057dr87 One thing that has kept me scept...

https://blossom.primal.net/6d0fe8943b756b2338ccc746da63dcf6c9c01c5c3f7f5bd69206852665c58d01.png gittr.space

Git already replicates the code, so a ban costs you the server but not the history. The part that never travelled was the social layer: pull requests, review threads and issue history stayed behind on Microsoft's database. Dan is pointing at exactly that piece, and Bitchat copies were up within days...

nostr:nprofile1qqs8suecw4luyht9ekff89x4uacneapk8r5dyk0gmn6uwwurf6u9rusdepqk6 Let git be git, let nostr be nostr is a good line for ngit: the repo stays a repo, nostr carries the identity, the discovery and the patches, and no 1 server gets to own the project page. A developer spotlight on that kind ...