Worried about Review Process

WLG3R · September 9, 2020, 4:29pm

If you don’t have a dedicated game server, you can always do some serverless middleman that can act like a proxy, like Firebase or AWS.

Firesplash · September 9, 2020, 4:31pm

This.
This is basicly what we do (but with our own server)

AnD4D · September 9, 2020, 4:41pm

That’s most likely the case, which is exactly why I’ve offered to pay people to do this for me. I’m aware of another team working in the same program that I am who have the same issue, so who knows.

Thanks for the help

Firesplash · September 9, 2020, 4:45pm

The point is you want hands-on your code and system which is a time consuming thing. Also you want someone to explain it to you (you wrote you want to know how it works to maintain it).
This means you basically want someone to do it for you and then teach you to do it (what is exactly what we are trying here) - Please don’t get me wrong, this is not meant rude.

BarryCarlyon · September 9, 2020, 6:42pm

I was confused to which example you were referring 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

github.com

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


      
          Similar to cors probably want to make this route specific
          rather than global
          
          But if this server only does extension traffic then all good to global
          */
          app
              .use('/:route?', (req, res, next) => {
                  if (req.headers['authorization']) {
                      let [ type, auth ] = req.headers['authorization'].split(' ');
          
                      if (type == 'Bearer') {
                          jwt.verify(
                              auth,
                              config.secret,
                              (err, decoded) => {
                                  if (err) {
                                      console.log('JWT Error', err);
          
                                      res.status('401').json({error: true, message: 'Invalid authorization'});
                                      return;
                                  }

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

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)