What is Nostr?
nielliesmons / Niel Liesmons
npub149pā€¦722q
2025-01-14 20:04:22
in reply to nevent1qā€¦8t88

nielliesmons on Nostr: Once you allow people to target/publish 1 event in multiple communities (i.e. ...

Once you allow people to target/publish 1 event in multiple communities (i.e. relays), you get a super high signal graph of your network for free, in the most efficient and targeted way.

An example, to answer some use case questions:
Danny the dev publishes a photography app release in a set of photography communities + a community that's all about using Kotlin for cool FOSS apps.

ā“ What replies should an app display by default?
šŸ‘‰ the ones one the relays (communities) were this app release was targeted (and accepted!)

ā“ What's a efficient and useful way to define and calculate the npubs in "Your Network"?
šŸ‘‰ following + contacts + active npubs in communities you yourself are active in.

You don't save everyone from every telegram group you're a part of as a contact, but that doesn't mean those profiles aren't epic useful for quick and targeted filtering use cases.

ā“ What (photography) books should a book app recommend to Danny the dev?
šŸ‘‰ the books that are valued by his photography Network

How do you know what his photography network is? Danny can select the relevant communities in two clicks or you can fairly detect topics based on the tags/categories of the communities themselves.

How do you know what's valued? It's whatever is being zapped/replied to OR literally is being stored in the communities (relays) themselves.

ā“ What apps should Zapstore recommend by default?
šŸ‘‰ similar to the previous use case, but with an extra focus on the app releases that are stored in the communities he's a part of
Author Public Key
npub149p5act9a5qm9p47elp8w8h3wpwn2d7s2xecw2ygnrxqp4wgsklq9g722q