Apart from Cloudflare being an access restricted walled garden that harms interoperability, I really do not want my content on CF & I do not want CF content reaching me. This bug is one of many issues likely caused by Cloudflare:

https://lemmy.dbzer0.com/post/4806490

I would like to flip a switch that has the effect of making my whole UX Cloudflare-free. Cloudflare is antithetical to decentralization and it has clearly broken the #Lemmy network.

  • fbmac@lemmy.fbmac.net
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    cloudflare has an option to serve your content inside tor without an exit node, is that better or worse?

    I’m using it to allow my ipv6 only server be visible for ipv4 users, maybe I’ll think on alternatives now

    • diyrebel@lemmy.dbzer0.comOP
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      Better or worse depends on who you ask.

      I boycott Cloudflare and I avoid it. Some CF hosts are configured to whitelist Tor so we don’t encounter a block screen or captcha. For me that is actually worse because I could inadvertently interact with a CF website without knowing about the CF MitM. I want to be blocked by Cloudflare because it helps me avoid those sites.

      The CF onion (IIUC) cuts out the exit node which is good. But CF is still a MitM so for me that’s useless.

      Some users might not care that CF has a view on all their packets - they just don’t want to be blocked. So for them the onion is a bonus.