UK Band, Muse, Had Its Social Media Handles Hijacked By Meta’s AI Agent
English band, Muse, recently had its social media handles “forcibly taken” away by Meta. The parent company of Facebook is now being used for its new AI Agent, also named Muse. How Muse (the band) lost control and the rights to its social media handles to Muse (the AI agent) are still unclear, but it […] The post UK Band, Muse, Had Its Social Media Handles Hijacked By Meta’s AI Agent appeared…
English rock band Muse recently found their social media accounts seized by Meta, the parent company behind Facebook. The AI-powered entity bearing the same name as the band is set to take over their online presence. The circumstances surrounding the takeover remain shrouded in mystery, sparking debates over the ethics of large platforms arbitrarily claiming control over handles.
Muse had secured the trademark for their name in 1999 and had been using @muse on Instagram and X for years, predating Meta's acquisition. The band first noticed the change when their handle shifted to @museband. Despite not being affiliated with Meta, the band decided to adopt @museband to avoid any potential legal disputes. However, it seems they may have relinquished their original @Muse handle in the process.
Officially, Meta prohibits the buying, selling, or trading of social media handles. Nevertheless, a clandestine market for these names exists due to their value and uniqueness. Meta CEO Mark Zuckerberg inadvertently tagged the band's account while referencing the AI agent, highlighting the confusion surrounding the matter. The band's name change and loss of handles have led to some crossed wires, with Meta executives incorrectly tagging the band's account instead of the AI agent.
So far, neither the company nor the band have issued any statements regarding the situation. Interestingly, the band's music often reflects their concerns about technology and its potential for social oppression, adding an ironic twist to the unfolding events.
Written by urgent.news from Lowyat.NET's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.