I'm not reading this.
I do miss the days when technical reports were clear and concise. This one has some interesting information, but it’s buried under a mountain of empty AI-written bloat.
If I want AI slop, I'll gladly have a chat with my paid $20 bucks Gemini account.
Like this, its purpose is to fly under the radar unless your figurative ears are pricked up and primed to detect the telltale signs. Fuck this shit.
The Wikipedia article on detecting AI writing is a big help if you need to calibrate your sensors: https://en.wikipedia.org/wiki/Wikipedia:Signs_of_AI_writing
If you try and run a site that has content that LLMs want or expensive calls that require a lot of compute and can exhaust resources if they are over used the attack is relentless. It can be a full time job trying to stop people who are dedicated to scrapping the shit out of your site.
Even CF doesnt even really stop it any more. The agent run browsers seem to bypass it with relative ease.
It doesnt .. look very new?
Another problem I have with it - they state that the red text was such a huge problem, but then their solution is to... Keep only using red? Why not, for example, make certain non-failure notifications yellow or some other color? Surely using other colors should at least be tested as a solution, right? The whole process seems bizarre to me
Or it might not
The majority of the traffic on the internet is from so-called "bots"
If a "bot" hits this "interface" does that count as being "seen"
The web's failing, its inability (unwillingness) to accept non-interactive use (no good for advertising), is Cloudflare's success
A strange thing to celebrate. MITM'ing the majority of the web for "security". Could there be a better way
Another source of amusement is the "You've been blocked" Cloudflare page showing the user's IP address and suggesting contacting the site operator might solve the problem
The truth is that sending an acceptable user-agent header value solves the problem
"You" are not being blocked (Cloudflare does not who "you" are), your IP address is not being blocked, the _request_ you sent was blocked because of crude heuristics
If a site operator wants a certain header value (why) then it should publish the list of acceptable values
Send another request with an acceptable header value and the requests succeeds. It appears "you" are not blocked, same IP address, same living, breathing, thinking person sending the request
Because that is a lot of energy spent too have done advance research for an UI that is basic (just a checkbox), not particularly great and common before and after cloudflare...
And a personal rant, I don't understand how they can be proud of themselves when you see the wasted time and energy supported by users to browse the pages that are being Cloudflare.
Imagine this billions of "click-wait" uselessely done by users everyday worldwide
We needed a new account on $MAJORSITE and we just could not get trough the captcha - I know, it's getting insane - In the end, we gave up, and just told $AI to make the account for us.
Something is going seriously wrong on the internet.
I can't be the only one.
It's slow and annoying, AI overview is good enough for me most of the times so that added time I bet makes websites lose a lot of visits.
Now, websites ask me to verify "I'm human", networks and services are starting to address their users as specifically "humans", and discourse is almost always about whether something or other is written by a "human" instead of just not slop.
I get that reality is what it is, but it just feels icky.
> 5 out of 8 points versus just 3 for "I am human." For the verifying state, it was even more dramatic — 7.5 versus 0.5.
n × p >= 5? (Sample size and margins of errors. Is 5:3 even meaningful or is this rather random personal preference?) Apparent splitting of missing or inconclusive data points? (7.5 vs. 0.5 out of a total of 8 subjects.) What kind of (social) research is this supposed to be?
