The bug should be fixed now so entering
[KEY=Steam Game]S:BOGHAV97VTM26QYI[/KEY]
(without quotes) should now work as intended. Sorry for the oversight on that one, I guess the bots had a few last hurrahs at my expense.
Some updates I'm working on:
- When it writes "claimed by USER" back to the thread, I'm going to add in the key type and name (so everyone knows what they missed out on!)
- Adding a dialog "Are you sure you want to claim?" when clicking the button, hopefully this prevents accidental claims
- Better error handling, as now the system kicks back errors (invalid giveaway ID, key already claimed, etc.) but still is refreshing the page as if you were successful. Looking into that.
- I'm looking into the reported mobile(?) issue with claim buttons not working
The old system actually used a disproportionate amount of processing power compared with GAF's regular daily operations. Gathering names for a drawing, kicking off a process every few minutes to see if a drawing needed to happen (which sometimes got stuck), performing the random calculations required for the drawing, etc. It was also set up in such a way that the more giveaways that were created over the years, the more CPU intensive this process became. The code was old and obviously unoptimized, and it needed replaced.
This new system was designed to be lean on resources from jump. We have to dance a fine line: for example just rendering the buttons normally would be a database driven process, but that would be a massive resource hit given GAF's daily traffic. The system now has a very tiny performance impact, and only has non-trivial impact segments server-side when a giveaway is being created or redeemed. It's designed to scale up linearly.
Thanks for coming to my TED talk