One month ago, we mentioned a key-blocking tool for developers. The proposal was simple: we’ll cover all production costs(*) and make this tool available to any developer who wants it. We were curious to know if they were interested in such a tool in the first place. And we received a ton of feedback from developers, both publicly and privately, and quickly learned that the majority is not interested in such a tool. Only 26 developers signed, despite the fact that major media outlets wrote about it.
Key-blocking – a different approach
We have dozens of ongoing projects and changes in our pipeline in order to constantly improve G2A, most of which require a tremendous amount of IT work. The decision which ones are going to be implemented depends largely on the feedback we receive. In the case of the key-blocking tool, we heard from the greater majority that they are simply not interested in it, as they don’t send review codes to people that cannot prove their credibility (**), and they don’t do massive giveaways. Therefore we have decided it will not be created.
However, everything that we offered still stands – we’ll block review keys and mass sales of giveaway keys. Only now, it will be operated by humans. We believe it is best we take care of this personally, as it can actually resolve the problem for those who face it. In this light, we will be taking inquiries through the G2A Direct platform and we will be individually handing all submitted issues.
(*) That would mean moving other projects we have in the pipeline. Besides, creating such a feature would not be a piece of cake. The complexity of the tool wouldn’t end on “developer puts in the key -> tool blocks it.” A lot more variables come into play on both the developers’ and tool’s side, as you could see from the short description in our previous statement.
(**) Quote: “emails like firstname.lastname@example.org asking for free codes don’t exactly sound legitimate”.