>forced to reinstall chrome

>>59201041
>not chromium

>bullied to install updates

>>59201041
>not installing firefox

>>59201462
>not installing GNU+Icecat

>>59201782
>not install lynx

>not going out and getting a life

>>59201041
>>59201065
>>59201462
>>59201782
>>59201845
>not Ungoogled Chromium

>>59202360
Chromium is shit like any Chrome based browser.

>>59202376
>Ungoogled Chromium
>Chromium
wew

>>59202412
Still shit

>>59202453
Have you actually used it?

>>59202482
I started on chrome based browsers. Reason why I'm on firefox.

>>59202491
>firefox - old
>chromium - new
>I MUST GO BACK

>>59202491
Stop trying to dodge my question- Have you actually used it?

>>59202514
yes. I switched back because webrtc wasn' t working.

>>59202514
Irrelevant as my critique does not pivot on privacy issues that it solves but rather the functionality of the browser.

>>59202540
>>59202536
>Actually using webshittyc
kek

>>59202577
webrtc is good faggot.

who the fuck offers free STUN/TURN services otherwise?

in an ideal world, everyone would have IPv6 and NATs would be DOA

>>59202651
>not caring about IP leakage
You're probably the kind of person who unironically uses Windows 10.

>>59202577
I don't but customization is the biggest thing for me.

>>59202789
wrong.

I have a gentoo hypervisor which runs numerous virtual machines, including: 4x Fedora 25 Server boxes and one Alpine Linux Docker container host running certain javascript web services.

my chromebook and my macbook also run GNU/Linux exclusively.

I even have a pissdroid phone, though that isn't exactly something to be proud of.

WebRTC does not leak your IP, it merely facilitates distributed web technologies, but you're just a cuck who likes depending on master/slave old timey, IPv4 NAT, bullshit that should have died with the invention of torrents, distributed hash tables and NAT-free IPv6.