the emo boy from horton hears a who

you’re welcome

Original post by @morallygrayautisticscientist here, this post was so funny I decided to draw it lol.

Panel by panel below:

DEATH: Even if I remove Dean from the playing field, we're still left with you, loyal, dogged Sam, who I suspect will never rest until he sets his brother free. 10x23

///

GOD JACK: Cas needed to remain locked away, because The Empty can't come to Heaven, not again. We wouldn't survive it.

///

GOD JACK: So you see, Dean. I had to kill you. It had to be done. But I... couldn't do it myself. It... I just couldn't.

GOD JACK: So I put out the hit; any monster who could get it done gets entry to Heaven.

GOD JACK: And it worked. (JENNY: [No, I'm not the big boss.] I just called dibs.)

GOD JACK: After that, it was easy. Tell Bobby that Cas helped, let him give that some weight, some truth. You had to think Cas was saved. So you wouldn't meddle.

DEAN: Meddle in what?

but it's an entirely new level of tragic when somebody you've actually spoken to gets turned into a bot account. it's like peeking at a zombie apocalypse through the window and realizing one of the shambling corpses was your friend.

and then the zombie catches sight of you, lurches up to your window, and shouts through the glass that they accidentally reported your account to tumblr and you'll be deactivated unless you click this link.

if you get something like this ↑ they're gonna follow up by instructing you to contact tumblr support on discord and give you contact info; or they're gonna link a website that looks sort of like tumblr support and say you have to email them; or any variety of "you must now contact tumblr, here is how you contact tumblr."

whatever they send you, it Does Not lead to tumblr. it leads to the master zombie that bit them and inducted them into the ranks of the undead, and will bite you the second they have your email and password. i might be confusing zombies and vampires. anyway,

it's easier to fall for these messages because the blog doesn't LOOK like a bot blog, because it ISN'T a bot blog. it's a normal person's blog that got accessed by a bot, meaning the blog's content CLEARLY looks like a real active user when you click on it. and yes—it might even be a blog you already know. sometimes bots like this go down a blog's DMs or reblogs and message people they've previously interacted with.

1. The court holds Google responsible for statements made by its AI, considering them Google's statements (search engines have limited liability for results in their engine as they're the words of other sites/companies/people), meaning when their AI lies/hallucinates they're liable for the defamation/harm resulting from those statements.

2. Google's defense that customers are generally aware of the lack of reliability and are responsible for fact checking was dismissed. As the court pointed out, that would "significantly diminish" AI Search's stated purpose and it can't be distinguished from Google's business practices/statements as a search tool.

3. Studies have found about 91% of Google's everyday AI responses are accurate, leaving millions of searches per HOUR with potential liability for falsehoods. 56% of correct responses weren't supported by the sources the AI listed. Both of which mean Google is now liable for a LOT more AI "errors."

4. Google was held liable for 80% of court costs in this case and this precedent is expected to reverberate around the world. This is a massive shift from the 3rd-party search provider role Google has previously played and it comes right as they've tied ALL searches to their AI search.

“…Let alone, wear on my sleeve.”