- Feature Articles
- CodeSOD
- Error'd
-
Forums
-
Other Articles
- Random Article
- Alex's Soapbox
- Announcements
- Best of…
- Best of Email
- Best of the Sidebar
- Bring Your Own Code
- Coded Smorgasbord
- Mandatory Fun Day
- Off Topic
- Representative Line
- News Roundup
- Editor's Soapbox
- Software on the Rocks
- Souvenir Potpourri
- Sponsor Post
- Tales from the Interview
- The Daily WTF: Live
- Virtudyne
Admin
Yep, that looks like milliseconds divided by 3600, so it was probably a JS Date object being treated as if it were seconds since 1970.
Admin
The recaptcha one reminds me of a website I found through google search results a few days ago that had a full screen cookie dialogue, but the accept and reject buttons were positioned off screen(as in the dialogue was position fixed to ensure it was always on screen, and the accept/reject buttons could never be brought onto screen without using the F12 developer tools).
I wound up not using the site and reported it with google(as you couldn't see the content so it's a useless site), I doubt they'll do anything, but hopefully it'll get bumped down off the front page until they fix it,
Admin
The hamlet of null, Perth and Kinross is twinned with the town of NaN NSW, and FileNotFound Oregon,
Admin
The captcha not loading is more likely to be caused by some ad/script blocker, the users shoot themselves in the foot with those.
Admin
So is there some new form of recaptcha, where only robots can check the box? Anyone left scratching their heads for more than a few seconds is automatically a human.
Admin
That was an actual legitimate strategy for a long time. If you're a low-enough target, a visible checkbox labeled "please check this" and an off-screen checkbox that shouldn't be checked will remove a lot of your fake handbag scam comment form spam.
(And yes, as a joke, I had a "pick the three numbers that sum to 100" captcha that really just rejected you if you submitted in less than five seconds.)
And hooray, as I redated my post, the captcha expired and couldn't be solved again, as if to prove my point.
Admin
It would still be 472 hours. I think it's more likely a nanosecond clock similar to
clock_gettime(3)on *nix systems. If you convert the hours part to seconds and then divide by1e+09you get almost exactly 1700 seconds, which is a little under half an hour. That seems like a reasonable period for such a countdown timer.