@Grape Ape Did you clear out your cookies in your main browser and still hit it, I'm just trying to figure out if something is wrong with the commit or if something is wrong with PA, we have no secondary reports currently.
@Grape Ape Did you clear out your cookies in your main browser and still hit it, I'm just trying to figure out if something is wrong with the commit or if something is wrong with PA, we have no secondary reports currently.
Clearing cookies appears to reset it for me. I've updated the original post with a summary as I understand it.
If one of the mods/tube can take over the summary post, I'd appreciate it.
Got hit again after being clearing. Continued when swapping from Firefox to IE.
0
AegisFear My DanceOvershot Toronto, Landed in OttawaRegistered Userregular
Also getting hit by it. Thought it made sense given the Hearthstone card reveal and the trickle of card posts coming out (although in retrospect, 5 posts/minute is kind of hard to pull off even for that), but then 1 post 5 minutes apart and then triggering it again made me scratch my head.
Wait @Grape Ape we do actually have some spam blockers in place, just to be clear. The time stamp on your phone indicates you tried to send that immediately after the first?
PMs are:
2 within 30 seconds
discussons are:
1 within 60 seconds
and comments are:
5 within 60 seconds
If you are testing the limit like to the second, its probably going to shit on you. The random ones that are minutes apart is what we want to squash. Also I guess the PM warning is inaccurate, I'll file that.
Wait @Grape Ape we do actually have some spam blockers in place, just to be clear. The time stamp on your phone indicates you tried to send that immediately after the first?
PMs are:
2 within 30 seconds
discussons are:
1 within 60 seconds
and comments are:
5 within 60 seconds
If you are testing the limit like to the second, its probably going to shit on you. The random ones that are minutes apart is what we want to squash. Also I guess the PM warning is inaccurate, I'll file that.
Gotcha. In that case I believe I am seeing intended behavior. Thank you very much for your help!
which will also fix the bug of Tube not being able to drop 6 sick Andromeda burns in a row. So that's good news!
As a dummy with no skin in the game, it seems reasonable to me to close this as fixed when that gets merged in + some baking time.
Really just as soon as an admin can shitpost to their hearts content which is the real win.
Wait "Grape Ape" we do actually have some spam blockers in place, just to be clear. The time stamp on your phone indicates you tried to send that immediately after the first?
PMs are:
2 within 30 seconds
discussons are:
1 within 60 seconds
and comments are:
5 within 60 seconds
If you are testing the limit like to the second, its probably going to shit on you. The random ones that are minutes apart is what we want to squash. Also I guess the PM warning is inaccurate, I'll file that.
It might be a display bug if it was saying 1 in 60 seconds though...
It's not a slack channel. One PM per 60 seconds is fine.
That's fine, regardless of my intense desire to send dozens of PMs every minute . It differs from what was said above, and with the recent weirdness of the spam limits, I thought it worth confirming.
It's not a slack channel. One PM per 60 seconds is fine.
I think there's some confusion about 2/30 seconds vs the warning message of 1/60 seconds as a potential mismatch.
I'll check if there's an item in their backlog tracking it...
E: no item in last 7 days that appears to correspond to this issue. Might have been lost in the scramble to triage problem and deploy a hot fix.
It's not a slack channel. One PM per 60 seconds is fine.
I think there's some confusion about 2/30 seconds vs the warning message of 1/60 seconds as a potential mismatch.
I'll check if there's an item in their backlog tracking it...
E: no item in last 7 days that appears to correspond to this issue. Might have been lost in the scramble to triage problem and deploy a hot fix.
While I respect your diligent looking at our github, sometimes we are internally confirming what the issue actually is before we file it. The issue is not lost.
It's not a slack channel. One PM per 60 seconds is fine.
I think there's some confusion about 2/30 seconds vs the warning message of 1/60 seconds as a potential mismatch.
I'll check if there's an item in their backlog tracking it...
E: no item in last 7 days that appears to correspond to this issue. Might have been lost in the scramble to triage problem and deploy a hot fix.
While I respect your diligent looking at our github, sometimes we are internally confirming what the issue actually is before we file it. The issue is not lost.
Good to hear and know. I'll stop being nosy about it.
Is there a good checkpoint for calling this issue closed/fixed? It feels like the major issue has been solved, and unsure what follow-up if any is pending...
Posts
I believe it is happening in bug report as well.
From this thread, incognito mode/cross browser not triggering it
https://docs.google.com/spreadsheets/d/1OLcAGbXhWIVcl5IziVpG0eKFJS3xi_Sac9kYMkRFvD8/edit?usp=sharing
Checked via PM
https://docs.google.com/spreadsheets/d/1OLcAGbXhWIVcl5IziVpG0eKFJS3xi_Sac9kYMkRFvD8/edit?usp=sharing
Clearing cookies appears to reset it for me. I've updated the original post with a summary as I understand it.
If one of the mods/tube can take over the summary post, I'd appreciate it.
https://docs.google.com/spreadsheets/d/1OLcAGbXhWIVcl5IziVpG0eKFJS3xi_Sac9kYMkRFvD8/edit?usp=sharing
Chrome desktop.
Currently DMing: None
Characters
[5e] Dural Melairkyn - AC 18 | HP 40 | Melee +5/1d8+3 | Spell +4/DC 12
Currently DMing: None
Characters
[5e] Dural Melairkyn - AC 18 | HP 40 | Melee +5/1d8+3 | Spell +4/DC 12
Logged out / back in just before this post.
Edit: and this is without a relog or clearing cookies or anything.
Ok so it happened just before it went live so that's good
Edit: 4:30 CST
Will try more rigorous cache clear and try again.
Edit: cleared all cache data <1 week old. Still occurs w/ the '1 time in 60 seconds' message.
https://docs.google.com/spreadsheets/d/1OLcAGbXhWIVcl5IziVpG0eKFJS3xi_Sac9kYMkRFvD8/edit?usp=sharing
E: only 2 of those posts were within a minute of each other. Speed posting is hard
https://docs.google.com/spreadsheets/d/1OLcAGbXhWIVcl5IziVpG0eKFJS3xi_Sac9kYMkRFvD8/edit?usp=sharing
PMs are:
2 within 30 seconds
discussons are:
1 within 60 seconds
and comments are:
5 within 60 seconds
If you are testing the limit like to the second, its probably going to shit on you. The random ones that are minutes apart is what we want to squash. Also I guess the PM warning is inaccurate, I'll file that.
Gotcha. In that case I believe I am seeing intended behavior. Thank you very much for your help!
https://docs.google.com/spreadsheets/d/1OLcAGbXhWIVcl5IziVpG0eKFJS3xi_Sac9kYMkRFvD8/edit?usp=sharing
which will also fix the bug of Tube not being able to drop 6 sick Andromeda burns in a row. So that's good news!
As a dummy with no skin in the game, it seems reasonable to me to close this as fixed when that gets merged in + some baking time.
Really just as soon as an admin can shitpost to their hearts content which is the real win.
https://docs.google.com/spreadsheets/d/1OLcAGbXhWIVcl5IziVpG0eKFJS3xi_Sac9kYMkRFvD8/edit?usp=sharing
So I believe this is working as intended as per:
It might be a display bug if it was saying 1 in 60 seconds though...
https://docs.google.com/spreadsheets/d/1OLcAGbXhWIVcl5IziVpG0eKFJS3xi_Sac9kYMkRFvD8/edit?usp=sharing
Also, that's a pretty harsh spam limit on PMs, you have to wait in between every message
3DS Friend Code: 3110-5393-4113
Steam profile
That's fine, regardless of my intense desire to send dozens of PMs every minute
3DS Friend Code: 3110-5393-4113
Steam profile
I think there's some confusion about 2/30 seconds vs the warning message of 1/60 seconds as a potential mismatch.
I'll check if there's an item in their backlog tracking it...
E: no item in last 7 days that appears to correspond to this issue. Might have been lost in the scramble to triage problem and deploy a hot fix.
https://docs.google.com/spreadsheets/d/1OLcAGbXhWIVcl5IziVpG0eKFJS3xi_Sac9kYMkRFvD8/edit?usp=sharing
While I respect your diligent looking at our github, sometimes we are internally confirming what the issue actually is before we file it. The issue is not lost.
Good to hear and know. I'll stop being nosy about it.
Is there a good checkpoint for calling this issue closed/fixed? It feels like the major issue has been solved, and unsure what follow-up if any is pending...
https://docs.google.com/spreadsheets/d/1OLcAGbXhWIVcl5IziVpG0eKFJS3xi_Sac9kYMkRFvD8/edit?usp=sharing