Cloudflase: Summary and Status – Pale Moon Moun Forum

Because this is a continuing problem at this time, this subject is intending to give a summary and “current statlflase and their promised claims of any browser is more than their” taking their captcha / turnstile pages.

Start the issue

Is jan 31^stUsers reported that, similar to an event of 2022, COPLFLARE’s CAPTCHA / “Report I attack” mode begins with failure and withdrawing browser users. It will soon turn into this time, any UXP browser is not only denied access to CloudFlerare’s “protected” sites. Even Firefox ESR 115 affected.
The community can quickly respond, opening a CloudFlare thread of CloudFlare explaining the problem (which is the only communication channels available to users, see below) and report the issue.
Mozilla’s claim applied to corporate pressure for Firefox ESR, the CloudFlase changes this UXP crash issue not considered in a JavaScript status and does not usually occur. Despite crashes, the CloudFlare does not respond to reports about it, which effectively causes all users in the UXP browser. The crash is resolved to a quick release of pale month 33.6.0.
Shortly after this, Cloudfrare made another change which, this time, causing different kinds of service by prompting the script hanging out what intentional The behavior when the script has not passed a collection of web api checks (because the same behavior is observed in their “officially supported by browsers” as well as if the user agent is included in the License Moon!). The worst symptoms released by a free release of moon pale in the month 33.6.1.1, suffering hanging in the script after the scripting script watchedog kick.

Limited communication channels available and ghosted

CloudFlare has more limited communication channels available. End users can only post to self-help “Community”, Webmasters / Clients can only be direct communication with Cloudfler
However, trying to deal with which channels are available resulting in me ghosted. A request for contact and unlock a dialogue for ongoing issues opened on February 1325, almost 2 weeks ago, which is up to date 0 replies.

Notifications@cloudflare.com wrote:Your request (01388216) has been submitted, and we will meet you soon.

status

Our current situation is and remains any and all websites on the back of a Cloudflase CAPTCHA or attack their “attack pages” the issue of 2022 lasted about 2 weeks. This time we leave the water for about a month of writing, with no visibility of the commercial browsers that they “support the cloudfrare indicators, no official and current discrepancies that they are”
As a result, our project is currently lost daily active users, and we are damaged by our traffic-based income as a result. The longer it lasts, the more damage. Unfortunately my choices are limited.
There are bases for legal action as a final procedure, but international anti-trust litigation is difficult and likely to get better part of a decade to resolve if I go to the US legal system.