@briankrebs Just to note, though, CloudFlare's "customer" is the content host. So it's not really surprising that, from their perspective, allowing content hosts to block scrapers (i.e., allowing "writer" to block "readers") is more attractive than allowing "readers" to block "writers."
And it's not inconsistent with their CEO's (in my view, honest and principled) stance on free speech: if you believe, generally, in enabling more speech, enabling speakers to block some listeners (on grounds of IP violation or whatever) makes a lot of sense.
(I'm not saying I agree, but I think it's relevant that this is both aligned with their business interests and consistent with the philosophy Prince has espoused. It's not just some political pivot a la Zuck.)
=> More informations about this toot | View the thread | More toots from _dm@infosec.exchange
=> View briankrebs@infosec.exchange profile
text/geminiThis content has been proxied by September (3851b).