That would mean spending money though, which is quite a requirement for non-profit devs/streamers.
Absolutely - that’s why whole clientID system is quite counter-intuitive.
I see what you mean by security reasons here, and well - fair enough.
What I had in my eyes was just a Authorisation page in settings with table somewhat like this:
| Name | Oauth token | More info | Remove? |
|---|---|---|---|
| Streamlabs | ************************************** | [show] | [X] |
| StreamElements | ************************************** | [show] | [X] |
| That funny app with timer | ************************************** | [show] | [X] |
| My own app 1 | ************************************** | [show] | [X] |
| CREATE NEW OAUTH |
Where you can either use already created oauth somewhere or you can create new one with your custom name and custom scopes (visible after clicking “More info” button, along with other possible information like how old is oauth, when it was last used etc, whatever possible and wanted).
Taken many (if not most, what would be my wild guess) users don’t even know they can revoke oauth access and don’t remember what apps they give their access to, this would allow for much more control and higher feeling of security (not even mentioning looking much more professional). And also - “forever” tokens would make life so much easier for both devs and users, that’s for sure.
One of reasons I started writing my own bot was my absolute bottomless hatred for having to re-authorize Streamlabs every time (sometimes every day, sometimes once a week, still - pain in the wrong place).
Well, that’s what sometimes happening, but to not overreact and be fair - it’s quite random. While I was making this bot I had to re-authorise it 3 times in one day, and other time it lasted few days.
With streamlabs chatbot it’s also random, but on average have to re-authorise every week - sometimes everyday, sometimes it will last for month.
It might be only ~5 mins everytime it happens, but when it happens right as the stream is starting, it’s surely a setback right at the start.
But also, thanks for the talk, I feel like I got to understand authorisation system a bit more now, even though it’s still super confusing.