> This IP address (185.220.101.33) has performed an unusually high number of requests and has been temporarily rate limited. If you believe this to be in error, please contact us at [email protected].
Why yes, I do believe this is in error, because I'm already sending my auth cookies.
hmm I just found out MSO rules are very different from MSE, duplicates are not welcome at all there and get insta deleted.
I don't like MSO, lol
@forestdistrustsStackExchange there's some complex mechanism based on IP as far as I can tell, that also has cache, so that people who just keeps reloading won't boost the view count.
It's from Jeff days, he was good with such things. :D
I've seen attempts to decode this mechanism, all were a failure and just wild guesses.
unfortunately not quite so rare; the proper detection should probably be "Scam aimed at United Airlines customers in body" but it sometimes loses the target organization
@ShadowWizardSaysNoMoreWar As the answer says, the bulk of the impact to the site (the outages) was not the DDoS itself - it was the systems going haywire hours after. So the discussion I saw about the issue never mentioned a DDos, only that the systems were going spare. It wasn't until later someone mentioned that an attack caused that.
@Catija heh, you reply to my deleted messages? Well, deleted because it's 100% not your fault, and on second and third readings I did notice it might be seen as attacking you. Anyway, understood, and thanks. :)
@M.A.R. my favorite toothbrush is flexible, I replace type and even brand once in a while.
Not with chat, I don't think. The inbox may know that a comment is removed (and removes the notification if you haven't already viewed it) but I don't think the inbox is aware of up-to-date chat info, so it can't remove notifications about chat messages that get deleted.
If I had slower notifications turned on, I wouldn't have gotten the ping at all since you must have deleted it pretty quickly but I have my chat notifications set to deliver immediately, so if it was around for long enough to trigger that, it stays in the inbox. :)
@forestdistrustsStackExchange I think there's some info about that somewhere ... essentially, your own views do count but at the same rate as other users' views... essentially, we only count unique views every 10 or 15 minutes (can't remember which) so, if you view the question, then come back 20 minutes later and refresh, the view count will increment but just sitting on it and refreshing constantly won't.
It's a chat setting, right? So if you turn on "faster notifications" you get an inbox notification in under a minute, sometimes within 10 seconds or so.
@rene There's another report for that here: meta.stackexchange.com/q/267234/622284 Unsure if this should be closed in one direction or the other, if at all, though.
@ShadowWizardSaysNoMoreWar No, I use Tor. The system just thinks that one user is making too many connections when it's actually a number of users. When an auth cookie is being sent, the system should count me as an individual regardless of my IP address. It only makes sense to assume that same IP = same user when they're unauthenticated and anonymous.
Now, if the system just straight up refused the connection, I could understand, but it's obviously serving a page to me, which means it received the headers I sent it.
