I cannot see the image because it’s posted in the walled garden of #Cloudflare, which excludes me. Would someone please repost the image on an open-access instance or website so everyone can view it?
Can say that my #Cloudflare#R2 block storage for #Mastodon is massively growing. A year ago it was stable at ~80-89Gb, but lately it's heading to 200Gb+ #Mastoadmin
How do I get my home IP (via Spectrum) off of the #CloudFlare bad list?
The soccer program my oldest is a part of has a website that uses cloudflare and every time I try to use it from home I'm blocked. My cell phone connection is fine (as are any coffee shop wifi connections).
Help?
Edit: for the record, I do have a OpenVPN connection going at times. Would be a pain if that was the culprit.
»Cloudflare-Alternative:
19 Cloudflare-Alternativen im Überblick«
Hat jemensch von euch Erfahrung mit eines diesen Alternativen oder gar sogar mit einer nicht aufgeführten? Wenn ja, welches könnt ihr aus welchen Argumente und Gründen empfehlen?
(Ich zweifle immer noch welches am "sichersten" und "daten sparsam" ist)
Today, between #gitlab#cloudflare and #firefox, I'm getting an endless loop of some silly attempt to verify that I am human. So it says at least, I don't think it can, but maybe it is recognizing that and that keeps it looping :-) Safari works.
The systemcrafters website is on #cloudflare. This not only enables a tech giant to create profiles of people. #survillancecapitalism It's also very annoying to pass these "verify you are a human" checks when using tor.
Please move to a less invasive provider. Thanks. @daviwil
My host informed me that it is possible to integrate #Cloudflare into my websites to take the pressure off my hosting account CPU (if I understand this correctly), which is already high because I upgraded my services to prevent problems with my websites not loading. It only happens every once in a while, but still.
I thought Cloudflare would be used before hosting, not after. So I am very confused. Going to take a while to wrap my head around this.
So because of my perpetual frustration with Cloudflare, I’ve made a thing. It’s a bit like FeedBurner, but with an emphasis on fetching feeds that are blocked by poor Cloudflare configuration. If there’s a feed that you can’t read in your RSS reader of choice, consider trying it here. It’s a work in progress, but I would appreciate help building my pool of blocked feeds. Currently I can read all the feeds I care about except 1.
Regular reminder that if you don't run your site on HTTPS you're doing yourself and anyone who visits your site a disservice.
This is double extra true for anyone doing ANYTHING related to sex. Even if your hosting provider is cool with what you're hosting, you owe it to the people who use your site to protect their privacy by preventing their ISP and any intermediary from knowing what they're looking at.
@amy@shalien I'm extremely unconvinced that DoH is good for the average person's privacy. It takes a situation where each ISP can snoop on their own users (but many probably won't) and instead concentrates everyone's data at a very small number of huge (and historically, abusive) companies.
Sure, you could change the defaults, but most people won't and this is a worse situation to normal DNS.
I certainly trust my ISP ( @aaisp ) not to snoop more than I trust #cloudflare !
With recent events, i have taken the decision to drop #cloudflare with the transition to new servers, i'll have to figure out what CDN (likely fastly ill try to apply for the foss program) to use and what DNS service to use also we'll have to move to a different S3 provider
During the transition to new servers TransFem.social, and all other TransFem.org services including the Sharkey repo's may experience a down time of up to 48 hours due to DNS nameserver changes
The original decision for using Cloudflare was to prevent spam and ddos attack, and while Cloudflare has done shit in the past the assumption was that they're neutrality would go both ways, this seems to not be the truth, their "neutrality" seems to only apply to harassment sites like kiwifarms.
our new setup is not only a lot more powerful but also comes with a firewall setup and DDOS protection directly from the Colocation provider severely reducing the need for Cloudflares ddos protection
I'm targeting next weekend as deployment date for the new servers, but this is highly depended on the RMA's arriving on time
@mjgardner@Perl@ChristosArgyrop@ovid Certainly it’s an embarrassment considering #Sourceforge has recently joined the exclusive walled-garden of #Cloudflare. I cannot reach any sourceforge.net/* pages. But I can reach perltidy.sourceforge.net because it’s CF with Tor whitelisted. However, I’ll still avoid it on principle. I don’t think I’ve filed bug reports there but certainly I will not in the future.
Little things you can do to save the environment (jlai.lu)