I've been noticing for a while that there doesn't seem to be a clearcut (interoperable) way to determine whether a given relay requires payment to post there or not. If you do a lot of manual digging and searching you can figure it out on a relay-by-relay basis but that seems unacceptable from a UI/UX point of view unless we (devs) want nostr to be geek-only.
I think for this issue what's probably needed is some kind of push to make both relays and clients really fully implement the "Server Limitations" (at least), and also the "pay-to-relay" blocks from the "extra fields" in NIP-11. So relays need to return those fields and clients need to parse those fields and if the relay has `limitations.payment_required: true` then clients should display that somehow so that it's easy for a user to know whether they can post to a relay right off or whether they need to do something special first (pay, configure POW, etc).
Too early for this now, but it would also be great somewhere down the road if there were a NIP that standardized how to pay for pay-to-post relays in a way that it could be implemented within clients such that users could do it all from within their client with a click or two. In my perfect world, this payment would not be limited to bitcoin / satoshis, but would instead be completely agnostic so that relays could take payment however they want and users could choose from among whatever choices the relay offered.
pjv
npub1pj…e0h42
2023-04-08 12:17:34
in reply to nevent1q…l4m2
Author Public Key
npub1pjvcwasj9ydasx9nmkf09pftsg640vm5fs7tzprssew8544yj2ds6e0h42Published at
2023-04-08 12:17:34Event JSON
{
"id": "c34ccfb28b01c1d5b11c0ec81b39958589fa8f5014bc87f7b15ae691180fefe2",
"pubkey": "0c99877612291bd818b3dd92f2852b823557b3744c3cb10470865c7a56a4929b",
"created_at": 1680949054,
"kind": 1,
"tags": [
[
"p",
"ee11a5dff40c19a555f41fe42b48f00e618c91225622ae37b6c2bb67b76c4e49"
],
[
"p",
"00000000827ffaa94bfea288c3dfce4422c794fbb96625b6b31e9049f729d700"
],
[
"p",
"35d26e4690cbe1a898af61cc3515661eb5fa763b57bd0b42e45099c8b32fd50f"
],
[
"p",
"218238431393959d6c8617a3bd899303a96609b44a644e973891038a7de8622d"
],
[
"e",
"00000dbb6e0e3966500cefa56f0ddf71b47997deacac64bef0c910a0f0fd1f5f",
"wss://nos.lol/",
"root"
],
[
"e",
"00000b8a5366af1e911eddb0d57bfcaa560e3c9268ee2bcc9180b1030879ffdb",
"wss://nos.lol/",
"reply"
]
],
"content": "I've been noticing for a while that there doesn't seem to be a clearcut (interoperable) way to determine whether a given relay requires payment to post there or not. If you do a lot of manual digging and searching you can figure it out on a relay-by-relay basis but that seems unacceptable from a UI/UX point of view unless we (devs) want nostr to be geek-only.\n\nI think for this issue what's probably needed is some kind of push to make both relays and clients really fully implement the \"Server Limitations\" (at least), and also the \"pay-to-relay\" blocks from the \"extra fields\" in NIP-11. So relays need to return those fields and clients need to parse those fields and if the relay has `limitations.payment_required: true` then clients should display that somehow so that it's easy for a user to know whether they can post to a relay right off or whether they need to do something special first (pay, configure POW, etc).\n\nToo early for this now, but it would also be great somewhere down the road if there were a NIP that standardized how to pay for pay-to-post relays in a way that it could be implemented within clients such that users could do it all from within their client with a click or two. In my perfect world, this payment would not be limited to bitcoin / satoshis, but would instead be completely agnostic so that relays could take payment however they want and users could choose from among whatever choices the relay offered.",
"sig": "0cb2aac9547b4411a90b3a53515a0df349f587808370811c68a85e08d9181807c0ab6e4da8a81713d0f54f54b2d506552a092bce381c1d05a37901dc84667b8d"
}