@jensimmons I would wish, that Apple contributes their WebRTC implementation for WebKit upstream to the Open Source project so that Gnome Web and other Free Software web browser would finally support WebRTC.
@jensimmons I would wish, that Apple contributes their WebRTC implementation for WebKit upstream to the Open Source project so that Gnome Web and other Free Software web browser would finally support WebRTC.
Here comes Movim 0.31, codename Kameny
With this exciting new release you'll be able to share simultaneously your screen and webcam when calling your friends , switch quickly between your one-to-one chats and chatrooms
, add your pronoun in your profile
...
Checkout our release note to discover all the other new features of this version
https://mov.im/community/pubsub.movim.eu/Movim/here-comes-movim-0-31-codename-kameny-yQUilX
Thanks again to @nlnet for their support on the video-conference features
Thrilled to join the WHEP spec as an editor! Helping make WebRTC simpler with HTTP originated media sessions. Excited to push Server Sent Offers for v1. Join the conversation at IETF 123!
https://everycastlabs.uk/thrilled-to-be-joining-the-whep-spec-as-an-editor
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:
HELP US SOCIALLY DEVELOP VIA CHAT! [JITSI + INTERFACE = CHAT ROUTLETTE STYLE]
@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
This is Major FFMPEG has merged WHIP Muxer for sub second latency streaming!!!
WHIP is the acronym for WebRTC-HTTP Ingestion Protocol. It is a low-latency live-streaming specification building off WebRTC.
Read more about it here
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.
@ip6li habe grade auch nen Interview abgelehnt, weil #MicrosoftTeams geb' ich mir nicht!
@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
This is the day! #KamailioWorld Conferece 2025 starts at 9:00am, Berlin, Germany: https://www.kamailioworld.com/k2025/ It is going to be two intense days, packed with presentations, attended by a full house! You can watch the live stream at: https://www.youtube.com/@KamailioWorld #opensource #telephony #voip #vonr #5G #webrtc