You are hyper-sensitive.
lol Check your other comments. You are the one sitting on your high horse making claims and putting words in people's mouth.
Because the rate-limit happens more often to a couple users, it doesn't mean it's an issue specific to Poal.
The rate-limit has been working perfectly fine for everyone else.
The rate-limit has been working perfectly fine for everyone else.
..and I literally never brought this up until some other user complained and you dismissed it out of hand.
A couple users.
you dismissed it out of hand.
See, you're doubling down. I didn't dismiss, but explained them the reason why they might encounter this issue.
So some serious questions for you to ponder... I am not trying to shit post. Really think about this:
How do you know it is only a couple users? Right now our working theory is that there is some level of ISP level NAT going on... if thats the case then literally millions of users could be hiding behind a single IP. We are talking about the specific logic used to uniquely identify users... if that logic is imperfect then this problem might be far more widespread than you realize. Now if the only consequence to these false duplicates is a transient error message then its no big deal... BUT:
The fact that I am not using TOR or VPN but yet still frequently see this error indicates to me that the server side logic used for unique identification will sometimes throw false duplicates. Is this the same code logic you use in 'The Algorithm' ? We have seen many people come here and be flagged for suspicious behavior. In many of these cases the abuse was very obvious to all of us even without admin access. But we also have people who staunchly defend their own actions and claim to be falsely accused. So if the logic used to identify unique visitors is sometimes flawed... is it possible that the algorithm sometimes flags users improperly?
(post is archived)