Newly created challenges via API automatically removed about online-go.com

[anoek]

For live games you need to maintain a connection with the websocket, without that the server reasons your browser has gone away and will remove the live challenge.

For correspondence games that's wot the case.

[anoek]

In specific you'll need to mimic what the official client does for keeping challenges alive: https://github.com/online-go/online-go.com/blob/devel/src/components/ChallengeModal/ChallengeModal.tsx#L715

[adamreisnz]

I'm creating a challenge via the API, this doesn't use web socket connections?

E.g. I'm intending to use these methods for game management/control: https://ogs.docs.apiary.io/#reference/games/game-movement/make-a-move-in-a-game

Where can I find documentation about the socket implementation?

[anoek]

You'll need to use the websocket protocol for any game playing (and live challenge keep alives)

If you're going to roll your own websocket implementation https://docs.online-go.com/goban/modules/protocol.html is probably a good start. https://github.com/online-go/goban/tree/main/src/engine/protocol for the typescript defs themselves.

[adamreisnz]

Thanks, I'll have a look into those.

Does the socket protocol still require an oauth application to be registered etc? Does it use the same authentication mechanism as the API with access tokens?

[anoek]

You get a jwt from your oauth process and pass that in as part of the authentication process for the websocket

[adamreisnz]

The token I got from the OAuth process doesn't look like a JWT, it's just a short 30 character random string.
Is there a different OAuth endpoint which issues JWT tokens?

[anoek]

mm, yeah not the oauth, from the https://online-go.com/api/v1/ui/config that you would get after you're authenticated