Better ?nostr=PUBKEY because referrer is often used by other scripts.

But it is still doubtful to do so - automatically adding parameters to URLs that do not process these parameters is a bad practice. And what if, without the user's desire, his #Nostr public key goes where he would not like?

Reply to this note

Please Login to reply.

Discussion

I've just read it again. Do you suggest adding a link only for BTCPay or LNBits links by their extensions? Then there's nothing wrong with that, of course. I thought it was about auto-adding parameters to any link via the Nostr client. I haven't quite understood the whole proposed scheme yet :)

The basic idea is dead simple payment for word of mouth (Nostr) referrals.

I actually don’t care how’s it’s implemented. The root idea was that I can post a link to a service (like Snort Premium, etc) with a checkout, where my link has a reference to my personal pubkey. Could even act like a coupon code and give a discount.

Then post checkout, and if that service gives referral rewards, that service can split or give a referral fee to that Nostr pubkey, as a referral payment reward/benefit. Use the Nostr pubkey (or other bech32 format with relays) to lookup their LNUrl Pay details - so it’s more dynamic.

Also, I don’t propose it gets auto-added to all URLs. There are privacy considerations too.

However a service can give you a referral link to share. But it can also be predictable too.