Does this sound like a good idea to you?
It has been suggested before, and yes it would be a good idea. It would be even better, if the reveal-key-button could be pressed only once for the same game/product: even with the new auto-removal feature, it is possible to win something twice, by manually entering more giveaways for a game you already won. Now, if the button you suggested were implemented, a winner could only reveal one of their multiple wins and had to wait until they can mark their first win "not received" (with a fake giveaway or a bad key for example) before revealing a second key for the same game. That's effectively a queue.
Comment has been collapsed.
308 Comments - Last post 41 minutes ago by radagast82
28 Comments - Last post 1 hour ago by Chris76de
362 Comments - Last post 1 hour ago by Detruire
24 Comments - Last post 1 hour ago by RobbyRatpoison
28 Comments - Last post 2 hours ago by UnknownEAK
809 Comments - Last post 2 hours ago by MeguminShiro
2,677 Comments - Last post 2 hours ago by ToatsMcGoats
177 Comments - Last post 23 seconds ago by AwakenGoGoGo
2 Comments - Last post 1 minute ago by damianea103
60 Comments - Last post 1 minute ago by PoeticKatana
13 Comments - Last post 4 minutes ago by Cim
95 Comments - Last post 10 minutes ago by CASA0
2 Comments - Last post 48 minutes ago by CTPAX001RUS
10,112 Comments - Last post 1 hour ago by popocho
Current System ---
The giveaway creator is able to input a Steam key when making the giveaway. This key may be displayed to the winner of the giveaway by toggling a button to "Show Key," or hidden from the winner by toggling it to "Hide Key."
Suggestion (from UltraTaber) ---
Add a button the the winner's page called "Accept Key" which will then display the key to the winner (assuming the creator has toggled his button to "Show Key"). This is a one-time event, independent of the creator's toggle, and once triggered, cannot be undone. Once the button is pressed, it will be known that the key has been seen and possibly used by the winner.
Benefits ---
Drawbacks ---
Comment has been collapsed.