News for hackers. Stuff that matters.
Re:Cloudflare’s service’s questionable practices by duskwuff on Wednesday October 23, 2019 @11:27PM (#21341410)
> It seems the author only has problems with Cloudflare almost completely because he uses Tor.

Partly because they use Tor, partly because they use a browser which supports neither Javascript, frames, nor images (i.e, Lynx). What both of these things have in common is that they are problems of the writer's own creation.

Also, Cloudflare's email address munging is optional. Web site operators can (and usually should) disable it.

Re:Cloudflare’s service’s questionable practices by paulryanrogers on Wednesday October 23, 2019 @11:50PM (#21341508)
> Partly because they use Tor, partly because they use a browser which supports neither Javascript, frames, nor images (i.e, Lynx). What both of these things have in common is that they are problems of the writer's own creation.

Technically it the developers whose sites don't degrade gracefully who created the problem for users. JS, images, frames, and trackability are not required to deliver much of what people want out of the web.

Re:Cloudflare’s service’s questionable practices by OrderlyTiamat on Thursday October 24, 2019 @02:38AM (#21342215)
But then these devs look at the market consuming their site and see that about 0.5% of the users need graceful degrading and decide there are more important issues to work on. Can we blame them?
Re:Cloudflare’s service’s questionable practices by paulryanrogers on Thursday October 24, 2019 @08:54AM (#21344160)
For cases where those features add little or no value, yes we can blame the producers.
Re:Cloudflare’s service’s questionable practices by sasasassy on Thursday October 24, 2019 @05:59AM (#21343028)
That's a bit ironic given that we are browsing a website that degrades gracefully without JavaScript, frames or images.