it happens often that people disable it in the past because they got scared by the description and forgot about it then complain that apps are not working as expected and need to be told to enable it
I have read maybe a thousand messages on the forum already and I don’t agree that it happens “often” to any reasonable sense of the word. As it is already hidden behind an advanced submenu, it posed no danger whatsoever. If you think people previously were not disabling it due to wisdom, but rather due to stupidity, feel free to open a modal confirmation once after the next upgrade to remind the user that they should enable it if that’s their thing, but don’t take this away from us.
I never use DC calls with random DC contacts, and I have various options for VoIP with ones whom I trust. Similarly, the circle to which I would be willing to do DC VoIP would be different compared to those who I would be willing to do some casual games with (or see also available collaborative real time chat webxdc).
There aren’t that many public webxdc that rely on P2P exclusively to work in the first place. It would make sense to have a toggle for consent either globally, per webxdc, per group or per sender.
It is possible to disable P2P or at least forcing TURN by many competing messaging apps.
Also, did you know that such P2P solutions not only leak your WAN IP, but also your LAN IPs that may be able to fingerprint you further?
Disclosing your IP (and networking fingerprint!) to your own chatmail server is not the same threat level as disclosing it to every contact. In certain circumstances, it would also enable them with silent pings to
track your whereabouts throughout the day,
how your delay and bandwidth capability change with network roaming kind and signal strength,
determine how many and what kind of devices you use at what times of the day,