not 410?
for the first time, since way back in the day, i took some ip blocking actions for nostr1.com.
scrapers have gone wild.
please make sure your scraper is nice, and listens to error responses with exponential backoff. nostr1 will send a 403 for "relay is gone".
many scrapers (i count 4+) are connecting to relays that do not exist in a tight loop and while usually i can handle this traffic, now it annoys me.
nostr:nprofile1qqs8d3c64cayj8canmky0jap0c3fekjpzwsthdhx4cthd4my8c5u47spzfmhxue69uhhqatjwpkx2urpvuhx2ucpz3mhxue69uhhyetvv9ujuerpd46hxtnfduq3vamnwvaz7tmjv4kxz7fwdehhxtnnda3kjctvll3q2p nostr:nprofile1qqs99d9qw67th0wr5xh05de4s9k0wjvnkxudkgptq8yg83vtulad30gpp4mhxue69uhkummn9ekx7mqpz3mhxue69uhhyetvv9ujuerpd46hxtnfduq32amnwvaz7tmgd9ehgtnwdaehgu3wd3skueqyluj3x lmk if u can fix it and ill unblock. the others i have no idea who they are, ..
Discussion
not 410, haproxy didnt have that response code by default, would that help?
yes. 403 I would assume to be some sort of rate limit issue, while 410 would indicate this is gone, don’t try again for a while (every 1d if the relay is seen)
I am also pushing an update that fixes the bug with automatic retries, backing off until reaching 1h if there are 10 failed requests
ok, i only saw your one ip, i unblocked it (lmk if there were others on simplex if u want). the list has grown fairly long now..
i switched the error code to http 410 for relays deleted
I have pushed the update, you can unblock it now
let me know if you continue to experience issues