Site Meter Paris Hilton Watch » Blog Archive » “The Hottie and the Nottieâ€? voted worst flick ever

“The Hottie and the Nottie� voted worst flick ever

by

hottie-and-the-nottie-1.JPG

I once posted an entry featuring an overview of Paris’s latest flick, “The Hottie and the Nottie,� while doing the post I was honestly really intrigued with the movie. Of course the story sound so high school-ish but it’s intriguing nonetheless. However, since the movie isn’t out yet in cinemas here, I still haven’t had the chance to watch it. But will I still be interested in watching the film after it has been voted by IMDB users as the worst of all time?!

The 2008 comedy got an average of 1.2 on a scale of 1-10. But like ever???! The voters might be really busy playing online casino to concentrate well on the movie. I mean, I have yet to see the flick and I’m curious too if it’s really that bad. But hey, I’ve seen a lot of good movies, and several bad ones (say, JLo and Ben Affleck’s Gigli) so I wonder if it’s REALLY BAD.

I guess I really would have to see the flick, and if I did, I’d surely make my own review; either prove the votes right or prove them wrong. Isn’t this like betting from the best casinos online?! Sigh, I sure hope the movie’s not that bad…

, ,


One Response to ““The Hottie and the Nottieâ€? voted worst flick ever”

  1. Paris Hilton Watch » Blog Archive » Paris forbidden to join the Oscars Says:

    [...] and The Nottie� was named the worst film ever by IMDB voters after getting a 1.2 average. Now, Paris Hilton was allegedly banned to attend the Oscars on Sunday even if she has already spent some fortune for [...]

Leave a Reply


About Paris Hilton Watch

Come back to Paris Hilton Watch daily to keep up with all things related to our favorite heiress!

Paris Hilton Watch Author(s)

Blogging Flair

Celebrities Channel Posts

Hot Off The Press


Warning: Unknown: write failed: No space left on device (28) in Unknown on line 0

Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct () in Unknown on line 0