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