Oh, yeah good questions.. I was kind-of just doing a more hu...

cloud fodder

npub10npj3gydmv40m70ehemmal6vsdyfl7tewgvz043g54p0x23y0s8qzztl5h

hex

52cc27b1746007b24ce6a01946caa5a632816984f5183b362d4d35d7d5e83e85

nevent

nevent1qqs99np8k96xqpajfnn2qx2xe2j6vv5pdxz02xpmxck56dwh6h5rapgprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgs8eseg5zxak2hal8umuaa7laxgxjyll9uhyxp86c522shn9gj8crsmvpspt

Kind-1 (TextNote)

2026-03-31T05:30:10Z

↳ Reply to Silberengel (npub1l5sga6xg72phsz5422ykujprejwud075ggrr3z2hwyrfgr7eylqstegx9z)

How can I tell If they have a limited kind list, or no AUTH but with whitelist? I always have to add 5 randoms, to make sure at least 1 works. Effecti...

Oh, yeah good questions.. I was kind-of just doing a more human type tagging, like tagging the relays I know about that are "good for Directory" purpose or etc, even if I don't run them, just to help discovery.. I also really dislike the wording on nip11 and clients saying "payment required" vs "payments accepted". Same for auth, "auth required" vs. "auth capable". We've evolved so far past nip11 and relays being just one single dumb thing. The relay may accept payment, but that does not mean it requires it to use.

So yeah, if you're automating, it might take some kind of testing of the relay capabilities, or if you have nip86 access you can pull allowedkinds that way (but that requires the access which is usually only owners and mods).

I don't really know how you'd do this for random relays.. That's why relays should all have their own monitors, where the operator can at least seed some of this info.. (or fix/augment their nip11s)

Raw JSON

{
  "kind": 1,
  "id": "52cc27b1746007b24ce6a01946caa5a632816984f5183b362d4d35d7d5e83e85",
  "pubkey": "7cc328a08ddb2afdf9f9be77beff4c83489ff979721827d628a542f32a247c0e",
  "created_at": 1774935010,
  "tags": [
    [
      "e",
      "f329693b53902e0869ae163fedd3be99fb2e92dd8311a15b5f8a8d2dc0cd4246",
      "wss://nostr.wine/",
      "root",
      "460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c"
    ],
    [
      "e",
      "32dbaec5045fe5999da55e5ed933366dc7ef090104482e9c89ec1eea3666a1e2",
      "wss://theforest.nostr1.com/",
      "reply",
      "fd208ee8c8f283780a9552896e4823cc9dc6bfd442063889577106940fd927c1"
    ],
    [
      "p",
      "460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c"
    ],
    [
      "p",
      "deab79dafa1c2be4b4a6d3aca1357b6caa0b744bf46ad529a5ae464288579e68"
    ],
    [
      "p",
      "fd208ee8c8f283780a9552896e4823cc9dc6bfd442063889577106940fd927c1"
    ]
  ],
  "content": "Oh, yeah good questions.. I was kind-of just doing a more human type tagging, like tagging the relays I know about that are \"good for Directory\" purpose or etc, even if I don't run them, just to help discovery..  I also really dislike the wording on nip11 and clients saying \"payment required\" vs \"payments accepted\".  Same for auth, \"auth required\" vs. \"auth capable\".  We've evolved so far past nip11 and relays being just one single dumb thing.  The relay may accept payment, but that does not mean it requires it to use.\n\nSo yeah, if you're automating, it might take some kind of testing of the relay capabilities, or if you have nip86 access you can pull allowedkinds that way (but that requires the access which is usually only owners and mods).\n\nI don't really know how you'd do this for random relays..  That's why relays should all have their own monitors, where the operator can at least seed some of this info.. (or fix/augment their nip11s)",
  "sig": "13075fcd34c7d5e18a62c861421dbfdc6a7209115ee2d39c0f0bfbb7de01b6ac0ce7f0f44609a744cd11b4c7433295229293690d4c4dc0e42675ae798028d4b4"
}