SUMMARY I refuse to be actively monitored by CloudFlare while reporting and working on bugs. *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. kde.org is now cloudflare 2. community.kde.org is now cloudaflre 3. bugs.kde.org is too!!! This is wrong. Here is a snippet from https://community.kde.org/Get_Involved/Bug_Reporting "Step 0: Is it a security issue? Do not file bug reports for security issues, as this makes the vulnerability public and could expose users to exploits. Instead, send an email to [email protected] For more information, see https://kde.org/info/security/." Not good (actually bad). Please stop using Cloudflare before we expose generations of software freedom loving people to the internet colonialist. Thanks I will not return to help fix bugs, until Cloudlfare is gone and I feel safe here.
Thanks for sharing your opinion.
Just for the record, the commentary below regarding the use of Cloudflare is factually incorrect. Cloudflare is only used for the following KDE.org sites, which do not include www.kde.org or bugs.kde.org: ; CNAME's to Cloudflare for externally hosted services, order by name. store IN CNAME store.kde.org.cdn.cloudflare.net. websvn IN CNAME websvn.kde.org.cdn.cloudflare.net. ebn IN CNAME ebn.kde.org.cdn.cloudflare.net. forum IN CNAME forum.kde.org.cdn.cloudflare.net. community IN CNAME community.kde.org.cdn.cloudflare.net. userbase IN CNAME userbase.kde.org.cdn.cloudflare.net. techbase IN CNAME techbase.kde.org.cdn.cloudflare.net. blogs IN CNAME blogs.kde.org.cdn.cloudflare.net. dot IN CNAME dot.kde.org.cdn.cloudflare.net. api IN CNAME api.kde.org.cdn.cloudflare.net.