> There are so many abuse protection companies out there that don't stigmatize non-western Internet users.
And there are also cases it's apparent and relevant to grandstand about, this is not one. The DDOS pages required me to go through hoops and try several devices even browsing from the US to this US site. Not typical, sure, but it is what makes the hyper charged complaints feel particularly off center.
> Also, do we really think that Columbia's IT people are that bad?
Nah, they are probably great. Likely very busy and wishing they had more staff/time like most "cost center" IT teams though.
> I doubt a page like this would get a substantial DDoS.
Any particular page is unlikely to get a DDoS but the site as a whole is likely to get them relatively frequently (disgruntled students and the like on top of the usual gamut) which is why the entire site is fronted by a CDN and given a single protection policy rather than setting everything up for each page posted.
> Making it inaccessible to half the world, particularly much of the country that the article is about, is conceding ahead of time to the people that might want to DDoS a page like this in the first place.
Again, these are probably good points on a general Cloudflare rant but posting them in this case actually makes the argument sound weaker since it's a presumed cause that doesn't seem to be the actual cause.
In an ideal world where we had extra IT time and could solve every problem and were talking about generalities of providers like Cloudflare I'd 100% agree with you. Sometimes reality gets in the way and it's not the reason we want to get fired up about or the reason we want to get fired up about isn't as easy or important to solve as we'd like it to be in the particular case though. Alternatively, if the topic were about Cloudflare instead of this particular school hosting this particular article I'd still agree as well. In this case it's none of the above - and why I say it's about not needing to baby it instead of an alternative. Similar load based protections for this site would also have kicked in with any provider, regardless our thoughts on Cloudflare.
And there are also cases it's apparent and relevant to grandstand about, this is not one. The DDOS pages required me to go through hoops and try several devices even browsing from the US to this US site. Not typical, sure, but it is what makes the hyper charged complaints feel particularly off center.
> Also, do we really think that Columbia's IT people are that bad?
Nah, they are probably great. Likely very busy and wishing they had more staff/time like most "cost center" IT teams though.
> I doubt a page like this would get a substantial DDoS.
Any particular page is unlikely to get a DDoS but the site as a whole is likely to get them relatively frequently (disgruntled students and the like on top of the usual gamut) which is why the entire site is fronted by a CDN and given a single protection policy rather than setting everything up for each page posted.
> Making it inaccessible to half the world, particularly much of the country that the article is about, is conceding ahead of time to the people that might want to DDoS a page like this in the first place.
Again, these are probably good points on a general Cloudflare rant but posting them in this case actually makes the argument sound weaker since it's a presumed cause that doesn't seem to be the actual cause.
In an ideal world where we had extra IT time and could solve every problem and were talking about generalities of providers like Cloudflare I'd 100% agree with you. Sometimes reality gets in the way and it's not the reason we want to get fired up about or the reason we want to get fired up about isn't as easy or important to solve as we'd like it to be in the particular case though. Alternatively, if the topic were about Cloudflare instead of this particular school hosting this particular article I'd still agree as well. In this case it's none of the above - and why I say it's about not needing to baby it instead of an alternative. Similar load based protections for this site would also have kicked in with any provider, regardless our thoughts on Cloudflare.