Mike Dilger on Nostr: I have just coded something that gets rid of R-plyGuy and R-plyGal quite well. I will ...
I have just coded something that gets rid of R-plyGuy and R-plyGal quite well. I will make it available on unstable soon. It is not the ultimate solution (is there any such thing?) but it works for these.
First I extended the filter.rhai script to have access to a variable 'name' which is the name of the user (from metadata). In my script I reject based on the user's name being "R-plyGuy" or "R-plyGal"
(I'm not putting the actual name in case someone else's spam filter aggressively filters that from contents).
This doesn't help yet because when the event comes in, we don't have the metadata to lookup the name so the event passes the original spam filtering.
So I added some settings to apply the spam filtering to various situations like the thread feed. The UI originally displays it briefly with a pubkey while it triggers the fetcher to go get the metadata. Once the metadata flows in, the next time it recomputes the feed the spam filtering now sees the name and strips out the event.
So you might see these flash on the screen, but not for long.
I have some additional work, then I'll push to unstable. Then I'll try to see if we can't get the master branch merged forward soon.
Published at
2024-09-10 22:22:51Event JSON
{
"id": "8f51e9d4523e6bbc137f5ee32dac48f3a3c1a39adc302d8b36f9275092455337",
"pubkey": "ee11a5dff40c19a555f41fe42b48f00e618c91225622ae37b6c2bb67b76c4e49",
"created_at": 1726006971,
"kind": 1,
"tags": [],
"content": "I have just coded something that gets rid of R-plyGuy and R-plyGal quite well. I will make it available on unstable soon. It is not the ultimate solution (is there any such thing?) but it works for these.\n\nFirst I extended the filter.rhai script to have access to a variable 'name' which is the name of the user (from metadata). In my script I reject based on the user's name being \"R-plyGuy\" or \"R-plyGal\"\n\n(I'm not putting the actual name in case someone else's spam filter aggressively filters that from contents).\n\nThis doesn't help yet because when the event comes in, we don't have the metadata to lookup the name so the event passes the original spam filtering.\n\nSo I added some settings to apply the spam filtering to various situations like the thread feed. The UI originally displays it briefly with a pubkey while it triggers the fetcher to go get the metadata. Once the metadata flows in, the next time it recomputes the feed the spam filtering now sees the name and strips out the event.\n\nSo you might see these flash on the screen, but not for long.\n\nI have some additional work, then I'll push to unstable. Then I'll try to see if we can't get the master branch merged forward soon.",
"sig": "2e96802389a3c28aec01ab89e406b3518398bd58bec2284b2786973e1fe828969a274427d8f83e74d4f8ba415cef31fb32971ba6d48576ec676650188c41187d"
}