LiveKit Community

right now this is what we're doing:

```        const at = new AccessToken(API_KEY, API_SECRET, {
            identity: participantName,
        });```

access token is internal to LK.. so not sure if it's a good idea to expose the claims in there to clients

well I feel like lk should be able to accept a token that has extra metadata that can be forwarded to the clients

could use that to easily add custom features on top of the livekit layer like roles without having to modify livekit

I see.. so this is something you are comfortable with all users seeing

and if its in the token, we don't need to worry about propagating or storing that data when the participants are rendering a new track

we can also trust it when its in the token because we can always validate the sig

sweet, do you want me to file anything on github?

you can file an issue and note that it's a feature

Added some info on the Websocket connect bug, i'd say it's top 2 on our priority list right now

Didn't go too deep into the code but it looks like the participant is the uid and the first session disconnects WS -&gt; refreshes -&gt; connects -&gt; Peer connection from session1 fails -&gt; cleanup participant (uid is the same) -&gt; kills new connection

Not sure how accurate that is but I think thats the pattern i see

If i wait a bit like close tab -&gt; reopen new tab it seems to work better

Nice to meet you, Edward! Welcome! :wave::skin-tone-4: 

good to meet you Edward! definitely. will add you shortly

<@U01KZ61GV5Z> is there any way that lk can clear out everything related to a user the minute their socket disconnects instead of 5-10 seconds after?

so for disconnections we rely on the peerconnection, not websocket. currently the peerconnection goes from connected to disconnected after 5s

what is the need to clear the user out earlier?

if a user refreshes their screen, there's no guarantee for us that we will call `unpublishTracks` in time before the browser loads again

I'm trying to see if I can hook into `beforeunload` in the browser and how consistent that is for disconnecting

LK does detect reconnects.. and I'm sure we can make it so that it sends unpublished when that reconnect happens..