https://livekit.io logo
Join Slack
Powered by
This message was deleted.
# helpdesk
s
This message was deleted.
b
I need something similar to this https://docs.daily.co/reference/daily-js/instance-methods/set-user-data as we are doing parity check for the current supported features that we built on the top of Daily.
a
Hi @bulky-finland-78364, when someone connects to a room they could loop through all current participants and get their metadata - then you can also use the metadata updated handlers to fire off code when anyone's metadata updates. That should cover "getting metadata for existing participants when you join a room" and also "keep that metadata updated afterwards"
b
Hi @ancient-cpu-94526 thanks for this prompt response. Are you pointing to 
setMetadata()
right?
a
yep - setMetadata for setting the metadata on the participant. then you can use the ParticipantMetadataChanged event to listen to those updates
but when first joining a room and you need the metadata of the people already in there.....you can just loop through the participants and read their metadata. it will be on them already!
b
Great! Thanks @ancient-cpu-94526
a
May I ask if there is - besides this metadata - some custom “appData” element, which can be transported transparently through the server, for instance to be handed out with a particular video publishing or a data channel?
a
You can can also use generic livekit events to just hook into webrtc datachannels to send reliable or unreliable events @adventurous-twilight-28575
or if you are looking for metadata that is more generic than participant metadata, you can also set metadata on the "room" that is accessible to all participants
a
Thanks. I meant something similar to the “appData” object which can be attached to each publication in Mediasoup. I’m using this excessively in order to provide extra information regarding my current audio/video/data publication, which might be useful for subscribers to decide, if they want to join or not
✅ 1
a
ah I see! maybe then worth noting that livekit includes a lot of info about each "track", but that's not data that you can modify in a custom way besides when you create the track and determine how you want it to be set up
(i'm coming from mediasoup too btw)
a
😀 I’m probably on that path too, not decided yet
👍 1
Today I got another motivation kick: Managed to marry my Android app with a GOLANG module and talk to it via unix socket. Tomorrow I will add my three simultaneous H.264 encoders in order to publish simulcast with H.264 hardware encoders and a GOLANG livekit client
Sorry for high jacking this thread
a
you are all good. you are also way more technically sophisticated than I am! sounds badass but your encoding wizardry is beyond me. I just do metaverse stuff at framevr.io
a
😀 Well, now at the third platform after Kurento has stopped development and MS is not sufficient here. Thanks for the flowers. We will see, how it works out. At the moment I’m more concerned to be not able to picture all the whistles and bells I have added over the years on the LK platform. Hope to talk you again if there are hurdles
✅ 1
a
twilio programmable video just went down today too!
a
Forey?
*Forever?
a
"Twilio will also end-of-life (EOL) its Programmable Video as a standalone product. “Given it’s such a niche area and a relatively small part of our portfolio, we believe partnering with video industry leaders is the best way to ensure long-term product innovation for our customers,” Lawson said. “Removing Programmable Video from our portfolio will also allow Communications to more effectively focus on our pillar products - Messaging, Voice, and Email.”"
a
Arghh…
Said, but in our business the only constant is the constant change (and then it changes again, to speak with Tom Petty)
a
only thing that stays the same is webrtc (so far, and with variegated, ever changing browser support) lol
a
Yeah. As long as they stick with 1.x changes are just marginal
✅ 1
2 Views
Open in Slack
PreviousNext
Powered by