Thank you for the quick response!
A few concerns…
“use a Server or webpage to handle oAuth loop” still means I have to use a server, which I am trying to avoid, unless you are implying that I write code for a localhost server to capture callbacks. In which case, I’ve considered it, but it’s really an issue of overcomplicating a solution.
“accounts system” is implying a persistence method? But doesn’t necessarily tackle the main issue of bypassing a server hosted callback URI management system. Unless, the accounts system you are mentioning is managed by Twitch, in which case I am unfamiliar.
Parsing chat through IRC was my first idea, though, I would prefer to use PubSub to take advantage of websockets, get accurate data without error in parsing, and bypass the need to read every message looking for a cheer.
Lastly, take a model of the CLI? Assuming you mean to model some code after the CLI to manage the issue myself? In which case, the answer is presumably similar to the “use a Server or webpage” option, which goes back to the overcomplicating the solution thing. Or maybe fork the CLI repo and edit it to fit my needs? Which I also considered, but not sure about the legalities of distributing the CLI through a paid application. Though, if I am 100% honest, I am not sure what you mean by this option.
Again, thanks for the response! Seemingly there isn’t a built in solution, which I kind of expected, though I am thankful for your help!