Hey, i dont see, how this helps to identify a stream. Especially this Service is not a public well-known service and is mostly developed by yourself (u didnt mentioned that in your text)
I think, a Streamer also has some more social media channels were they could link back to their stream they own. I would not trust such a service but i would trust their Twitter-Accounts or Facebook-Accounts... 🤔
Yeah @SeaLife is right, most people are going to not know what keyoxide is, or not care, and instead will just look for a link to Twitter and look at the Twitter account for a link back to the streaming site.
This is also related to #511 which lets websites mark up these links between each other in a way that can be parsed if you really want to have that be machine-readable. But in reality a human-visible link between each profile is going to provide a better user experience for most people anyway.
Just to throw this out there, IndieAuth is a very small addition to OAuth 2.0 which adds identity into the system in a much lighter weight way than OpenID Connect. Mastodon could easily add this extension to return the user ID of the user who just authenticated. The login form on OwnCast would ask the user to enter their server name, and do discovery on the server to send the user there to log in.
I did a talk about how Mastodon/ActivityPub apps can use IndieAuth to accomplish this kind of thing. The video is available -- of course -- on my website: https://aaronparecki.com/2020/09/22/25/activitypub-oauth-2-1