Reply to thread

Message

<blockquote data-quote="SeriousHoax" data-source="post: 1122125" data-attributes="member: 78686">Only when something you use is using WebRTC like video calling, live-streaming, etc. that sort of things, not in case of regular browsing. Besides, the IP leakage part is for people who always use VPNs. Even when you use VPN, your actual IP could leak when using something that relies on WebRTC. Since you neither use video calling/live-streaming regularly nor using a VPN 24/7, you have no reason to disable WebRTC or worry about IP leaks in general. Your IP is known to every site you visit anyway.Extension-based approach seems easier for AV vendors, less bugs but I also prefer using as few extensions as possible so........<img class="smilie smilie--emoji" loading="lazy" alt="🤷‍♂️" title="Man shrugging&nbsp; &nbsp; :man_shrugging:" src="https://cdn.jsdelivr.net/joypixels/assets/6.6/png/unicode/64/1f937-2642.png" data-shortname=":man_shrugging:" /></blockquote>

[QUOTE="SeriousHoax, post: 1122125, member: 78686"] Only when something you use is using WebRTC like video calling, live-streaming, etc. that sort of things, not in case of regular browsing. Besides, the IP leakage part is for people who always use VPNs. Even when you use VPN, your actual IP could leak when using something that relies on WebRTC. Since you neither use video calling/live-streaming regularly nor using a VPN 24/7, you have no reason to disable WebRTC or worry about IP leaks in general. Your IP is known to every site you visit anyway. Extension-based approach seems easier for AV vendors, less bugs but I also prefer using as few extensions as possible so........🤷‍♂️ [/QUOTE]

Verification