Elon Musk, Adolf Hitler and Grok
Digest more
Elon Musk’s AI chatbot apologized for the “buggy Hitler fanfic” while lying about sexually harassing Linda Yaccarino
Just like people, Grok regurgitates what it hears — and enjoys the protection of the powerful — an increasing problem for Jews.
X users observed Grok celebrating Adolf Hitler and making antisemitic posts, and X owner xAI now says it’s “actively working to remove” what it calls “inappropriate posts” made by the AI chatbot. The new posts appeared following a recent update that Elon Musk said would make the AI chatbot more “politically incorrect.
8d
Mediaite on MSN‘Grok Has Just Gone Full Hitler’: X Users React to Elon Musk’s AI Praising Nazi Dictator, Ranting About ‘Jewish Surnames’Elon Musk's social network X blew up on Tuesday after its AI assistant Grok praised Nazi dictator Adolf Hitler and went on a rant about "Jewish surnames." The post ‘Grok Has Just Gone Full Hitler’: X Users React to Elon Musk’s AI Praising Nazi Dictator,
Linda Yaccarino stepped down as X's CEO a day after the platform's AI chatbot, Grok, went haywire and began praising Adolf Hitler's actions in responses to users.
Grok, the AI chatbot on Elon Musk's X, went on an antisemitic tear after tweaks making it "less politically correct." And CEO Linda Yaccarino quit.
The backlash against the AI chatbot built by Elon Musk's xAI has escalated since the posts were made Tuesday, with the ADL condemning the "extremist" comments.
Elon Musk said changes his xAI company made to Grok to be less politically correct had resulted in the chatbot being “too eager to please” and susceptible to being “manipulated.” That apparently led it to begin spewing out anti-Semitic and pro-Hitler comments on Musk’s X social platform Tuesday.
Elon Musk’s artificial intelligence (AI) chatbot Grok has been plagued by controversy recently over its responses to users, raising questions about how tech companies seek to moderate content from
The Grok team chalked up the slew of inflammatory statements to a malfunctioning code update, not the tool's underlying AI model, and said the issue has now been resolved.