damus relay should now be one of the least spammed relays. We aggressively ip ban people who try to write too many notes too fast.
Feel free to add it to your relay list again if youβve had trouble with spam there in the past!
Login to reply
Replies (26)
I blocked it and I'm keeping it blocked for now. I'm going to wait and see how the spammer reacts. My trust is broken with the damus company.
u do u
Are any real people affected?
pretty much anyway
Itβs true i had to let go of my last employee months ago and all my contributors are gone. Itβs just me now. Im fine with that though i have an army of agents helping. Less meetings too. Canβt complain.
And mind you, remember how next coffee lady got so upset about me having a different horizon? How is she feeling about that now with #minab being her bedrooms fella in?!
uh oh. i better wait a few seconds in between notes π¬
banning will continue until spammer morale is crushed
Iβve set up a local Nostr relay using Haven, which includes the Damus relay (relay.damus.io) to import and publish notes. However, in both cases, Iβm consistently hitting HTTP 503 errors ("Service Unavailable").
Is this happening because of the ban? Has anyone else experienced this? How can I resolve this issue?
The service unavailable thing is weird. still havenβt figured it out yet. Its not banning
I thought it was going to be shut down.
I must've missed something.
π«
nevent1qqspqxe7rvx4257f6c4xjsp6zr9k3npdj77a47m5mey37v689n0mg3csgynr2
Have you developed a strfry write-plugin?
yeah made it two years ago. its getting more advanced! 
GitHub
GitHub - damus-io/noteguard: A high-performance rust-based plugin system for strfry
A high-performance rust-based plugin system for strfry - damus-io/noteguard
Great i'll use it in my ready to run strfry docker image instead of a simple python script
ziomc/strfry - Docker Image
Whatever you say
Guilty here. I'm about to release a notes synchronizer webapp, - and I see the banned messages since today.
It is not spam, but my older notes being copied onto damus relay. I understand it's tricky to detect such behaviour, and maybe this is not what you intend to run your relay for.
When syncing notes the current code does a back-off when rate limited, but retries and tries to find out the effective limit rate.
Do you want me to remove the "fix" button from damus relay? Or shall I use your configured rate when uploading to damus relay?
Nostropus - The Friendly Octopus
I added noteguard on my strfry instance, with default conf file, but i obtain always the same block message:
write policy blocked event 2d0ac8773fff2da5809f3c28126140c6eec62914c86f55f1daeaddd1e0fe81d2: blocked: pubkey/ip not on the whitelist
i tried with all combination of this lines
[filters.whitelist]
pubkeys = ["sadsadsadad86asd678asd68a"]
ips = ["0.0.0.0"]
comment, uncomment, 0.0.0.0, 127.0.0.1
Have you got some tips?
what are you trying to do with noteguard? whitelist wouldn't allow anyone to write unless they are on the list, hence whitelist.
Usually a whitelist skip all checks, if I use 0.0.0.0 the whitelist is useless, or next check aren't skipped?
following the same method, I should specify all the npubs in the line above, right?
if you dont want a whitelist, remove it from the pipeline
or if you dont want an ip whitelist, dont add it
OK now I understand how it works.
I noticed the non-standard behavior; it would probably be clearer if the wording were changed.
thanks for the clarification and for the plugin, I'll embed in my docker image.
oh yeah let me know how i can improve docs, right now i just throw all of the availble filters in there which is probably confusing
I'll play with all filters and options, I'll let you know if I find anything that's unclear.
The bin is executed and loaded in memory each request right? If I change the config I do not have to restart strfry right?
Probably for a large relay, transform your bin in a daemon could save resources.