On my phone: Mozilla/5.0 (Linux; Android 4.4.3; HTC6500LVW Build/KTU84L) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/39.0.2171.93 Mobile Safari/537.36
You are the end result of a “would you push the button” prompt where the prompt was “you have unlimited godlike powers but you appear to all and sundry to be an impetuous child” – Zero, 2022
You are the end result of a “would you push the button” prompt where the prompt was “you have unlimited godlike powers but you appear to all and sundry to be an impetuous child” – Zero, 2022
You are the end result of a “would you push the button” prompt where the prompt was “you have unlimited godlike powers but you appear to all and sundry to be an impetuous child” – Zero, 2022
You are the end result of a “would you push the button” prompt where the prompt was “you have unlimited godlike powers but you appear to all and sundry to be an impetuous child” – Zero, 2022
Mozilla/5.0 (Linux; Android 4.4.2; SPH-L710 Build/KOT49H) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/39.0.2171.93 Mobile Safari/537.36
You are the end result of a “would you push the button” prompt where the prompt was “you have unlimited godlike powers but you appear to all and sundry to be an impetuous child” – Zero, 2022
Mozilla/5.0 (X11; FreeBSD amd64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/39.0.2171.95 Safari/537.36
As a web dev I'm pleased to see only one person has posted an IE string, and appears to have done so as a joke.
Fun fact: IE11 sabotaged its UA string (and other identifying properties which now report themselves as "Mozilla") specifically to prevent browser detection, but is far enough from rendering and event standards that professional developers still have to make browser-specific allowances. Because UA strings can change at a moment's notice and we can't always count on that Trident 7.0, so far the best way to detect it is if (!window.ActiveXObject && 'ActiveXObject' in window).
I'll go ahead and call an ambulance for any Javascript programmers, because as they comprehend the scale of everything that is wrong with this, they'll likely attempt suicide.
Also, it tries to pass as IE7 in Compat Mode. I mean that is the rendering it's supposed to use, but it actually sets the rest of the internal bookkeeping in a manner that other IE's don't in Compat Mode. But it still doesn't pick up IE7 conditional comments.
You are the end result of a “would you push the button” prompt where the prompt was “you have unlimited godlike powers but you appear to all and sundry to be an impetuous child” – Zero, 2022
Mozilla/5.0 (Windows NT 5.1; rv:38.0) Gecko/20100101 Firefox/38.0
You are the end result of a “would you push the button” prompt where the prompt was “you have unlimited godlike powers but you appear to all and sundry to be an impetuous child” – Zero, 2022
Let's try some on a school computer.
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Firefox/45.0
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.112 Safari/537.36
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_3) AppleWebKit/601.4.4 (KHTML, like Gecko) Version/9.0.3 Safari/601.4.4
Comments
Mozilla/5.0 (Linux; Android 5.0.2; Nexus 7 Build/LRX22G) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/39.0.2171.93 Safari/537.36
(The other Jane)
Fun fact: IE11 sabotaged its UA string (and other identifying properties which now report themselves as "Mozilla") specifically to prevent browser detection, but is far enough from rendering and event standards that professional developers still have to make browser-specific allowances. Because UA strings can change at a moment's notice and we can't always count on that Trident 7.0, so far the best way to detect it is if (!window.ActiveXObject && 'ActiveXObject' in window).
I'll go ahead and call an ambulance for any Javascript programmers, because as they comprehend the scale of everything that is wrong with this, they'll likely attempt suicide.
Also, it tries to pass as IE7 in Compat Mode. I mean that is the rendering it's supposed to use, but it actually sets the rest of the internal bookkeeping in a manner that other IE's don't in Compat Mode. But it still doesn't pick up IE7 conditional comments.
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Firefox/45.0
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.112 Safari/537.36
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_3) AppleWebKit/601.4.4 (KHTML, like Gecko) Version/9.0.3 Safari/601.4.4