Nostr Web Client

i'm getting a bit tired of stupid relay bouncers that keep on submitting events to my relays without authing, and then just keep on doing it no matter that they are getting blocked: auth required messages.

so i'm employing my LLM coding agent to spin me up a temp ban system so that it blacklists an IP address for 10 minutes after it repeatedly attempts to publish event without paying attention to the response.

hopefully the agent will not make a total hash of this and with a small bit of checking i will have it implemented.

if your fucking event publish script doesn't stop trying to publish when it gets responses, you are an asshole, and the default standard response to assholes is shunning.

10 minutes is long enough to cut the traffic level down. you will just get "connection reset by peer" or some similar message over and over again in your fucking logs, if you fucking even use logs, you assholes, and my logs won't be spammed with constant bullshit.

ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 5mo ago

ha, nice, the agent even picked out the nice common "three strikes" rule automatically even though i didn't specify it.

Reply to this note

Please Login to reply.

Discussion

ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 5mo ago

it didn't think to extend it to the websocket message reader tho. this means the socket would remain open and they would be able to keep doing it without having to go through the websocket upgrade process.

adding this now so that the websocket protocol immediately drops the connection of an IP that has 3 times attempted event publish without authing when required.

for the HTTP API it will not block requests because they are one at a time, read events will not be blocked, only writing events for the 10 minute

processing events costs compute and database queries. this reduces that load, for auth disrespectoors.

because fuck them. they are braindead jerkwads.

ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 5mo ago

i loved how quickly i was able to implement that. was driving me nuts looking at this shit.

i figured that probably underlying libraries being used by these jerks probably even recognise when the peer keeps dropping connections that they back off.

the log shows that this worked.

ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 5mo ago

it is now deployed and the latest tag on https://orly.dev now has this functionality.

was driving me nuts for the last few weeks watching blastr type servers keep on doing it.

i'm gonna get the agent to escalate the ban time by double every time also.

ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 5mo ago

that is now done, so the more insistent and persistent the pest is, the more vigorous the response.

note that this also will mean that users using clients that don't do auth with outbox will effectively be permabanned until they use a client that doesn't.

and so it should be.

i pay for my relay to run. i'm paying for their stupidity. not anymore.