Thread - Nostr Hypermedia

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

Budabit

Social Git collaboration on Nostr

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

Replies (3)

Niel Liesmons 2 months ago

What did you tweak? I'm still very very open spec-wise. Most up to date is here (with many probably dumb stuff in there still, especially not sure about the whole profile list thing): https://www.chateau.community/wiki/naddr1qvzqqqrcvgpzqesd33ux28msfplvnwxac2p7988j2ctf8hdrhgjx607nczxmkuyrqq8kummnw3ez6cm0d4kh2mnfw3useql3jw Only thing we're doing with Zapstore for now is: - having a keypair as the ID for communities - targeting stuff at ID directly with the h tags Moderation and white listing is still pretty much server+side and will become more transparent as we go (and as we are are more sure about how to spec it).

1 replies ↓

Five 2 months ago

Thanks for the link! Tweaks: - I use profile lists plus reactions on approval forms for content section permission accounting, no 'badges' tag. I use badges for driving engagement but not perms - I layer explicit kind 1984 reporting as event or person-bans (from admin or moderators) Otherwise plumbing is there for targeting but ux needs some thought still. Especially with repos I find it easier to just target directly with the h-tag for now (not yet implemented) but those are replaceable so this can be pivoted later on

1 replies ↓

Niel Liesmons 2 months ago

Yup, we're doing direct h tags in the app events too. An extra event doesn't really make sense. 99% of what you want to target at more then one community is replaceable.