LQ Suggestions & FeedbackDo you have a suggestion for this site or an idea that will make the site better? This forum is for you.
PLEASE READ THIS FORUM - Information and status updates will also be posted here.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
With an Addon like uMatrix it's possible to block cloudflare for this site.
It still works after that, except for parts of the editor (toolbar buttons). Of course all BBCode can be inserted manually still.
But I do wonder why cloudflare is required for that?!
I don't understand how an ad blocker can help, it has no control over the way the traffic comes from.
Nobody's talking about ad blockers.
You need to see for yourself what uMatrix does.
Of course it can only show me what is visible to the outside.
Maybe LQ is doing more "Cloudflare BS" internally - I don't know. How do you know that?
Location: Fleury-les-Aubrais, 120 km south of Paris
Distribution: Devuan, Debian, Mandrake, Freeduc (the one I used to work on), Slackware, MacOS X
Posts: 251
Rep:
Because it's the way Cloudflare works(and get money to live for sure). I've seen it since I've got sometimes timeouts on LQ: the error message doesn't come from LQ servers but from Cloudflare ones, even saying that LQ uses uses "the always online Cloudflare service". Cloudflare clearly acts as frontal proxy, so it can read all the traffic, including passwords and so on.
Because it's the way Cloudflare works(and get money to live for sure). I've seen it since I've got sometimes timeouts on LQ: the error message doesn't come from LQ servers but from Cloudflare ones, even saying that LQ uses uses "the always online Cloudflare service". Cloudflare clearly acts as frontal proxy, so it can read all the traffic, including passwords and so on.
You're right, of course, though perhaps some have confused Cloudflare with the usual cross site requests to advertisers, etc (I know I did and have to admit that my previous reply was spontaneous and off the cuff).
LQ of course uses Cloudflare and it's correct that you cannot simply block it. You can block some of the scripts, etc but that's about it.
If you ping "www.linuxquestions.org" you can see for yourself that it resolves to "www.linuxquestions.org.cdn.cloudflare.net".
Thank you for the clarifications, cynwulf and Stéphane Ascoët.
I stand corrected (and I could have done that myself had I thought a little harder).
I agree it's less than desirable.
A simply hosted website like they did in 1999 would be much nicer.
But LQ isn't that anymore now, is it.
What would be a better alternative to the sort of services cloudflare provides?
Jeremy used to serve client-side scripts (they make things like the advanced posting editor work) from Google CDNs. He moved them to Cloudflare after people (quite a few, actually) complained.
The part that the OP is complaining about is something else. It would be done by a Cloudflare proxy, not a CDN, and would not be blockable by site visitors. I haven't had a problem, but I'm actually a bit curious as to why LQ needs (or needed) that.
I had wondered what you were all complaining about - just bumped into it myself. Having had gateway issues previously, and (many) timeouts on the old CDNs, this is just another iteration. This seems to be less prone to being intrusive to the client (me) in terms of interruptions I see.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.