Being cast in a major pop culture has its disadvantages. There will be supporters who think that an actor or actress is perfect for the role that they just landed. And then, there's the immediate backlash that comes from armchair quarterbacks who envision someone totally different, and start to pick apart any actor lucky enough to land a part, ridiculous as that may seem. The most recent example of this is The Meg co-star Ruby Rose, who faced near-immediate backlash from vocal fans on social media following her casting as Batwoman on The CW's planned Arrow-verse crossover event. And as a result, Rose just left social media, turning off her Twitter account and limiting her Instagram account to approved followers.
Now, we don't know for certain that the Batwoman backlash caused Ruby Rose to leave Twitter. But the last few messages that she Tweeted, as reported by The Hollywood Reporter, suggest that the fan backlash is what prompted the social media exit. Rose wrote:
Ruby Rose is set to become the first LGBTQ lead in a live-action superhero television program, playing Kate Kane on The CW in a crossover event that will mix episodes from shows by Arrow, The Flash and Supergirl. It's believed that The Cw will want to develop a Batwoman program around Rose if audiences respond in kind to her take on the DC character. In the newer version of Kate Kane, introduced in 2006, the character is a lesbian. Which is why Rose seems confused that some fans believe she isn't "lesbian enough" to play Batwoman on a television program.
The timing of Ruby Rose's Twitter exit could be coincidental. But it's looking more likely that the Orange if the New Black star joins Star Wars: The Last Jedi's Kelly Marie Tran and Millie Bobby Brown of Stranger Things as actors forced to leave social media because they didn't want to deal with a steady stream of criticism from a vocal fanbase.
Your Daily Blend of Entertainment News
Thank you for signing up to CinemaBlend. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.