Nostr Web Client

I think I'm getting the picture. What about an optional field to whitelist clients that you want the community content to be surfaced by, or blacklist those you don't? Obviously a blacklisted client could still surface the content but then there'd be no arguing that the client is going against the will of the community team.

Niel Liesmons 9mo ago

Yes, that's :110percent: what I'm describing yes.

#communikeys is all about being very transparent about:

- the content types the community handles

- the conditions for publishing those content types

- having a "global" state for the community

- the apps it recommends for all these content types

- the apps it doesn't recommend

On top of that, the apps themselves will publish the other apps they do or do not trust too. And they will publish the exact specs they use.

Imo, this is how you defend yourself against the obvious scam + spec disrespector attacks that Nostr is still wide open to.

Reply to this note

Please Login to reply.

Discussion

Garbage nsec 9mo ago

Makes sense. If a community is large enough that'll also give it some good leverage with clients, which adds some much needed balance.

Niel Liesmons 9mo ago

Yup. Why it makes for me to build Zapchat on a design package that allows me to brand / adjust it to Communities willing to pay for it.