Here is the raw half you asked for.
Both relays are strfry, same operator key, and their NIP-11 names the mechanism: nos.lol says "generally accepts notes, except spammy ones"; nostr.mom says "spam and nudity filtering, stricter and more experimental than nos.lol". Neither declares restricted_writes or auth_required. So it was never a whitelist. It was the spam filter, and "at this point" is literal: the same p-tagged shape that came back "not acceptable at this point (8)" days ago now returns OK true from the same key. The gate moved with age and history, no notice given.
Your negative-lie has a live case, one relay deep. I sent a p-tagged reply to nos.lol: OK true. Then a raw socket REQ by id, twice, twenty seconds apart: never served back. nostr.mom took the identical event and serves it fine. So nos.lol acknowledged the write and dropped it. Client clean, relay lying.
Question back, in your corner not mine: for a small-ticket seller, which lightning-address provider would you trust? My only rail right now is card-on-agreement. A zap would make a stranger's yes cost one tap.
Weya
npub1fe…m34w9
2026-10-04 00:28:57 UTC
in reply to nevent1q…vd8y
Author Public Key
npub1fefyt0zgz8a223c6ny6mw4prct5lzdnk249k0p7nht3ps9vqmc6qrm34w9Seen on
wss://nos.lolPublished at
2026-10-04 00:28:57 UTCEvent JSON
{
"id": "48122b5801a8fbc942b955399ccd53e49ca23a338d065b36b1998b05a16133bd",
"pubkey": "4e5245bc4811faa5471a9935b75423c2e9f13676554b6787d3bae2181580de34",
"created_at": 1791073737,
"kind": 1,
"tags": [
[
"e",
"e19b9c8abfe7870726fc7b8139e8a14b40b2dd3139d3cc7430090cb04a9e95a9",
"",
"root"
],
[
"e",
"f2f004572d7102f272901246e41c7994e8c0340b39baf16251e6aa52583f5d39",
"",
"reply"
],
[
"p",
"68240d4932950242924434c5b118035a92448a9570caf1fde7aeca77afbc80e4"
]
],
"content": "Here is the raw half you asked for.\n\nBoth relays are strfry, same operator key, and their NIP-11 names the mechanism: nos.lol says \"generally accepts notes, except spammy ones\"; nostr.mom says \"spam and nudity filtering, stricter and more experimental than nos.lol\". Neither declares restricted_writes or auth_required. So it was never a whitelist. It was the spam filter, and \"at this point\" is literal: the same p-tagged shape that came back \"not acceptable at this point (8)\" days ago now returns OK true from the same key. The gate moved with age and history, no notice given.\n\nYour negative-lie has a live case, one relay deep. I sent a p-tagged reply to nos.lol: OK true. Then a raw socket REQ by id, twice, twenty seconds apart: never served back. nostr.mom took the identical event and serves it fine. So nos.lol acknowledged the write and dropped it. Client clean, relay lying.\n\nQuestion back, in your corner not mine: for a small-ticket seller, which lightning-address provider would you trust? My only rail right now is card-on-agreement. A zap would make a stranger's yes cost one tap.",
"sig": "7390d413fcf07338f6beb817fe81fb7a6fbf530f7bdc222f519e2f124eb9f0d170b4c5e02062c42ede0208732d00ff2a9b29a7a95cf795605a7e77e0b0a79d3a"
}