Settings and activity
2 results found
-
2,542 votes
An error occurred while saving the comment 
TheBoxyBear
supported this idea
·
An error occurred while saving the comment TheBoxyBear
commented
Renaming the categories is just a band aid fix for a deeper issue. Currently, Twitch is able to distinguish between categories of the same name as both appear in search results with their respective cover art. The problem comes down to the category page url using the name of the category rather than a unique Id. Although this makes the url easier to remember and identify, it makes it impossible to specify the exact category between duplicates and the server returns the first category it finds that matches the name.
The solution: Make the category endpoint use either the IGDB unfriendly name instead of the friendly name and make links to category pages contain the unfriendly name (the name as it appears in the url of the IGDB page). This would prevent collisions whilst keeping the url easy to remember and identify. In order to maintain compatibility with existing links and urls generated by third-party applications, the endpoint should keep supporting urls with category names, even if the resulting category isn't always the right one. Because differenciating between friendly and unfriendly names would be quite tricky if not impossible, perhaps the unfriendly name could be provided through a url parameter "?name=".
Once implemented, renaming individual categories could still be considered to make it easier to tell which is which, especially when the categories have no cover art or have very similar art. However, the priority remains to fix the endpoint which would immediately reduce the severity of the issue for existing and upcoming categories. In its current state, the category is effectively wiped from existence, including all livestreams under that category. This lessens the enjoyment of Twitch for fans of the specific category, lessens discoverability of streamers and deprives the game from the publicity generated by streams if both games are from different developers, so is the case with the 2017 game Stray by developer rxi.
-
18 votes
An error occurred while saving the comment TheBoxyBear
commented
According the the Q&A on the new help page regarding tags https://help.twitch.tv/s/article/guide-to-tags The decision to remove custom tags seems to have a lot to do with the lengthy approval and localization process.
Having both custom and localized tags would be very complicated if not impossible though I don't believe localized tags are a necessity. By localized tag, I am specifically talking about a single tag showing the same stream while also going under different names based on the locale of the user. Localized tags under the proposed system would take all the old tags and their localizations and separate them as stand-alone, language specific tags. For example: 'Hard Mode' and 'Mode Difficile' would be different tags. The logic being that streams have a primary language and tend to use custom tags that match that language. A viewer that would search for a tag using its name in a certain language is very likely to also be searching for streams in that same language.
Regarding the submission process, the mere addition of custom tags should lead to fewer submissions as there is now an alternative. As for the submissions that are sent, they could be approved as single-language tags without being localized, further cutting down the length of the process. A downside to this would be that approving tags in a single language will cause duplicate submissions that need to be analysed and approved once again. In order to prevent these duplicates, the submission process could be made so that a user can request a localization to an existing tag. Since the tag has already been approved, all that needs to be done is either coming up with a localization or making sure the one submitted matches the meaning of the original tag.
TheBoxyBear
shared this idea
·
It should be up to Twitch to update to modern web standards, not IGDB to apply bandaid solutions on a game by game basis just to make Twitch work. The url scheme can work for channels since all channels names must be unique and the channel database is controlled by Twitch, but it can't work for categories not held to the same restriction. The responsibility especially shouldn't be put on the shoulders of a third party that provides the game database.