Settings and activity
1 result found
-
25 votes
Thank you for your detailed submission and articulating the usefulness of the badge for game developers. We agree with the sentiment and additional context can be found in the deprecation announcement. You are correct that there was an increase in requests to verify organizations. This process is also used to gain access to other features such as Drops campaigns and game analytics. Product updates to limit requests for a global badge and remove confusion, such as enabling the badge only on a matching category as you mention, will take considerable time while continuing to block new developers from using these organization features. This change will reestablish the 1-week SLA for organization requests and an improved implementation of the game developer badge can be considered in the future while we enable new game developers to onboard.
An error occurred while saving the comment 
Xenflux
supported this idea
·
The timing is really amazing. This news is really unfortunate, if it's true.
Historically, I've seen some streamers had a habit of giving developers VIP to better highlight their messages. (And even then, they weren't always certain they were the actual developers, instead going off of good faith, because not every developer even knew the badge existed.)
Recently, while watching streams of new/unknown games (it's currently Steam Next Fest, as I write this), I've advocated to developers that happened to show up in chat that they go through the process to get the badge.
I believe it was just last week or so that I also suggested the very same idea presented here: to change/highlight the badge when the stream was set to a category associated with the developer. This would make it easier for the developer to be noticed in chat and by the streamer, just generally improving engagement. It seems like such an easy win and value-add for Twitch, I strongly recommend considering this direction rather than dropping the badge entirely.