the auth works pretty well, i have one bug. my problem is i dont handle when a client just sits there sending the same req over and over (pre-auth). so i need to build in the rate limiting now.. does yours do rate limits like this? the pattern is, connects once, sends thousands of reqs (which all get sent a reply of auth required)
Discussion
one extra bug i noticed besides this not having limits that is.. but its a rarer case, still..
yeah, implementing limits, that's a matter of creating some kind of timer, so the thread just backs off for like a second or whatever and then answers and if it's the same shit again backs off again further and etc
It fails a lot but it could be the spam
I have thought a lot about limiting sockets per ip address
ya, i've been finding/fixing lots of bugs.. im super annoyed w ubuntu rn (the host os) it doesnt have compatible journal with debian AND it uses snap 😭. seemed fine for a while, till it wasnt.
yeah, i'm not experienced with the pros and cons of this stuff because i only have like one or two things running
there is rate limit ability in there somewhere
you could make it just quit giving the same thing after a while maybe, why waste the bandwidth
ya, its all good, i can add a backoff for this case fairly ez. possibly some other things maybe ill do here while im in the code, like supporting dynamic limits/notice payments.