Well, maybe it's just the programmer in me, but I certainly care about bugs in software. Sure this one in particular doesn't really matter in the end—provided it's not indicative of more serious problems—but surely when a bug is found, even a minor one, it's better to fix it than to let it linger, no?
I dunno. As I say, maybe I'm just extra-sensitive to these sorts of things because I myself program, but it's the sort of thing I'd want to stamp out of my own work, so I figured I'd bring it to the attention of the administration.
Comment has been collapsed.
13 Comments - Last post 10 minutes ago by Celtic69
26 Comments - Last post 27 minutes ago by lafilleange95
31 Comments - Last post 41 minutes ago by BDK
1,543 Comments - Last post 2 hours ago by Willi4DC
11 Comments - Last post 2 hours ago by JHartmann
15,644 Comments - Last post 4 hours ago by Channel28
88 Comments - Last post 5 hours ago by MrVivian
6 Comments - Last post 1 minute ago by vigaristti
35 Comments - Last post 10 minutes ago by RePlayBe
823 Comments - Last post 11 minutes ago by kyriaki
42 Comments - Last post 11 minutes ago by Hawkingmeister
26,917 Comments - Last post 32 minutes ago by Unekha
537 Comments - Last post 37 minutes ago by Fitz10024
2,536 Comments - Last post 37 minutes ago by JMM72
I've noticed this issue a few times, but this is the first time I've definitively determined what the issue is, but it is definitively a bug:
As the example which definitively proved it was an issue, I was recently entered into multiple Talisman giveaways, before I decided to purchase the Humble Bundle containing it. When I purchased the bundle, rather than wait for the Entered Games list to load, I simply performed a search for Talisman, opened all the GAs I was entered into in new tabs, and Ctrl+Tabbed between them, removing my entries as I went along. However, despite removing my entries from four separate giveaways, my point balance only increased by 15P—the value of a single giveaway.
My assumption is that the AJAX handler does not check for the giveaway code when entries are removed, and so when it receives multiple requests in short succession, it assumes those received after the first are erratic and discards them. I've tested it the other way—ie, entering giveaways in short succession—and it does not seem to be an issue there, which would be a more serious and exploitable issue. However, the presence of the bug in removing entries could still possibly be concerning from a security perspective, and is certainly a bug in need of patching regardless.
Hopefully this issue will be reviewed and patched soon.
Comment has been collapsed.