Legality of extensions requiring viewers' OAuth permissions

So we can neither request Twitch API or Steam ID oAuth? Granted both would need to fire a popup or link offsite which is all the things extensions want to prevent.

It would also seem that we can’t suggest to users to “go to the broadcasters forum/website” to link these accounts together either, (my first extension was blocked due to a link to the broadcasters own website even though when I explicitly asked “someone at Twitch” if that was ok, I was told it was, but thats a different story altogether).

Either way it’s a tough dimension to work in (300px x 500px) so I’d probably never shove oAuth in there but I would direct to the EBS/backend service in order to provide a way for users to link accounts, which ought to be permitted under the “needs to do this in order to function” rule. But I have ways around this rule, since we’ve been sending people offsite from chat for ages to link accounts… So I have a fair tonne of steamID’s on file for $caster_viewers

I’m not saying allow us to fire popup’s whilly nilly, but allow us to send users off Twitch to the EBS and back.