Looks like The Bird (npub176g…q836) is using Amethyst, so this is not going to be enough to resolve the problem on its own. Because of the way Amethyst has implemented the outbox model, it connects to relays that are not in the user's outbox or inbox relays in order to display replies. In my experience, it does this even though I have proxy relays set.
This being the case, I also encountered a lot of spam while using Amethyst, even though I have ZERO public relays in my inbox relays. The only solution I could really come up with that was effective was to add the relays where the spam was appearing to my blocked relay list.
My list of blocked relays is growing as I encounter spam on new relays, but here's what I have blocked so far:
relay.primal.net
top.testrelay.top
relay.ditto.pub
nostr.bitcoiner.social
nostr.oxtr.dev
relay.dreamith.to
bitcoiner.social
Now, the unfortunate thing is, Amethyst encrypts the entries on the blocked relays list, and many other clients don't read that encrypted content, so they will still connect to those relays. For instance, I am on jank.army right now and I see all the spam, even though it is on relays I have already blocked. This disregard for encrypted entries on lists is far too common.
Dikaios1517
npub1ku…v3lhe
2026-09-02 23:14:51 UTC
in reply to nevent1q…6aws
Author Public Key
npub1kun5628raxpm7usdkj62z2337hr77f3ryrg9cf0vjpyf4jvk9r9smv3lhePublished at
2026-09-02 23:14:51 UTCEvent JSON
{
"id": "6e00b5944acbbf78563aa55ebf91f721dbb9b009b0c20b9e3374c3763f0356cc",
"pubkey": "b7274d28e3e983bf720db4b4a12a31f5c7ef262320d05c25ec90489ac99628cb",
"created_at": 1788390891,
"kind": 1,
"tags": [
[
"e",
"e50a08aab39fb21204e28481424a46f467e56e3436776d9687f42ec405a83467",
"wss://theforest.nostr1.com/",
"root",
"f6900e6b42a83a6d66589714de49ac86919c6464857d9e164b953bcf9c7e939d"
],
[
"e",
"98d8f2e289bd1534464f24797f9a727917f63a6dd6bcc0071f284c3263a5d7d5",
"wss://spatia-arcana.com/",
"reply",
"c230edd34ca5c8318bf4592ac056cde37519d395c0904c37ea1c650b8ad4a712"
],
[
"p",
"f6900e6b42a83a6d66589714de49ac86919c6464857d9e164b953bcf9c7e939d"
],
[
"p",
"bc02e0a6c0f01ad9cb57a2b0f8ef8241bc5ff979ce4452ce9e243de457756725"
],
[
"p",
"c230edd34ca5c8318bf4592ac056cde37519d395c0904c37ea1c650b8ad4a712"
],
[
"client",
"JANK"
]
],
"content": "Looks like nostr:npub176gqu66z4qax6ejcju2dujdvs6gecerys47eu9jtj5aul8r7jwwsnqq836 is using Amethyst, so this is not going to be enough to resolve the problem on its own. Because of the way Amethyst has implemented the outbox model, it connects to relays that are not in the user's outbox or inbox relays in order to display replies. In my experience, it does this even though I have proxy relays set.\n\nThis being the case, I also encountered a lot of spam while using Amethyst, even though I have ZERO public relays in my inbox relays. The only solution I could really come up with that was effective was to add the relays where the spam was appearing to my blocked relay list.\n\nMy list of blocked relays is growing as I encounter spam on new relays, but here's what I have blocked so far:\n\nrelay.primal.net\ntop.testrelay.top\nrelay.ditto.pub\nnostr.bitcoiner.social\nnostr.oxtr.dev\nrelay.dreamith.to\nbitcoiner.social\n\nNow, the unfortunate thing is, Amethyst encrypts the entries on the blocked relays list, and many other clients don't read that encrypted content, so they will still connect to those relays. For instance, I am on jank.army right now and I see all the spam, even though it is on relays I have already blocked. This disregard for encrypted entries on lists is far too common.",
"sig": "fdb0c6aabe1146970912776c8efdf58ed80e511382d4a9d02caad9b362d8be7c7c3ec298d9fc358b327d1e46ccb628f8a7a52c4bdf041877a5fe7ae337b5bb23"
}