Lez on Nostr: Communities are by nature socially centralized. Therefore the right design in my ...

Communities are by nature socially centralized. Therefore the right design in my opinion is to have its content bound to pubkeys rather than server addresses. The data can still be redundant if community members take care about archival and hosting.
For public communities - like opensource development - this is definitely the way and the data should be widely replicated.
This is a key property of #communikeys.

My humble opinion about privacy is: if you need personally, generate a new pubkey for the kind of interaction you want to be hiding.

quoting
nevent1q…pkpn

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 (nprofile…4s8y) , 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 https://budabit.club 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