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