A way to go directly to a stream by entering its name

[rakslice]

Checklist

• I understand that Streamlink Twitch GUI is just a launcher for Streamlink
• I have read the contribution guidelines
• I have checked the list of open and recently closed issues
• I have checked the commit log of the master branch

Description

It would be useful if there was a way to go to a stream by entering its exact name as seen in its ordinary twitch URL. A fine version of this would be putting the exact match (modulo display name case) first in the streams/channels search results.

Rationale: A common use case for me is that I want to go to a stream I don't usually follow, usually off a raid in an open chat window where I have the lower case stream name right there in the URL ready to copy-paste. Currently I can enter the name in the search box on the channels page but then I have to hunt through the full screen grid of mostly spam items for the exact thing I just typed in which appears maybe a couple rows in.

[bastimeyer]

The messy search results are caused by Twitch's helix API. The old kraken API returned the matching channel first in the results, which was far better than what's currently being returned. There are also other issues with the channel/stream search endpoint on the helix API, which I've described in #856.

When searching for a channel name, an additional query could be made for a matching channel name whose result gets displayed above the regular search result. However, this would mean that there would always be a duplicate entry due to the regular search results below the exact match, which would not be ideal. As explained several dozens of times, client-side filtering of API responses won't be implemented, so removing the duplicate won't be happening.

Redirecting the user to the channel page on a match is also not ideal, because of accidental matches when searching for a different term which is part of a channel description for example. Adding a checkbox for exact matches could be done, but the search-bar component hasn't been touched and updated in a very very long time, so I'm not really willing to extend the bad design with more features like this. I've already explained my motivation for working on any new stuff on this project in #849 when I had to rewrite the entire data-implementation for the kraken-to-helix API switch, so see this as additional context to your feature request.

[rakslice]

I bailed out of this world when streamlink/streamlink#2680 happened so let's say, whatever else, I appreciate how frustrating it all is