DanConwayDev

thanks for your help @sectore. I reintroduced `match_event` eventually. PRs and Issues are being managed on nostr now. see https://gitworkshop.dev/r/naddr1qqzxuemfwsqs6amnwvaz7tmwdaejumr0dspzpgqgmmc409hm4xsdd74sf68a2uyf9pwel4g9mfdg8l5244t6x4jdqvzqqqrhnym0k2qj

Here's an alternative approach. Instead of including the pubkeys in the `d` identifier, include them as an array in the in an `owners` tag. Benefits: 1) allows new owners to...

> Counts are mostly irrelevant because, ideally, clients should not rely on a single relay to download information from. And if Clients get two counts from separate relays, it's impossible...

I raised an issue on the NoStrudel repository regarding thread. This scenario should be included in these test vectors: https://njump.me/nevent1qqs8l36pryz6qxrhgx542me7nrp55wvafvy74cgj3dwsxxeey9d5x8gpp4mhxue69uhkummn9ekx7mqzyzsq3hh327t0h2dq6matqn5064cgj2zanl2stkj6s0lg4t2h5dty64ytpru

Can't you just check for a relay running on `localhost:4869`? That's the port both Citrine and https://github.com/CodyTseng/nostr-relay-tray run on.

the one on `4869` would be the primary local relay but apps could support a custom local relay and store this as a local setting in the app.

@vitorpamplona, your right, I updated it to reflect your suggestion. Less updates to the announcement event would be preferable. There may be a scenario where the author wasn't to stop...

I previously wrote some code that listed a number of `` as additional values in the `refs` tag. This improves the UX when the state event is ahead of the...

listing additional maintainers in the `announcement` event signals trust in the `announcement` and `state` events they publish against the same identifier. clients should fetch events published by all of these...

> > ```js > > ["refs/heads/master", ""], > > ["refs/tags/v1.0.0", ""], > > ["HEAD", "ref: refs/heads/master"], > > ``` > > Either way is fine to me. This looks more...