And #communikeys fixes the Njump scenario.

Since you can see where the publication was targeted, you can already display it in the web App(s) the involved Community(ies) recommend and skip the need for a one-site-fits-all approach (njump) entirely.

Reply to this note

Please Login to reply.

Discussion

Do you have an example event for #communikeys? I could publish one for theforest and then you'd have another a realistic example.

Right now we just have the "k" tags per content sections.

But that's not fine-grained enough for Replies (freaking kind-1s) and Indexed Text (30040).

nostr:naddr1qvzqqqrcvgpzp22rfmsktmgpk2rtan7zwu00zuzax5maq5dnsu5g3xxvqr2u3pd7qydhwumn8ghj7argv4nx7un9wd6zumn0wd68yvfwvdhk6tcpr3mhxue69uhhg6r9vd5hgctyv4kzumn0wd68yvfwvdhk6tcppemhxue69uhkummn9ekx7mp0qqrxu6ts943kxwstwsx

We're going with a new "c" tag for category.

Yup noted that!

If you have a The Forest npub:

1) go to Chachi (with that nsec/signer) and start a Community with whatever content sections (and fees, etc...)

2) send me the link and we'll have fun 😉

Okay, I'll try that. Maybe tomorrow. Need to go to bed. GN

Same here :zzz: