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.
16,661 Comments - Last post 60 seconds ago by Kenruyoh
11 Comments - Last post 9 minutes ago by Seibitsu
27 Comments - Last post 45 minutes ago by Chris76de
223 Comments - Last post 47 minutes ago by gilbygamer
64 Comments - Last post 1 hour ago by Rosayde
5 Comments - Last post 2 hours ago by kasiq
2,364 Comments - Last post 4 hours ago by FranckCastle
117 Comments - Last post 2 minutes ago by MayoSlice
27 Comments - Last post 3 minutes ago by s4k1s
46 Comments - Last post 8 minutes ago by ngoclong19
438 Comments - Last post 21 minutes ago by Tucs
1,610 Comments - Last post 23 minutes ago by miIk
128 Comments - Last post 35 minutes ago by gilbygamer
2,893 Comments - Last post 37 minutes ago by herbesdeprovence
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.