Adsense HTML

Showing posts with label third party conduct. Show all posts
Showing posts with label third party conduct. Show all posts

Week 7: Liability of ISPs and Infrastructure Providers

This class deals with liability of intermediaries. For example, is an ISP liable for the conduct of its users? Is a web hosting company liable for the content of others that it hosts? Is TripAdvisor liable for reviews of hotels posted by users? Is Google liable for the content that appears on this blog?

Should such intermediaries be liable for the actions of others?

The main reading for the class is the iiNet case:

Seizure of Domain Names

A post from a student:

"Earlier this year an Act was passed by the US government (Combating Online Infringements and Counterfeits Act) which specifically allows the seizure of any website which has been "'primarily designed' to offer goods and services in violation of the Copyright Act and / or the Lanham Act".


In February the US Department of Homeland Security used this new act to seize 83 internet domains. The seizure involved re directing the DNS of that domain to a banner as shown here. One domain in particular was channelsurfing.net, this web site hosted links to other sites which hosted copyrighted material. The site operator Brian McCarthy is now facing court for Criminal Infringement of a Copyright.


As a part of this DNS seizure the DNS hosting provider FreeDNS was disabled. This caused the approximately 84,000 customers of FreeDNS to be redirected to the DHS 'banner', some of whom were not related to the original seizure at all (eg RapGodFathers.com)."


Compare the Australian case of

Cooper v Universal Music Australia Pty Ltd [2006] FCAFC 187


See also

http://news.cnet.com/8301-1023_3-20023918-93.html

http://www.rawstory.com/rs/2011/03/10/new-york-man-faces-five-years-in-jail-for-linking-to-online-videos/

http://act.demandprogress.org/sign/dhscomplaint/?source=front


Fined For Conduct of Facebook Fans

In his judgment Justice Finkelstein held that: "while it cannot be said that Allergy Pathway was responsible for the initial publication of testimonials (the original publisher was the third party who posted the testimonials on Allergy Pathway's Twitter and Facebook pages) it is appropriate to conclude that Allergy Pathway accepted responsibility for the publications when it knew of them and decided not to remove them. Hence it became the publisher of the testimonials."

In responding to the judgment, ACCC chairman Graeme Samuel said: "Many corporations now use Facebook "Fan" pages and Twitter accounts to promote their businesses. This outcome confirms that any business that decides to leave public testimonials or other comments on their Facebook and Twitter pages will be held responsible if they are false, misleading or deceptive."

See ACCC Press Release

ACCC v. Allergy Pathway [2011] FCA 74


How should damages be assessed for privacy and cybersecurity breaches

Listen to this podcast where I discuss how damages should be assessed in privacy and cybersecurity lawsuits. The Lawyers Weekly Show host J...