William Casarin

this spec doesn't claim to solve the spam problem on nostr. you can recover a simpler version of nip29 communities with this spec if you have a community id anchor...

> We might just call it something else to avoid confusion not against that. something along the lines of namespaced discussion groups? not sure what you would call it. distributed...

the community name can just be the hashtag/namespace. then this can be scoped to a relay: to: #[email protected] cc: [email protected], nprofile...., #bitcoin@* (or simply #bitcoin, sends to users outbox relays)...

> The issue with `#[email protected]` is the dependency on the relay url forever. If the community moves to a new relay, things break/are not as easy to load. > >...

so in this setup you could follow global communities #bitcoin o > communikeys is there a spec for this somewhere so I can compare?

> `#bitcoin@nprofile1`? so that you have a hint for the outbox relay of the key at the time of singing, while also having the key to search for the new...

I’m just gonna make nip05/explicit relay urls at the base of this protocol to simplify outbox logic, since theres no real accepted way to get relay lists in a distributed...

its not fixed

you can just create a note in the future with nostril or nak to test

if you send me your database in `~/Library/Application\ Support/notedeck/db` I can debug