Put it on general for now :(
We are still figuring out how to place this one.
nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z slight issue configuring relays for filter.nostr.wine
The relay is pay-to-read and pay-to-write and it broadcasts notes to public free-to-read relays
If I put it in Home which is outbox (I think) then others will try to read from it
So another section, home-but-not-outbox?
Wondering if NIP-65 needs more flexibility
Discussion
Thanks 👍
If Amethyst can be configured to work with filter.nostr.wine as intended, i.e. it's the only relay Amethyst reads from and writes to, this contradicts NIP-65
"When broadcasting an event, Clients SHOULD:
Broadcast the event to the WRITE relays of the author"
So the client choice is either
a) ignore the recommendation and support proxy/aggregating relays
b) follow the recommendation and break the use case
Clients making different choices will make global configuration impossible
=> seems NIP-65 is broken, can't work with aggregating/proxy relays and can't support global configuration of paid-for (auth-to-write, open-to-read) relays