Dear Maintainer,

In my understanding,the main reason for not building webrtc support is GPL
incompatible license of BoringSSL [1]

There are also other technical reasons, but missing audio / video call support
is a major drawback and gstreamer powered webrtc support in webkitgtk can still
take a long time to come by.

Last month BoringSSL license was switched to Apache 2.0 [2], making one of the
primary reason for not enabling this support go away.

Please consider enabling webrtc support via libwebrtc since boringSSL is now
GPL compatible. If not for trixie, at least we can have in trixie-backports.

Especially with the recent changes in Mozilla ToS (they backtracked a bit after
backlash - but they have not restored the documentation where they promised to
never sell personal data), dependency on Google for funding and many other bad
defaults make people look for an alternative. The only non Google alternative
usable today is GNOME Web, but missing WebRTC support is a big drawback for
audio / video calls.


[1] https://www.slideshare.net/slideshow/webrtc-support-in-webkitgtk-and-
wpewebkit-with-gstreamer-status-update/276562055#6
[2]
https://github.com/google/boringssl/commit/33d1049b1f730d2725bb09b2256fd5fe4c46b17e