This message was deleted.
# helpdesk
s
This message was deleted.
d
you won't need to deploy egress
b
thanks @swift-controller-1011 Kinda thought so, I set it up, tested it and it works The helm chart, though, drove me nuts 😄
d
I think that's just helm/kubernetes in general 😅 tho if you have suggestions about how we could improve the livekit helm chart, please share! 🙏
b
😄 yeah, I really want to keep everything in git and deploy via argo
suggestion: would like to use a secret value from another secret, since the API key is needed for livekit but also my backend needs it so rather than duplicate, read it from somewhere
do webhooks trigger on data sent (ie: chat messages?) need to keep a temporary history if possible
d
we do not trigger webhooks for data sent today.. it could be too noisy depending what's being sent. you can, however, join the room from the backend (using Go SDK), and listen to each data message in the room.
b
I thought about that as well, but wouldn't that show this user in the front-end? Or I suppose the solution would be to simply hide if the user is "SYSTEM" (let's say I call it that)
yeah, that's actually not a bad idea, rather than use my own websocket, I've been doing that but not entirely happy with it- and my own turn etc, such a complicated thing I really like liveit, the front-end dev loves it too 😄
❤️ 2
so you guys built something really cool
d
So you can actually keep the user hidden from others by giving it
hidden: true
grant in the token. docs here
thank you for the kind words!
b
amazing 😄 that's exactly what I need, hidden: true
thanks so much for your help so far, really appreciate it
👍 1
d
let us know if you run into anything else or have any other feedback!
b
Another question , hope it's not too much to keep asking Before we join user to a room we have them in a lobby and I'd like them to see who is already in a room (or at least how many people) I can use the hidden token to connect user to room and get the participants (I presume and not sure it's the best approach), but the docs talk about "roomList" permission What would that list include? The docs could be a bit more detailed, so for example I would issue a token with roomList permission but only for a specific room (don't want them to see all rooms) Would that work? From the API docs I can see I'd only get the total users/ but I would like their names too (ie: the identity) On top of that I would also like to avoid very tech savvy people in getting a hidden token and getting streams and not being seen by their peers Perhaps a bit of an edge case 🙂
d
ah, I don't believe there's a way to list only a single room at the moment. perhaps we could add this option to enforce in
roomList
Rooms contain all of the participants too, so you can go through all of their information from the returned type
b
thanks for the reply
do you mean when I list the rooms, all the participants are listed there already, so I don;'t need to connect to get them?
d
yeah
b
ah, cool but won't be able to use that, since I don't want everyone to see all rooms will figure out a way, again thanks so much for answering messages
👍 1