The problem with social media of any kind is that we by default become politicians in a lose-all game of popularity, spiraling into a race to the bottom.
Nostr can change that but not by trying to fit the protocol to social media. It's the right primitives used in the wrong way and it is destined to fail.
What we need is strong communities forming resilient networks, with easy forking/exit guarantees.
As for specs NIP29 and 72 were close but not quite there. I am betting hard on #communikeys from now on designed by @Niel Liesmons , slightly tweaked and extended to my taste. The most important primitives are in place, now testing moderation features and adjusting #BudaBit to this spec.
You can already start a community at
to or look at the BudaBit community:
ncommunity://0a8ecba4868c13e1e84cc5cb58c02c1fd0880d9e5a25a5050ee96ad8a166d7c8?relay=wss%3A%2F%2Frelay.primal.net%2F&relay=wss%3A%2F%2Fnos.lol%2F&relay=wss%3A%2F%2Fbudabit.nostr1.com%2F&relay=wss%3A%2F%2Frelay.damus.io%2F
Budabit
Budabit
Social Git collaboration on Nostr
But Bluesky is not sleeping on this, they have been building out 'tangled' - social software collab similar to #gitvianostr .
And they recently got a funding boost as well:
The problem exists, and we got the right primitives to answer the need:
- NIP34
- Grasp
Some clients:
- 