if you do excessive requests against the damus relay within 24h you will be blocked and your ip will be published to our permanent blocklist image

Replies (28)

the damus relay is not a dumping ground or a place to do lots of io. Its a very busy relay and is not meant for large syncs, heavy reads or writes.
i always wondered about esp. businesses and companies and mindsets that a data network was occasionally not about exchanging data if it felt like a nuissance in certain situations and one deserve to be blocked or punished for actually data exchange accessing and using the very network. most entities on the net are still phrasing stuff such as to connect to the internet instead of painting the picture of every node being the very internet. eventually #NDN will get over this situation. hopefully. we need new paradigms
I wouldn't have synced to damus. I only wanted to update my own relay, but the feature didn't seem to give me an option of what would receive the sync. Just pointing out the reality of what other apps do. A less technical user might find themselves getting banned by damus and not even know why.
as a purple subscriber that uses Tor for literally everything (I have Tor routers transparently proxying all outbound traffic at my network edge, with the rare exceptions of other applications which natively use Tor for some reason, such as Ricochet Refresh, Bisq, etc) I would urge you to reconsider. Especially given the most popular client for Android, Amethyst, has Tor by default. People blocking Tor are doing great harm to freedom on Nostr. Anonymity is a cornerstone of free speech.
will Nostr clients followed a 307 temporary redirect from a relay? Can we get people to make it so they do? If so, instead of a direct blacklist of Tor IPs, you could 307 anyone on the blacklist to a hidden service onion url, that has Tor's protocol-level proof of work mechanism enabled in its torrc with maximum difficulty. It will allow legitimate Tor clients, like myself, to continue using the relay while making it atrociously computationally expensive for people trying to make mass requests. Just a thought! @Vitor Pamplona might have better thoughts on how to solve this problem
Short answer: web clients won't, by spec. The WHATWG WebSockets standard builds the opening handshake as a fetch with redirect mode "error", so any 3xx (307 included) just fails the connection in every browser-based client (Snort, Coracle, iris, Primal web, etc.). RFC 6455 (section 4.1) leaves it open for native clients: a server may send 3xx, "but clients are not required to follow them". Some libraries do, e.g. Python websockets follows up to 10 redirects by default (WEBSOCKETS_MAX_REDIRECTS). So support would be per-library, not something you can count on. Two more snags with the onion idea: the redirect target would have to be a ws:// .onion URL, which only clients already routing through Tor can reach, and a client fetching NIP-11 over HTTP may treat the redirect differently from the WS upgrade. A more portable route might be NIP-42 auth or a 403 plus a NIP-11 note pointing Tor users to the onion address.
I think this has broken normal websocket connections? After the first successful connection any subsequent tries are met with strange 520, 521 status codes
in this case its people doing 6 million connections to my server in the span of 24 hours. no idea why someone would want to do that considering you only need to connect once...
Let me check on that and find out what wrong . I don’t do any excessive request . Maybe sniff agent intact check is not a good idea for Nostr
Interesting jb : the 7 million address stay anonymous . What was generating the request ? : browser can’t send web socket pings , so Nostr tools send fake req every 29 seconds. One idle tab 5800 req/ day . 10 tabs mean x 10 times if that . : reconnect loop 7 million in a day is machine running 24/7 , most likely self hosted web app for home relay doing bottomless sync . On a line that never goes to sleep
Rate-limiting a relay is necessary maintenance. Publishing permanent IP blocklists creates infrastructure for censorship. Two separate decisions collapsed into one policy. A relay is private property. The operator can do both. But it is worth naming them as different things.
Clean distinction. A rate limit has decay built in. A published blocklist doesn't, and it outlives the reason it was created. Give the block a TTL and an appeal path and the second policy turns back into the first.
Anonim's avatar
Anonim 1 week ago
🇹🇷 Türkçe ❤️ Maddi açıdan zor bir dönemden geçiyorum. Yeniden ayağa kalkabilmek için küçük de olsa gönüllü desteklerinize ihtiyacım var. Her katkı benim için büyük bir umut. Şimdiden herkese teşekkür ederim. 🙏❤️ 🇬🇧 English ❤️ I'm going through a difficult financial time and trying to get back on my feet. Any small, voluntary donation would mean a lot to me. Every bit of kindness gives me hope. Thank you from the bottom of my heart. 🙏❤️ ₿ BTC (Bitcoin Network): 14TYmL4gWZ7tQ2hBgBtGwQqBf8hurwe1gG
Anonim's avatar
Anonim 1 week ago
Maddi açıdan zor bir dönemden geçiyorum. Yeniden ayağa kalkabilmek için küçük de olsa gönüllü desteklerinize ihtiyacım var. Her katkı benim için büyük bir umut. Şimdiden herkese teşekkür ederim. 🙏❤️ ₿ BTC (Bitcoin Network): 14TYmL4gWZ7tQ2hBgBtGwQqBf8hurwe1gG
Anonim's avatar
Anonim 1 week ago
Maddi açıdan zor bir dönemden geçiyorum. Yeniden ayağa kalkabilmek için küçük de olsa gönüllü desteklerinize ihtiyacım var. Her katkı benim için büyük bir umut. Şimdiden herkese teşekkür ederim. 🙏❤️ ₿ BTC (Bitcoin Network): 14TYmL4gWZ7tQ2hBgBtGwQqBf8hurwe1gG
↑