Master WebRTC: From Media Capture to Peer Connection https://jsdev.space/webrtc-intro-guide/ #javascript #webrtc
Master WebRTC: From Media Capture to Peer Connection https://jsdev.space/webrtc-intro-guide/ #javascript #webrtc
Lots of interesting stuff for the next Movim summer release
You'll be able to share your webcam and screen simultaneously
The feature is already available on https://mov.im/ if you want to try it out
All those video-conference improvements are possible thanks to @nlnet !
In January 2007, Ignite Realtime launched the red5 plugin for Openfire, introducing flash-based media server capabilities. Over time, #WebRTC became the standard for audio and video conferencing. Ignite's work evolved into various plugins supporting diverse media use cases.
#XMPP is regaining popularity, with Openfire leading due to its flexibility.
For our audio/video functionality, we have refocused on enhancing media interoperability in XMPP. More info in our blog: https://discourse.igniterealtime.org/t/webrtc-based-audio-and-video-in-openfire-2025/95683
@mray @cwebber would love to know as well.
For people not in the know, @librecast is a R&D initiative that's innovating the internet stack with support of @NGIZero and @nlnet
First, to enable #multicast on the unicast internet an overlay network is planned, based on #WebRTC. See:
https://librecast.net/librecast-strategy-2025.html
#Librecast LIVE will bring all the technology together, to demonstrate and be a reference implementation. With #ActivityPub support being planned. See:
@zwol my favourite hack in this space is how #WebRTC demultiplexes the 3.5 protocols (ICE SRTP/SRTCP and DTLS) that all arrive on the same port.
https://datatracker.ietf.org/doc/html/rfc5764#section-5.1.2
Read it and weep.
tl;dr switch on the first byte of the packet.
(Although tbh I've never seen anything bad happen as a result.)
Here's a deeply nerdy talk I gave about sending lidar data over webRTC data channels using 5g.
https://www.youtube.com/watch?v=wpHojBJ6nLI&list=PLDaEs5k2Xy-u-vwyKswF2viDuROt9yNiM&index=8
So, dann schauen wir mal, ob Europa in der Lage ist, die DS-GVO anzuwenden und die Verantwortlichen der irischen Datenschutzkommission (Data Protection Commission, DPC) die cojones haben, Meta mit der Höchststrafe für Datenschutzverstöße zu beglücken.
https://localmess.github.io/
Was denkst du?
#webRTC #meta #yandex #dsgvo
Both #Yandex and #Meta used obfuscation techniques to hide that the traffic occured and/or that the apps were listening to these requests:
Meta traffic was using #WebRTC, which does not show up in the browser's developer tools
Yandex traffic looked non-local
Yandex apps started listening only after several days
BTW: Apparently, Meta stopped doing this yesterday. But they probably still have the mapping DB.
All the details by the researchers here.
https://localmess.github.io/
Staggering how far #Meta will go to de-anonymise users.
I was actually surprised it took so long because this is not a new loophole. We discussed this issue almost 10 years ago in a different context: #WebRTC allows to circumvent the secure origin policy.
https://github.com/w3c/webappsec-csp/issues/92
I made a PoC back then
https://lgrahl.de/examples/dc/webrtc-circumvent-secure-origin.html
which still works to this day. It is also hard to prevent because the PoC doesn't do anything that is forbidden. It leverages a currently essential part of the STUN protocol.
Don't get me wrong, I'm all in for making an effort to remove all user-controllable input, but now we might see shortcuts being taken to get things fixed quickly, potentially destroying a bunch of nice and niche use cases along the way.
@pixelschubsi #webxdc in #DeltaChat doesn't use #webrtc for real-time channels, please, I recommend you to read and try out things before spreading fake information
for your information webxdc uses #iroh for #p2p in DeltaChat
Today is allocated to looking under the hood of the #webrtc data channel and figuring out what has changed in the 8 years since I last looked properly.
(Eeek, almost everything!)
"... browser-to-browser file sharing and messaging.
Your files and messages will not be stored in the cloud or uploaded to a server.
UnCloud uses WebRTC direct communication between browsers."
i have started to use avatar icons in my chat app, i am not completely satisfied yet but i am getting closer to the standard design of chat apps...
Wechsel zu LiveKit: OpenTalk setzt auf eine noch leistungsfähigere WebRTC-Technologie!
Adaptive Streams, Simulcast & optimierte Skalierbarkeit machen Videokonferenzen noch besser.
Mehr dazu: https://opentalk.eu/de/news/webrtc-upgrade-opentalk-wechselt-zu-livekit
Anyone gotten #simplepeer working for sending/receiving data? Or has time and network/NAT development left it broken?
Another question for my #WebRTC friends: Do you know what *exactly* makes an audio stream sync up with a video stream in libwebrtc?
Is it the a=msid:<stream-id> <track-id> grouping on the sender side?
Is it the a=msid:<stream-id> <track-id> grouping on the receiver side?
Is it both? Or is it something else entirely, e.g. do we need to create a MediaStream from both tracks on the sender or the receiver? Or do we need to attach both audio and video tracks to the same <video> element?
I've seen cryptex being merged in libsrtp. Haven't found a cryptex issue in the libwebrtc issue tracker. Do we know more on the status quo on cryptex support in #WebRTC?
(Summoning all my WebRTC friends here )
@steely_glint @s @danjenkins @lminiero @murillo
who has a #webrtc experience report
After taking a closer look at #XMPP clients for the #linux desktop, there's this frustrating "tie" for finding a favorite.
#Dino, which is likeable for being able to do video and audio calls, only has limited support for multi-user chat (complete with fancy moderation tools). These audio and video calls it can do are AMD64-only at this time.
#Gajim, which is likeable for being able to do multi-user chat well (with great moderation tools), alas, can't do audio and video calls to the other XMPP clients (like, say, #Conversations, as they use a newer #WebRTC-based method now).
So there's this strange situation where one is tempted to use both at the same time.
My takeaway is that #Conversations for #Android is the only xmpp client that I would possibly and carefully recommend to family and friends at this time, as it can cover all of the above. (#Monal on #iOS/#MacOS only has "partial" support for Multi-user chat, BTW.)
Yes I'm aware of the existence of Snikket, Quicksy, and Prav. No need to chime in on those.