Hi there, I wouldn't be making this post if I saw another one about it, but...

I both dislike centralization and nonfree Javascript. I believe the spirit of Lemmy embraces both ideals, however, Cloudflare both promotes a centralized internet that requires the execution of nonfree scripts to interact with it. I understand that bots (epsecially LLM powered) are a pervasive issue that plagues this (and many other) communities. I also understand that being logged-in prevents the requirement of using Cloudflare's captcha, so that only a one-time login is required, although I'm constantly blocking requests to cloudflareinsignts.com.

Finally, I understand that I the alternatives are not necessarily effective, although it seems to work for many projects. I'm not saying other solutions are better for short or medium term, but I was wondering if the management were planning on eventually replacing it.

you are viewing a single comment's thread
view the rest of the comments
[–] 3 points 5 days ago (3 children)

What problem would be solved by this hypothetical migration?

  • source
  • hideshow 6 child comments
  • [–] 14 points 5 days ago (1 child)

    I trink this is rooted in forward thinking. If cloud flare gets a monopoly in that position (what it arguably already has), they can project all the power of a monopoly about us...

    So this is more about preventing future problems and not solving problems that exist.

  • source
  • parent
  • hideshow 2 child comments
  • [–] -4 points 5 days ago* (2 children)

    So this is more about preventing future problems and not solving problems that exist.

    The question remains unanswered: which problems, hypothetically or otherwise, would this migration solve?

  • source
  • parent
  • hideshow 4 child comments
  • [–] 6 points 5 days ago (1 child)

    Cloudflare projecting its dominating power onto lemmy?

  • source
  • parent
  • hideshow 2 child comments
  • [–] -3 points 5 days ago (2 children)

    Cloudflare projecting its dominating power onto lemmy?

    I'm sorry, this assertion is meaningless scaremongering. What exactly is "projecting it's dominating power" supposed to mean?

    And by the way, may I point out that site maintainers purposely adopted Cloudflare to serve specific purposes?

  • source
  • parent
  • hideshow 4 child comments
  • [–] 3 points 4 days ago* (1 child)

    OK, if there is a monopolistic instance between you and the rest of the world that decides who can reach you and who not and you are depending on that single monopolistic instance, I think we all agree that this is a bad thing.

    Potential threads from this are (but not limited to):

    • cloudflare going up in price and you have to take it.
    • cloudflare is blocking or restricting access to your page, because of political dispute.
    • cloudflare collects meta data to reconstruct user behavior and social relationship and uses it to pressure individuals.
  • source
  • parent
  • hideshow 2 child comments
  • [–] 0 points 4 days ago* (1 child)

    OK, if there is a monopolistic instance between you and the rest of the world that decides who can reach you

    It's the site owners who are rolling out anti-abuse systems. They picked a vendor to meet their needs. I don't think Cloudflare put a gun to their heads to force them to onboard their services. Do you?

    Potential threads from this are (but not limited to):

    You mean "hypothetical", not "potential".

    Meaning, they are imaginary scenarios, and they represent the worst case you could think of.

    You need to ask site owners what is their policy for these hypothetical scenarios you invented. On a technical side, removing anti-abuse protection is all it takes to fix it. This means that no action is required to address any of your hypothetical concerns.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 4 days ago (1 child)

    I really don't know what you are aiming for...

    Concerns about cloudflare becoming an issue are totally valid. Good day.

  • source
  • parent
  • hideshow 2 child comments
  • [–] -1 points 4 days ago

    I really don’t know what you are aiming for…

    If you need anyone to spell it out to you, you are mindlessly complaining about programming.dev adopting anti-abuse services from a service provider. When lightly pressed on the topic, you fail to present a single problem of doing that or even a single coherent argument against it.

    In short, you failed to point out any problem involving or any reason to replace an anti-abuse system. And yet you argue the service should be replaced.

    Is "why" such an insurmountable challenge?

  • source
  • parent
  • [–] 1 point 4 days ago* (1 child)

    to serve specific purposes

    You're asking for specifics on their concerns while not providing the specifics that were already in place in your claim here.

    They acknowledged and included reasons for the Cloudflare adoption in their original post.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 4 days ago

    You’re asking for specifics on their concerns while not providing the specifics that were already in place in your claim here.

    If you want to change something, the very least that's expected of you is that the change actually fixes something.

    If you can't even put together a description of exactly what's broken, obviously you can't tell if your proposal is even able to fix anything.

    And may I point out the fact that this very discussion starts by admitting that alternatives are not effective?

    Change for the sake of change is a pointless endeavour. Moreso if it comes from mindless militancy.

  • source
  • parent
  • [–] 4 points 5 days ago (2 children)

    I use Firefox Focus on my mobile and I can't enter sites with CloudFlare because it says my browser is incompatible. It gets annoying when I ramp up my privacy on the Internet and sites outright refuse to load if they see I don't allow cookies and trackers. I'd rather see broken js-free website than pitch black CloudFlare page.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 4 points 5 days ago (1 child)

    I use Firefox Focus on my mobile and I can’t enter sites with CloudFlare because it says my browser is incompatible.

    I also use Firefox Focus and I never experienced that issue at all. Are you sure this is a Cloudflare issue?

    Also, site owners are purposely using Cloudflare to protect themselves from abnormal traffic. If site owners are the ones paying Cloudflare to lift these barriers, why do you interpret this issue as a problem created by Cloudflare?

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 5 days ago (1 child)

    Are you sure this is a Cloudflare issue?

    For shits and giggles I logged into programming.dev with Firefox Focus, and suffice to say I'm posting this with that browser.

    I also did some tweaking and I did noticed that it I configure Firefox Focus to strip all types of tracking (akin to NoScript) then Cloudflare complains about extensions.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 5 days ago (1 child)

    Exactly that, Cloudflare complains about extensions. It's a matter of aggressive tracking protection. I can view Anubis protected sites just fine, only the Cloudflare ones prevent access.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 5 days ago (1 child)

    Exactly that, Cloudflare complains about extensions.

    What you are describing is not browser incompatibility. It's default fallback page that Cloudflare shows when it fails to run its javascript code.

    Site owners such as programming.dev maintainers purposely onboarded Cloudflare to run those scripts, as that's how their anti-abuse system works.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 5 days ago (1 child)

    The 'browser incompatibility' is what's written on the fallback page. The question was about the problem that migration from Cloudflare would solve and I provided one particular problem. Not that it affects me personally, because I use a standalone app for Lemmy, but I assume there are some people that do not wish to run Cloudflare js

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 5 days ago

    The ‘browser incompatibility’ is what’s written on the fallback page.

    No. The page clearly says "Incompatible browser extension or network configuration".

    It then lists a number of troubleshooting steps to get the page to work.

    The question was about the problem that migration from Cloudflare would solve and I provided one particular problem.

    I don't think so. Site maintainers are expecting your browser to run the scripts to detect and prevent abuse, and you are going way out of your way to not run them. You are not describing a problem.

  • source
  • parent
  • [–] 4 points 5 days ago* (last edited 5 days ago) (1 child)

    Personally, my local Cloudflare seems to have some problem with IPv6 and some sites won't load. On my desktop I've set Firefox to use IPv4 for such sites, but on my phone I need to use mobile data (which doesn't support IPv6). I don't think it's a common problem, but you did ask.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 5 days ago (1 child)

    Personally, my local Cloudflare seems to have some problem with IPv6 and many sites won’t load.

    Some global ISPs still struggle with IPv6. I recall that until somewhat recently Vodafone didn't supported it at all. Are you sure this is a Cloudflare issue?

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 5 days ago (1 child)

    Cloudflare gives its 522 error, but I can load via IPv6 from the same city. I've also found the issue with Cf in front of servers I run on a different continent, so I've been able to do some good testing and have spent plenty of time looking into it. I haven't found any other Cloudflare locations with the problem, but there's plenty of them.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 5 days ago* (1 child)

    Cloudflare gives its 522 error

    This means Cloudflare is forwarding the request but the origin server times out. Meaning, it's the origin server that is unable to handle the IPv6 request.

    https://developers.cloudflare.com/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-522/

  • source
  • parent
  • hideshow 2 child comments