Movies: 1135
Comments: 67725
Members: 718
Online: 0 Guests: 100
  • strict warning: Non-static method view::load() should not be called statically in /home/corona/public_html/modules/views/views.module on line 823.
  • strict warning: Declaration of views_plugin_display::options_validate() should be compatible with views_plugin::options_validate(&$form, &$form_state) in /home/corona/public_html/modules/views/plugins/views_plugin_display.inc on line 1684.
  • strict warning: Declaration of views_plugin_display::options_submit() should be compatible with views_plugin::options_submit(&$form, &$form_state) in /home/corona/public_html/modules/views/plugins/views_plugin_display.inc on line 1684.
  • strict warning: Declaration of date_plugin_display_attachment::options() should be compatible with views_object::options() in /home/corona/public_html/modules/date/includes/date_plugin_display_attachment.inc on line 33.
  • warning: Attempt to modify property of non-object in /home/corona/public_html/modules/date/includes/date_plugin_display_attachment.inc on line 24.
  • warning: Attempt to modify property of non-object in /home/corona/public_html/modules/date/includes/date_plugin_display_attachment.inc on line 25.
  • warning: Attempt to modify property of non-object in /home/corona/public_html/modules/date/includes/date_plugin_display_attachment.inc on line 26.
  • warning: Attempt to modify property of non-object in /home/corona/public_html/modules/date/includes/date_plugin_display_attachment.inc on line 28.
  • warning: Attempt to modify property of non-object in /home/corona/public_html/modules/date/includes/date_plugin_display_attachment.inc on line 29.
  • warning: Attempt to modify property of non-object in /home/corona/public_html/modules/date/includes/date_plugin_display_attachment.inc on line 30.
  • warning: Attempt to modify property of non-object in /home/corona/public_html/modules/date/includes/date_plugin_display_attachment.inc on line 31.
  • strict warning: Declaration of views_handler_field_comment::init() should be compatible with views_handler_field::init(&$view, $options) in /home/corona/public_html/modules/views/modules/comment/views_handler_field_comment.inc on line 48.
  • strict warning: Declaration of views_handler_field_user::init() should be compatible with views_handler_field::init(&$view, $options) in /home/corona/public_html/modules/views/modules/user/views_handler_field_user.inc on line 48.
  • strict warning: Declaration of views_handler_field_comment_username::init() should be compatible with views_handler_field::init(&$view, $options) in /home/corona/public_html/modules/views/modules/comment/views_handler_field_comment_username.inc on line 48.
  • strict warning: Declaration of views_handler_argument::init() should be compatible with views_handler::init(&$view, $options) in /home/corona/public_html/modules/views/handlers/views_handler_argument.inc on line 699.
  • strict warning: Declaration of views_handler_filter::options_validate() should be compatible with views_handler::options_validate($form, &$form_state) in /home/corona/public_html/modules/views/handlers/views_handler_filter.inc on line 584.
  • strict warning: Declaration of views_handler_filter::options_submit() should be compatible with views_handler::options_submit($form, &$form_state) in /home/corona/public_html/modules/views/handlers/views_handler_filter.inc on line 584.
  • strict warning: Declaration of views_plugin_style_default::options() should be compatible with views_object::options() in /home/corona/public_html/modules/views/plugins/views_plugin_style_default.inc on line 25.
  • strict warning: Declaration of views_plugin_row::options_validate() should be compatible with views_plugin::options_validate(&$form, &$form_state) in /home/corona/public_html/modules/views/plugins/views_plugin_row.inc on line 61.
  • strict warning: Declaration of views_plugin_row::options_submit() should be compatible with views_plugin::options_submit(&$form, &$form_state) in /home/corona/public_html/modules/views/plugins/views_plugin_row.inc on line 61.
  • warning: Creating default object from empty value in /home/corona/public_html/modules/views/modules/comment/views_handler_field_comment_username.inc on line 32.
  • strict warning: Non-static method view::load() should not be called statically in /home/corona/public_html/modules/views/views.module on line 823.
  • strict warning: Non-static method view::load() should not be called statically in /home/corona/public_html/modules/views/views.module on line 823.
  • strict warning: Non-static method view::load() should not be called statically in /home/corona/public_html/modules/views/views.module on line 823.
  • strict warning: Non-static method view::load() should not be called statically in /home/corona/public_html/modules/views/views.module on line 823.
  • strict warning: Non-static method view::load() should not be called statically in /home/corona/public_html/modules/views/views.module on line 823.
  • strict warning: Declaration of content_handler_field::options() should be compatible with views_object::options() in /home/corona/public_html/modules/cck/includes/views/handlers/content_handler_field.inc on line 170.
film news

Rumor shot down: Olivia Wilde is not Tomb Raider Lara Croft

Posted by Patrick Sauriol on Sunday, October 30, 2011

This is what happens when some movie websites pick up any piece of gossip and run with it as fact. It's something that's pissed me off as the new generation of site owners seek traffic over quality of content. Before this turns into an editorial rant, here's what sparked this latest non-event.

A Brazilian movie site called Cinepop published a story "confirming" that Olivia Wilde would be the next Lara Croft in a new Tomb Raider movie. The film is in the early stages of development, and has been for a year, but this is the first report that linked Wilde to the role.

The story goes out on Google RSS syndication and news. Other movie websites then rush to covered the news, seeking their own wave of attention for the headline.

The fact is Olivia Wilde hasn't been hired to play Lara Croft in Tomb Raider. Using her own Twitter account, the House actress issued this bit of rumor control last evening: "Hey internet, I'm not the new Lara Croft. But I've seen about 23 drag queen impersonators tonight in new york so all is well!"

So endeth the rumor, but not my rant. Bail out now if you don't want to read griping about the present state of the internet movie blogosphere.

Here's the problem: there's a good number of websites/blogs out there in Internetspace that don't care if you have the correct information. All they want to get you to do is click their headline and deliver another impression so they can make a tenth of a penny from serving ads.

These websites are run by owners that don't care about getting the story right, or supplying context for the news item they're regurgitating on your screen. They think of you as a mindless drone, one that they can get to jump like a trained dog. And to a large extent, the way that Google and the world of search engine marketing is, they're right.

Traffic is more important than facts or doing a decent job reporting what's known. Every site gets a story wrong now and then, and this site isn't above that. The difference between Coming Attractions and these other sites that I'm talking about is that these other guys keep repeating the same "mistakes" over and over, but they're not mistakes. It's intentional and done on purpose.

I don't expect this rant to reach the eyeballs of the readers that visit those other sites, but to my readers that read Coming Attractions, know this: I won't lower this site to that level.

All that said...Olivia Wilde isn't a bad choice to play the next Lara Croft.

WarCry
Location:
Posts: 152
Posted: 8 years 6 weeks ago

You're absolutely right on the editorial part. Don't just throw crap out there and hope no one notices you have no proof, and hope everyone's forgotten when you're proven wrong.

I would say, though, that Olivia Wilde making a Twitter-post saying "It's not me" isn't really all that strong of a condemnation. Bradely Cooper and Quinton Jackson both denied, denied, denied involvement with the A-Team move right up until they confirmed it.

What I think SHOULD have happened is that every site and media outlet that posted the story needed - and needs in the future - to make sure they're reporting the story as "Unconfirmed reports" or "Unverified rumor." Making any definitive statement one way or the other creates the same problem. If, next week, Wilde and the studio comes out and says "Yeah, it's real, we just weren't ready to announce yet, but since it's leaked...." you're going to look a bit silly for simply taking a Twitter-post as "definitive." Actors and their reps can, do, and will lie about stuff like this, a lot of times because of contract negotiations and/or NDAs in place.

 

All that said, tough, I'd far prefer you err - as you tend to do - with the "Hey, we don't know if it's true, may be complete BS, but here's what we're hearing" types of stories. It's one of the reasons when I hear ANY rumor, this is the first place I check for more or clarified news.

 You don't have to like it, you just have to do it. --Richard Marcinko