Check out our comments and trackback policy You Link We Follow, You Comment We Promote

Jun 28 2008

EMI Sues Hi5, VideoEgg for Copyright Infringement

Bilal Hameed   |  25 Views

image-thumb42 EMI Sues Hi5, VideoEgg for Copyright Infringement

TechCrunch is reporting that EMI has filed a lawsuit against Hi5, VideoEgg and ten other defendants alleging them of "massive and blatant" copyright infringements.

The lawsuit basically alleges Hi5 of posting musical videos on its social network without prior notice or permission of EMI. EMI has been particularly active in suing companies in the recent past, AllofMP3, YouTube, Apple, MP3Tunes, XM Radio and Infospace being some of the affected companies.

The dragging of VideoEgg into the lawsuit depicts that EMI is interested in penalizing everyone that the deem associated with the copyright infringement in anyway. VideoEgg is the company that serves videos on Hi5 and plenty of other social networks. However there contract with Hi5 ended in April 2008. The ten other defendants might be the executives of these two companies and or other service providers.

VideoEgg on the other hand maintains that they received on DMCA takedown notice from EMI ever and hence are working within the law here. VideoEgg uses AudibleMagic technology to track and identify copyrighted content. AudibleMagic is the same company to whom Youtube consulted once they started getting a lot of lawsuits up there alley just after the Google buyout.

These icons link to social bookmarking sites where readers can share and discover new web pages.
  • SphereIt
  • Facebook
  • TwitThis
  • bodytext
  • Reddit
  • del.icio.us
  • StumbleUpon
  • Technorati
  • E-mail this story to a friend!
  • Print this article!

Related Posts
Recent Posts
 
1 Comment »
Name (required)
E-mail (required - never shown publicly)
URI
Your Comment (smaller size | larger size)
You may use <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong> in your comment.
 
Trackback responses to this post