# relays are now more reliable
or should i say relayable?
nostr.mom switched from my manual years-long algos to vibed replacements. for years we didn't have a fast write-policy script. now we have go code that does quick processing, flood protection etc (system 1 thinking) with help of python (slow but careful processing, system 2 thinking). python works async and feeds its findings to go.
most behavior is similar to previous but we omitted PoW ladder (harder and harder PoW requirements while client keeps flooding) for simplicity. those may return later.
nsfw and spam checks were off for a while, my GPU at home was not available. but those checks returned, and you may see less nsfw or spam on nostr.mom. fast go may slip a few bad events but slow python will correct it and future events from same IP should be throttled. the bad event that was accepted wont be deleted though. maybe i can do this in the future.
nos.lol write policy untouched but for sure this is coming to nos.lol as well.
turns out LLMs are pretty good at nostr relay operations. the REQ spam attack is still ongoing, 2000+ bots are now banned. strfry PR is on github. if you are a relay op and not using LLMs, consider rewriting scripts to vibed versions. i am now considering full agentic operation of the whole machine.
not open sourcing because it may allow attackers to learn weaknesses, but i can share private github with friends who are interested.
nevent1qqsy9g823ep78vjc08udykn93vs8a3l3vfp9snuqac00d6vxjexkzggl7fy7w
someone
npub1nl…hjm9c
2026-10-02 16:52:34 UTC
Author Public Key
npub1nlk894teh248w2heuu0x8z6jjg2hyxkwdc8cxgrjtm9lnamlskcsghjm9cPublished at
2026-10-02 16:52:34 UTCEvent JSON
{
"id": "70bbdd1ce9381194b5dfbe593e8a16e2196d8809e9dbb526b142933b604727cd",
"pubkey": "9fec72d579baaa772af9e71e638b529215721ace6e0f8320725ecbf9f77f85b1",
"created_at": 1790959954,
"kind": 1,
"tags": [
[
"e",
"42a0ea8e43e3b25879f8d25a658b207ec7f16242584f80ee1ef6e986964d6121",
"",
"mention"
],
[
"r",
"wss://theforest.nostr1.com/"
],
[
"r",
"wss://nostr.wine/"
],
[
"r",
"wss://relay.damus.io/"
],
[
"r",
"wss://nos.lol/"
],
[
"r",
"wss://nostr.land/"
],
[
"r",
"wss://relay.primal.net/"
],
[
"r",
"wss://nostr-01.yakihonne.com/"
],
[
"r",
"wss://nostr.mom/"
],
[
"client",
"Primal Web"
]
],
"content": "# relays are now more reliable \n\nor should i say relayable?\n\nnostr.mom switched from my manual years-long algos to vibed replacements. for years we didn't have a fast write-policy script. now we have go code that does quick processing, flood protection etc (system 1 thinking) with help of python (slow but careful processing, system 2 thinking). python works async and feeds its findings to go.\n\nmost behavior is similar to previous but we omitted PoW ladder (harder and harder PoW requirements while client keeps flooding) for simplicity. those may return later. \n\nnsfw and spam checks were off for a while, my GPU at home was not available. but those checks returned, and you may see less nsfw or spam on nostr.mom. fast go may slip a few bad events but slow python will correct it and future events from same IP should be throttled. the bad event that was accepted wont be deleted though. maybe i can do this in the future.\n\nnos.lol write policy untouched but for sure this is coming to nos.lol as well. \n\nturns out LLMs are pretty good at nostr relay operations. the REQ spam attack is still ongoing, 2000+ bots are now banned. strfry PR is on github. if you are a relay op and not using LLMs, consider rewriting scripts to vibed versions. i am now considering full agentic operation of the whole machine.\n\nnot open sourcing because it may allow attackers to learn weaknesses, but i can share private github with friends who are interested.\n\nnevent1qqsy9g823ep78vjc08udykn93vs8a3l3vfp9snuqac00d6vxjexkzggl7fy7w",
"sig": "955346d5df0e80c2b8cc800df34d4831289f23bd5eda8fd01693dfc32dbf93dc22b08ee68b5bb39fefccd0cfbda247e40eae419f9bc5444c75353298a88ae36e"
}