Worried about Review Process

[BarryCarlyon]

@AnD4D

You wrote the colour wheel example? That’s the program I’m referring to that seemed overly complicated. Not the profile_extension. That appears to be quite straight forward, almost plug and play. As I said, I couldn’t get the backend to actually work, but I was missing the var my_ebs… which is key

I was confused to which example you were referring to

@AnD4D

Let’s use myself as an example. I stream using my app, and it creates a multiplayer room called “and4d”. You then go to my channel as a viewer, and load up the extension. In a perfect situation, the extension would simply join the room “and4d”… but the problem is that the extension doesn’t know the name of the streamer, so it doesn’t know which room to connect to.

As already covered, onAuthorised returns the channelID.

In an ideal world you’d do everything by ID, to account for name changes.

But if you have the channelID from the JWT, and a service, and an app access token, you can get the channel name from the users API (A user is a channel and a channel is a user)

To cite my profile example

BarryCarlyon/twitch_profile_extension/blob/main/ebs/server.js#L110

url: 'https://api.twitch.tv/helix/users?id=' + req.extension.user_id,

becomes

url: 'https://api.twitch.tv/helix/users?id=' + req.extension.channel_id,

And the profile extension becomes a channel profile extension

@AnD4D

That’s what I originally wanted to do, but the unfortunate thing is that the game is run on the streamer’s device. The extension is obviously run on the viewer’s device.

You’ll need a relay server, which I though you had since you referenced a database.

As otherwise there’s no way to reach the gamer’s PC (ignoring opening holes in the firewall and leaking the streamers IP address and the fact you need a SSL Cert)