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!

Replies (27)

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?! image
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
nevent1qqspqxe7rvx4257f6c4xjsp6zr9k3npdj77a47m5mey37v689n0mg3csgynr2
You're basically saying him trying to build a company means nothing. He made effort into thinking of a cool name and branding his app. He should of just named his app Will according to you.
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? image
↑