• viking@infosec.pub
    link
    fedilink
    arrow-up
    33
    ·
    5 days ago

    As if they’d impose maximum penalties, no matter how deserved. But hey, fingers crossed!

    And imho the whole issue can be avoided by using mobile websites and/or alternative app front-ends for meta services, if you can’t steer clear of them altogether.

    And blocking apps from using background data should seal the deal.

    • masterofn001@lemmy.ca
      link
      fedilink
      arrow-up
      14
      ·
      edit-2
      5 days ago

      I have webrtc completely disabled in browsers.

      I tell everyone, and I abide by : never use an app if you can use the website. If they only have an app be prepared to be fucked.

      I also use a VPN / firewall / DNS filter (by domain and by IP). Rethink or invizible provide all 3 in 1 on android. On linux rotating VPNs, rotating local DNS resolvers [dnscrypt-proxy with local doh with blacklists], and strict firewall rules.

      *Facebook* , *meta*, *Instagram* etc are blocked in and out. As are Google “safety” domains, and a lot of their APIs.

      Privacy may be inconvenient, but selling (giving away for likes) your soul to the devil could cost you a lot more.

      • viking@infosec.pub
        link
        fedilink
        arrow-up
        2
        ·
        5 days ago

        Same here, in my productive browser (Fennc on mobile, stock Firefox on desktop) WebRTC is blocked. I keep a chrome variant around in case anything truly doesn’t work (Cromite on mobile, Edge on Windows, since I have to use some MS applications for work that I don’t care to install on my system).

        I rotate VPN servers, not services though.