In order to bypass the GDPR, Meta apparently plans to move to a "Pay for your Rights" approach

The Wall Street Journal reported that Meta plans to move to a “Pay for your Rights” model, where EU users will have to pay $ 168 a year (€ 160 a year) if they don’t agree to give up their fundamental right to privacy on platforms such as Instagram and Facebook. History has shown that Meta’s regulator, the Irish DPC, is likely to agree to any way that Meta can bypass the GDPR. However, the company may also be able to use six words from a recent Court of Justice (CJEU) ruling to support its approach.

  • AllNewTypeFace@leminal.space
    62·
    1 year ago

    Of course, that just means you don’t see ads on Instagram/Facebook. They still collect your data, aggregate it and trade it with data brokers, so the ads you see elsewhere (not to mention prices you’re offered) will become more accurate. In fact, it’s not unlikely that the behavioural data of people who pay to opt out of being spammed with ads will be more valuable to data brokers.

    Also, for those who don’t pay, the ads will get more frequent and annoying to induce them to pay. (See also: Spotify)

    • Ferk@lemmy.ml
      16·
      1 year ago

      In fact, it’s not unlikely that the behavioural data of people who pay to opt out of being spammed with ads will be more valuable to data brokers.

      True. This is why the AdNauseam extension doesn’t simply “hide” ads, but it goes out of its way to actually simulate clicks for ALL ads, causing algorithms to be unable to more accurately profile you and making the pay-per-click model fall on its face. If everyone did that, advertisers would have to pay for completely meaningless clicks making it no longer worth it to advertise this way.

      Though it’s still not a solution to privacy, since it still gives some insight on your tastes by allowing them to know what websites do you frequently visit.

        • TheAnonymouseJoker@lemmy.ml
          36·
          1 year ago

          Firefox and Chrome browsers have an about:performance page that show how much CPU and RAM each extension take in realtime. This extension probably consumes no more than 1% CPU, considering LibRedirect for example takes 0.5% CPU.