Flutterby™! : I had to verify the eyes hurt Google

Next unread comment / Catchup all unread comments User Account Info | Logout | XML/Pilot/etc versions | Long version (with comments) | Weblog archives | Site Map | | Browse Topics

I had to verify the eyes hurt Google

2024-04-09 00:25:02.988716+02 by Dan Lyke 4 comments

I had to verify the "eyes hurt" Google trends theme for myself, and, sure, the graph is eye-rollingly worth a giggle, but the map... Sigh. I weep for humanity.

https://trends.google.com/tren...hurt&date=now%201-d&geo=US&hl=en

[ related topics: Humor Photography Maps and Mapping ]

comments in ascending chronological order (reverse):

#Comment Re: I had to verify the eyes hurt Google made: 2024-04-09 09:47:24.840707+02 by: spc476

What is with this eclipse? I don't recall this level of fervor over the 2017 eclipse, which seemed to be just as big, if not bigger (since that one went from Washington state to South Carolina). Did we really get that much stupider in seven years?

#Comment Re: I had to verify the eyes hurt Google made: 2024-04-09 15:44:34.695975+02 by: DaveP [edit history]

Uh… in 2017 we had this

Crap. URL breakage due to line-wrapping, but apparently making it a link fixes that.

#Comment Re: I had to verify the eyes hurt Google made: 2024-04-09 20:07:34.308911+02 by: Dan Lyke

Interesting. Thanks for the bug report. I've fought the line wrapping thing a couple of times.

#Comment Re: I had to verify the eyes hurt Google made: 2024-04-10 21:16:40.504872+02 by: spc476

I hate to defend Trump here, but ... there is no context in the photo that this is Trump looking at an eclipse. For all I know, he could be looking up at Trump Tower, or maybe a 50' mirror suspended beneath a helicopter.

Add your own comment:

(If anyone ever actually uses Webmention/indie-action to post here, please email me)




Format with:

(You should probably use "Text" mode: URLs will be mostly recognized and linked, _underscore quoted_ text is looked up in a glossary, _underscore quoted_ (http://xyz.pdq) becomes a link, without the link in the parenthesis it becomes a <cite> tag. All <cite>ed text will point to the Flutterby knowledge base. Two enters (ie: a blank line) gets you a new paragraph, special treatment for paragraphs that are manually indented or start with "#" (as in "#include" or "#!/usr/bin/perl"), "/* " or ">" (as in a quoted message) or look like lists, or within a paragraph you can use a number of HTML tags:

p, img, br, hr, a, sub, sup, tt, i, b, h1, h2, h3, h4, h5, h6, cite, em, strong, code, samp, kbd, pre, blockquote, address, ol, dl, ul, dt, dd, li, dir, menu, table, tr, td, th

Comment policy

We will not edit your comments. However, we may delete your comments, or cause them to be hidden behind another link, if we feel they detract from the conversation. Commercial plugs are fine, if they are relevant to the conversation, and if you don't try to pretend to be a consumer. Annoying endorsements will be deleted if you're lucky, if you're not a whole bunch of people smarter and more articulate than you will ridicule you, and we will leave such ridicule in place.

Flutterby™ is a trademark claimed by

Dan Lyke
for the web publications at www.flutterby.com and www.flutterby.net.