Okay I won’t complain about subscription fatigue because it’s only 21sats ffs.
But still a little annoying we can’t arrange/pay/automate such payments from any nostr client I’m aware of.
Also it’s not letting me in 😭
Discussion
I agree about the subscription fatigue. If there was a place to paste a renewable NWC connection string would you use it for a relay? I see coinos can support this.. I may attempt to implement this in the future, though it still depends on the friction of the users having to sign into, or paste their pubkey into my client to manage their subscription, they're viewing from another client and have no interest in that nor are even shown the landing page or etc.
What is the problem you're having? Is the payment not working?
Yeah it would be good to have some sort of standard so clients could show payment options from within their interface.
I am not very found of NWC into relays because of the not so subtle “commitment” to a specific set of relays.
If we think about nostr as a p2p protocol (because permissionless npubs and such), relays should be “mere concierges”, so maybe the client should arrange relay payments in the background for the user instead (you already have a wallet setup for sending zaps after all).
As for nostr21, I had some heisenbugs but the payment went through. Turns out it was showing me the wrong relay url in some places of the UI: wss://nostr21.nostr21.com instead of just wss://nostr21.com.
albyhub has zap planner, which lets you schedule lightning payments using an NWC string to lightning addresses at specific intervals. It also ha a field to put the recipient so I suppose one could put their npub, then the receiver would know the sub is paid.
this is not client integrated which would be ideal, but seems like a tool client and relay devs could utilize for the function.