Category: Freedom of Speech

  • Legal Threat from Martin Keatings

    A few years ago I wrote an article about how the Scottish Independence Party were/are dangerous idiots.

    At the time, the group appeared to clearly be linked to two individuals: Martin Keane and Deane Syme, and this was reflected in the article.

    Today, I received a legal threat over that article from Martin Keane, claiming that he and Deane Syme had nothing to do with what the SIP became, and that I must immediately remove the article or face legal action in the Sheriff Court. Here is the full text of his e-mail:

    Dear Stephen Blythe

    It has been brought to my attention that you have an article on your site at the following address (https://iamsteve.in/tag/martin-keatings/)

    The article itself deals with details of the Scottish Independence Party or SIP. I am writing to inform you that your article is factually incorrect and indeed rises to the level of libel. 

    I will go through each part of the article and specify to you the factual inaccuracies in the hope that you will remove the article immediately. If you do not, then I will be required to take the matter further which may include you being summonsed to appear in the Sheriff Court.

    You open the article “Tonight I became aware of the existence of the so-called ‘Scottish Independence Party’. No, not the Scottish National Party, but the Scottish Independence Party – aka Martin Keatings and Deane Syme.” – Considering the fact that your article was launched on 27/10/2014, this statement, straight off the bat is factually incorrect. Both Dean & I did consider setting up the SIP, however, based on the preponderance of evidence of the current political climate at that time in Scotland & also the fact that I did not have the time to continue forward, Dean and I both decided, 2 weeks prior to that date, that we were in fact not going ahead with it.

    The group on facebook was left open to the public and the existing members of that group, to do with it as they pleased. But Dean & I’s involvement went no further than thinking about it, trying to find out if there would be enough support & indeed then deciding not to go ahead. This all happened within the 2 weeks AFTER the referendum.

    Any posts after that time were down to third parties and not Dean or I. That makes the rest of your article totally false because any post, any statement, any action, any idea thereafter was nothing to do with Dean or I. The real kicker, of course, is that the situation is further confused by the fact a unionist tried to establish a party in the same name later on. You article, factually incorrect and indeed incorrectly naming us resulted in both of us receiving full blown abuse from the Yes community. Something I was unaware of until I got back from visiting my then-fiancee in Moscow.

    Now it seems your factually incorrect article is dragging us into another dispute. This has now reached the point where it needs to stop. I am asking you to kindly remove the article – or, you may if you wish, remove mine and deans name from said article and put a line at the bottom that says. MARTIN KEATINGS AND DEAN SYME ARE IN NO WAY INVOLVED WITH SIP.

    Its a simple case of, we had an idea, it didn’t go anywhere, someone else (the loons) decided to pick it up, you reported on it and linked us to it (which is incorrect) and then that idea didn’t work. Another loon picked it up again and the web community googled and guess what came up.

    Please remove the article, or our names (with an addendum)or i’m going to have no other choice but to make this legal stephen, and to be honest I don’t really want to do that to you bud.

    Martin

    I’m not really sure what this is meant to mean. Martin states that himself and Deane considered setting up a party under this name, created the Facebook page and associated discussions, but then decided not to go ahead with it… which means that referencing them in the article was perfectly legitimate.

    Given that the standard for defamation requires that a statement must be untrue and lower the defamed in the estimation of right thinking members of society, and that saying somebody is a member of a political party when they are not does not qualify, I would suggest that bringing an action for libel would not be the best use of time or effort.

    I have clarified the original article to highlight Martin’s concerns, and that should put an end to the matter.

  • Real Punishments Needed for DMCA Takedown Abuse

    Note: The opinions expressed within are mine, and mine alone – not necessarily endorsed by Automattic or WordPress.com.

    Last week Automattic released an update to our transparency report, detailing the number of takedown and information requests that were received between January and the end of June this year – as well as the number that had been acted upon, or rejected. There has been some good coverage of what’s included in the report by TorrentFreak, ARSTechnica, and TechDirt.

    One area that’s particularly interesting is that relating to the DMCA notification and takedown process, regarding instances of alleged copyright infringement. The full figures are available on the page itself, but here are the highlights:

    WordPress.com Transparency Report

    If you’re like me, it can be difficult to pull out something meaningful from a table of figures, at least at first glance. The important thing to note here is that 43% of the total notices received were rejected – either for being incomplete, or abusive. This figure rises to 67% if you remove sites that were ultimately suspended for a terms of service violation from the ‘Percentage of notices where some or all content was removed’ column.

    Incomplete notices can be anything from the complainant not including a signature; failing to specify the content that they are claiming copyright over; or not including the required statements ‘under penalty of perjury’. Abusive notices include those that target material which is not copyrightable (such as trademarks or allegedly defamatory content); where the complainant misrepresents their copyright; or attempts to prevent fair use of the material – protected by US copyright law.

    Many complainants simply want to get content removed from the web, irrespective of which route they have to take to get it. As a result, a variety of different tactics are deployed, particularly when a third party agent is engaged to carry out the task. For example, the wording of takedown demands may be fudged in order to give them the appearance of a valid DMCA takedown notification, whilst failing to substantively fulfil the statutory requirements. In other cases, claims regarding alleged copyright infringement are mingled together with threats concerning trademark infringement or defamation – obfuscating the invalidity of the DMCA takedown itself in the process. Web Sheriff in particular have been known to adopt this practice, with ‘kitchen sink’ takedown demands listing what seems like every law passed in the last 20 years incase one of them might apply in any given scenario. The Pirate Bay have infamously mocked Web Sheriff in the past for some of their tactics:

    Pirate Bay Web Sheriff Mockery

    It can be a difficult process to manually review and untangle exactly what a complaint relates to, and whether or not it is a valid DMCA takedown. Clarification e-mails often go ignore, something that is particularly true in cases where the notifications are being generated by bots. Replying to point out that a notification is incomplete, or that the material is actually hosted elsewhere in many cases is met by nothing except a deaf ear, and a duplicate takedown demand the following day.

    Whilst the DMCA’s safe harbor provisions are designed to provide protection for third party intermediaries as well as the rights of copyright holders, the phenomenon of automated takedown demands has resulted in a massively lopsided burden on those service providers who take their responsibilities seriously, and do not just acquiesce to every single takedown notification automatically.

    Complainants are able to submit grossly inaccurate DMCA takedowns on a massive scale, routinely through the use of automated systems that indiscriminately target particular keywords across the web – all without any real fear of legal consequence. The sheer volume notices generated means that the vast majority of service providers simply remove content immediately and automatically, without scrutinising them for their formal completeness or legal validity. The few that do choose to go through them manually in order to protect their users (like WordPress.com), end up facing a huge burden.

    Without stronger statutory consequences for those who abuse the DMCA’s notification and takedown system, the battle for freedom of expression online will be increasingly difficult. The majority of service providers will inevitably default to censorship in the first instance, as the number of notifications (and therefore the resources required to push back effectively) increases.

  • Blow Struck by WordPress.com Against Fraudulent DMCAs

    Blow Struck by WordPress.com Against Fraudulent DMCAs

    Abuse of the American online copyright takedown system (DMCA) is rife. People frequently submit fraudulent notifications to online service providers in order to censor views that they disagree with, curbing legitimate freedom of expression. Examples include those trying to stifle negative reviews about their businesses or products, preventing political satire, and even inappropriately targetting the normative use of a trademark.

    All too often, OSPs simply shrug their shoulders when confronted with these scenarios, and process the notices anyway in order to avoid losing their safe harbor protections. Even when alerted to what’s going on in specific circumstances, many choose a policy of non-intervention, rather than to defend their users.

    The result of one of two cases which were filed by Automattic in response to fraudulent takedown notifications submitted concerning material posted by WordPress.com was released a few days ago, Westlaw citation: 2014 WL 7894441. The judgement concerned a notice sent by a group called ‘Straight Pride UK’, who objected to the publication of an e-mail interview which a journalist Oliver Hotham had conducted. Under §512(f) of the DMCA, Automattic were awarded a total of just over $25,000 in damages – $960 of which was for Hotham’s time.

    The outcome was a ‘default judgement’, as the defendant’s (unsurprisingly) didn’t turn up to the hearing, despite being served properly through the standard international processes. It’s unlikely that either Automattic or Hotham will ever see any of the money, so it is largely a symbolic victory. However, it should not be dismissed too quickly, as the case highlights a number of important issues:

    • The DMCA is frequently abused, with few consequences for those who misrepresent their copyrights
    • Taking action against this abuse is expensive, and happens extremely infrequently
    • Enforcing damages against those from outside the US is difficult, and so there is a hole in the remedies available where those who abuse the system fall into this category
    • Even where organisations or individuals are resident in the US, major online service providers do nothing about the fraudulent notices they receive that could be actionable
    • In order for damages to be awarded, material must be removed as the result of a misrepresentation. There are no consequences for fraudulent notifications that are caught by diligent service providers first – at their own risk

    The DMCA is a blunt tool that has an incredible power to silence dissenting voices without recourse. The only way in which this is going to change is if service providers begin to stand up against the abuses, using the considerable resources as their disposal – both to further the conversations in this area, and also to take legal action where possible.

    Transparency: I am a Community Guardian for WordPress.com.

     

  • Hyperlinks, Copyright Infringement, and the DMCA

    Hyperlinks, Copyright Infringement, and the DMCA

    Hyperlinks are a fundamental part of the core fabric of the web. As the basic tool used to connect pieces of information together, it’s difficult to imagine how the Internet could function without them. 

    Despite its critical nature, the role of hyperlinks has attracted the attention of those seeking to prevent particular kinds of information from being shared. One of the prime examples relates to copyright, and efforts to disrupt the dissemination of materials without authorisation. As part of this, the delivery mechanism of the hyperlink – as well as the infringing act itself – has come under fire.

    Hyperlinks and Case Law

    There is not a sizeable wealth of case law available that directly relates to the question of whether a hyperlink can constitute copyright infringement. As a result, discussions concerning potential liability often draw upon analogies taken from older cases – sometimes with judgements over a century old – in order to apply established legal principles to the uncertainties thrown up by technological evolution.

    In the case of Hird v. Wood from 1984, the defendant was seated near to a sign on which defamatory messages were displayed. Despite not having created the sign, it was held that he incurred liability simply through the act of drawing attention to it. In the later case of Byrne v. DeanHird was referenced, the judge noting the following:

    If defamatory matter is left on the wall of [a] premises by a person who has the power to remove the defamatory matter from the wall he can be said to have published the defamatory matter to the persons who read it.

    Applied to our topic, it would appear that this principle would impose an obligation on the operators of websites (as well as their hosts) to remove hyperlinks that led to illegal material.

    The Supreme Court in Crookes v. Newton did not completely accept the above analogy. Instead, they found the argument put forward by the respondent to be more persuasive: a comparison between hyperlinks and footnotes. In other words, both are ‘content neutral’, communicating the existence of something, but not necessarily commenting on the content. This view is one also supported by Tim Berners-Lee, credited with the creation of the World Wide Web:

    The intention […] was that normal links should simply be references, with no implied meaning.

    However, the court also recognised that the Internet is ‘a potentially powerful vehicle’ for defamation, and that the context itself was important in establishing possible liability. In the words of the court:

    Individuals may attract liability for hyperlinking if the manner in which they have referred to content conveys defamatory meaning.

    Analogy is one instrument that can be used when considering the relationship between the use of hyperlinks and the law; powerful, albeit imprecise. The issues involved in real life situations are more complex than can be addressed by analogy alone, and courts have often taken differing approaches in making their determinations.

    One of the first cases to directly challenge the legality of the use of hyperlinks, and their potential to constitute an infringement of copyright concerned their use on the website of a Scottish newspaper named the ‘Shetland News’.

    The links in question were published on the Shetland News website. They took the form of headlines copied from the site of a rival paper: the ‘Shetland Times’. By visiting the Shetland News website and clicking on these links, visitors were taken to the corresponding articles on the Shetland Times website. Confused yet? The way things were set up meant it was possible to completely avoid having to visit the Shetland Times’ homepage, and therefore missing out on its advertising. As a result, the Shetland News website was receiving ad-based income for providing direct links to articles that they themselves had not authored. 

    Understandably, the Shetland Times weren’t too pleased about this, and succeeded in having the use of the links halted through the use of an interim interdict. The reasoning for the decision was that the links came in the form of headlines that had been copied verbatim from the other site, and so there was potential copyright infringement. Disappointingly from an academic point of view, the case was settled out of court, with no final judgement made on the actual liability arising from the use of the links.

    One of the first significant cases in the US regarding the status of hyperlinks was that of Kelly v. Arriba Soft Corp. This concerned the display of thumbnail images from a professional photographer’s website in search results. The images were available both as resized thumbnails, and full sized previews, which is akin to the functionality provided by Google Images. Arriba was sued for copyright infringement, and the appeal judgement from the Ninth Circuit Court in San Francisco found that the thumbnails were protected under the doctrine of fair use. However, there was liability incurred for the displaying of the images in a new display window – a practice known as ‘in-line linking’. After an amicus brief filed by the EFF, the judgement was revised; the concerns about the in-line linking removed, with the fair use affirmation standing. 

    In the case of Intellectual Reserve, Inc. v. Utah Lighthouse Ministry, Inc., the court found that hyperlinks pointing towards illegally distributed material could in of themselves be considered to be contributory copyright infringement. In this particular situation, the facts were complicated because the owner of the website in question had originally stored copies of the protected content on their own servers, before replacing them with hyperlinks to copies stored elsewhere. It was the context of these actions that was important – echoing the ratio decidendi in Hird.

    One of the more commonly cited cases in this area is the infamous Grokster case, in which the Supreme Court introduced a new potential for liability: that of inducement. It was held that where technology is created for the intended or actual purpose of encouraging its users to breach copyright, then the creators themselves could be held liable for contributory copyright infringement. Ultimately, Grokster was shut down. Despite the concern by service providers over the precedent of this case, the facts were very particular to this situation, with the platform actively fostering the ‘blatant and overwhelming’ infringing activity of their users. It is extremely unlikely that the same definition would be applied to the majority of contemporary online intermediaries.

    Hyperlinks, the DMCA, and Contributory Infringement

    Online service providers often receive DMCA takedown notifications that target hyperlinks leading to allegedly infringing material, rather than material that resides on their servers. They are faced with an interesting quandary as a result: whether or not to remove the link.

    On the one hand, hyperlinks generally do not constitute copyright infringement. However, it is the context that is the determining factor when considering potential for liability. A link created by a user to illegal material may well be infringing, but where does this leave the service provider?

    Service providers are afforded safe harbor immunity from the infringing actions of their users, provided they ‘remove or disable access to’ material upon receipt of a valid DMCA takedown notification. However, it is unclear how this would apply in the case of hyperlinks. In our example, the infringing material itself is located on servers out-with their control, but there is still potentially infringing activity taking place on their platform. Would a host be liable for a failure to remove a hyperlink to material, where that hyperlink was found to be an infringing act, based on the context?

    We can take some insight into how the decisions of future courts may fall in this scenario by considering the ‘server test’ discussed in the Perfect 10 cases. Here, the facts concerned the display of websites in Google’s Image search that were infringing upon the copyright interests of the plaintiff. It was found that Google was not liable for direct infringement on the basis that the material at issue did not reside on their servers, and was served up from another host through their use of framing, or ‘in-line linking’. With regards to contributory infringement specifically, the court held that there was no liability, as the infringing activity itself would still exist irrespective of whether or not Google Images existed. In other words, they were not found to be encouraging the copyright infringement.

    In Flava, the defendants were operators of a ‘social bookmarking’ service called myVidster that allowed users to share videos from different locations around the web, which were then embedded on their platform, served up from the original locations. They were sued for contributory copyright infringement, based on the actions of users that were sharing clips that had been uploaded without authorisation.

    The service provider had already received a number of takedown notifications regarding the material, and it was argued that they had not taken enough action as required to qualify for safe harbor protections. However, that is not the be all and end all. In the words of the court: ‘a non-infringer doesn’t need a safe harbor.’ The parties who uploaded the videos in the first place were the ones whose activity was infringing, and the question is whether myVidster had encouraged their infringing activity to an extent that constituted contributory infringement. The court did not find this to be the case, holding that myVidster was neither a direct or contributory infringer. In other words, they were too far removed from the infringing activity, 

    My View

    Irrespective of the potential for individuals to incur liability based on the context of hyperlinks which they create, the application of the DMCA should not extend to their removal.

    Part of the criticism of the DMCA is that there is a substantial burden placed on copyright holders to track down and report instances of infringement across the web. Much like the mythological Hydra, as one falls, more spring up to take its place. Slaying the beast requires attacking the root of the problem; treating hyperlinks as valid subjects of takedown notifications is to mis-understand the task, and only serves in the creation of extra conceptual heads to pursue.

    Rather than target hyperlinks, the focus of enforcement efforts should be on the actual source of the infringing material: the host. Take out the location pointed to by hyperlinks, and they are instantly rendered obsolete. This is not only a far more effective approach in tacking infringing activity, but one that also avoids creating extra and unnecessary work. Financially, this means less is paid to third party agents such as DMCA.com, whose revenue is based on successful takedown notifications.

    The DMCA is already a blunt, and powerful tool. Abuse of the system is rife, and often deployed for the purposes of censoring legitimate expression, rather than to curb copyright infringement. To extend its remit to include the removal of hyperlinks is a dangerous step, that fundamentally alters our relationship with a core structural element of the web, and risks a (further) chilling effect on freedom of speech.

    Despite recent case law seeming to support this principle, the judgements have been extremely dependent on the circumstances involved, and there has been no definitive authorities. As a result, it is up to online service providers to shape the approach to the issue, rejecting DMCA notification takedowns that concern hyperlinks. Policy decisions such as this create the normative frameworks that have the power to help ensure or hinder a free and open web, and it’s critical that tech companies lead the charge, rather than taking a minimum risk stance.

  • Why I’ve Switched to WordPress.com

    Why I’ve Switched to WordPress.com

    The eagle-eyed amongst you may have noticed that not only have I switched the blog’s theme in the past few days, but I’ve also shifted the hosting completely over from a self-hosted WordPress.org instance, to one on the servers of WordPress.com. (Confused? This article will explain the difference.)

    For years I’ve always run sites using WordPress software that I’ve configured myself, rather than those on WordPress.com, based on the following reasons:

    • Hacker Mentality – Not wanting to let go of complete control of my site, and the ability to do with it what I please (like hosting weird web apps and playing about with plugins)
    • Cost – I was always under the impression it would be relatively expensive to keep all of my stuff on WordPress.com’s servers, as generous pals have hosted my sites previously
    • Transition Pain – Moving from an already established and customised site to a different platform seemed like a faff, with inevitable SEO problems/broken links
    • Features and Customisation – Not believing that I’d be able to get my blog to look/feel the way I wanted it to within the WordPress.com boundaries, and that I would miss features (like permalink restructuring)

    The more I thought about it, the more I realised that I didn’t actually need to run a self-hosted site for http://iamsteve.in. The design of the site was pretty straightforward, there was no real complicated customisations involved, and the cost of shifting to WordPress.com wasn’t what I thought it might work out at; definitely not for a site that isn’t hosting large numbers of images anyway.

    In fact, the benefits of being hosted on WordPress.com seemed more and more appealing:

    • A dedicated, and passionate support team that are on hand to help out with any issues (Working alongside them, this was an even bigger boon for me personally)
    • A streamlined interface that I use everyday (for both work and pleasure)
    • No more having to login to separate admin panels all the time
    • A site that is integrated into the highly active WordPress.com community – and so more engagement with other users on the posts
    • No more worrying about rogue plugins crashing or needing to be re-configured after an update breaks something
    • The ability to take massive spikes of bandwidth, as I’m hosted on WordPress.com’s massive network

    and one of the most important things of all:

    • The knowledge that my host won’t be intimidated by any legal pressures that come from any of the critical posts I write. (See here for more)

    I’m incredibly proud to be part of a team that fights back against those who attempt to censor bits of the Internet that they don’t like on a daily basis, and it makes sense to bring my own writing into that fold. I know I have good people on my side should anything hairy come up.

    Really the only thing that I was left swithering over was the pain of moving across. I thought I would give it a bash, and two hours later, the entire site is completely migrated over (multiple domain names and all). The difficulties I thought I’d run into didn’t even crop up as issues at all. All of my custom permalinks are smartly resolved by the WordPress software to their new locations (which I am both almost in disbelief and awe at).

    I’m pleased. Not a bad experiment after all.

  • ‘Family Friendly’ UK Government Policies. What About Immigration?

    Ever seeking to be seen as the ‘family man’, David Cameron has stated that in future, all government policies should pass a ‘family friendly’ test before becoming law. (#)

    It should be pretty clear to anyone with a critical mind that this is nothing more than meaningless spin and rhetoric. Cameron’s government are focussed on what benefits the privileged, not the underdog, but they have to appeal to a moral position in order to condition skeptics into voting for them. However, there’s one specific example that immediately comes to mind that should illustrate the duplicity involved with this proclamation: that of immigration.

    The usual bullshit position on immigration in the UK tends to be: “we’re here and it’s our right to be here – nobody else should be allowed. Foreigners should just go home.” – worded more or less diplomatically depending on who is involved. Immigration? Pah! Why should those immigrants be considered anyway?

    Interestingly enough, experience has shown that this dogma transforms (as do many others) when the issue comes closer to home. It’s easy to dismiss immigrants of a different colour or nationality in the abstract, but not so much when one of your family members is separated from a loved one because of harsh and unpredictable immigration regulations.

    The fact is that immigration policy in the UK is racist, and purposively both complex and contradictory in order to make the application process as difficult as possible. There are no elements of fairness or justice in how people are dealt with, and what results is a maddeningly frustrating and expensive undertaking for anybody who dares to fall in love with somebody from another country. When the system invariably break down, people are forced to appeal to the safeguard of the European Convention of Human Rights, which is then handily used as a scapegoat for undermining national sovereignty. Few point out the responsibility of the UK government to ensure that the system is fit for purpose in the first place.

    There are endless amounts that have already been written about my own experience with the UK immigration process alone, but never published. It’s something I constantly swither over making public, partly through fear of any future reprisal. After all, we still have a number of years to go before we are completely out of the woods, and at any point our hard-fought battles could be revoked. Why is so little said about this stuff in detail by those who go through it? Because we are terrified of the possible consequences that might happen. People should know about what injustices happen in the system, and freedom of speech should guarantee the ability for that to happen, but who wants to risk it when their application may be denied?

    For those of us who are on the receiving end of such policies, we know how awful it is. We know that immigration is a disgusting mess; one that has no concern for families, or for keeping them together. We know that kids get used solely as an excuse to raise the barrier for entry to the UK, not treated as human beings. We know that what really matters here is ethnicity, not family values. We know that it’s a specific kind of morality that is in mind here: that of the white, mother and father, British kind. We know that all this is true, and have resigned ourselves to being subjected to that, often silently… but to then turn around and talk about the importance of ‘family friendly’ policies is just flat out insulting.

    Don’t believe a word of this pish.

     

  • The ‘Right to be Forgotten’ is not a Bad Thing

    There has been much said in the past week about the ‘right to be forgotten’ principle being developed in European Law, after the decision by the European Court of Justice in the case of Google Spain v AEPD and Mario Costeja González.

     

    new-google-logo-knockoff

    Why this decision isn’t a good thing

    The decision of the ECJ has been subject to swathes of criticism for a variety of reasons. However, one of the biggest issues to raise its head is the ideological discussion of Data Protection v. Freedom of Expression.

    Originally, data protection was intended to help protect individuals from organisations collecting and storing information on them erroneously. In general, data protection is a good thing. Infact, it’s bloody awesome. It means that when any company or other body collects ‘personal data’ on you, recording it in a filing system, you have the right not only to see it, but to have inaccurate data modified, as well as to prevent the processing of it for marketing purposes.* Sounds good, right? Oh, and this also applies to organised filing systems that are stored on paper, not just electronically.

    In reaching its decision in the Google Spain case, the ECJ has applied the established approach to data protection, whilst at the same time injecting the relatively new principle of the ‘right to be forgotten’. The problem with this is that the circumstances are fundamentally different to those in which the protections were introduced to be applicable to.

    In the Google Spain case, the information was held to be legally published on the site of the newspaper in question, and so is not required to be removed. However, because Google collected, stored, and processed the links to the information, it was then considered a ‘data collector’ under the data protection definitions, and so obliged to consider, and give effect to the removal request.

    This is DUMB.

    This is not the same as a situation where an organisation is keeping detailed personal records on an individual (such as their medical details, telephone number, or address, for example), that would not otherwise necessarily be found elsewhere. In this situation, the information is already in the public domain, published lawfully. The fact that Google collects the locations of this data, stores it, and then offers up the hyperlinks in search results should not bring it under the gambit of The Directive in its current form. I won’t even begin to think too much about the baffling way in which this seems to fly in the face of the general approach to hyperlinking that was laid out in the Svensson case, earlier this year.

    In any event, these removals only apply to the EU – not to Google sites (or those of any other ‘search engine operator’) that lie outside. Clearly the ECJ must not have heard of a proxy before. At the root of it, this is bad law because in the context of a global Internet, it is meaningless.

    Why the right to be forgotten isn’t a bad thing

    When the right to be forgotten was first being discussed, it was in relation to something far more sensible – something which had very little to do with freedom of expression at all. It was to do with the right of users to have online service providers remove the personal information held on them when they chose to delete their account. Ever tried to delete your Facebook account completely? It’s not exactly a walk in the park. It wasn’t about trying to hide past transgressions that have already received media attention, and it wasn’t about curtailing the basic architecture of the web – it was about being able to tell Zuckerberg that when you want to leave, they should honour that.

    The problem with the ECJ’s decision is the way in which they have applied the principles of data protection, rather than data protection itself. Whether or not the Court wilfully misunderstood, in order to crowbar the right to be forgotten into the judgement in this case is one thing, but that doesn’t mean the entire principle should be dismissed.

    Sadly, a lot of the commentary has focussed on the specific facts of this case, and applied them broadly to support a wider theoretical gap between the supposed American principle of freedom of expression, and the European importance on privacy. Whilst that is a whole separate discussion, I do not believe that this should be reduced to some sort of absolute Transatlantic ideological difference. Instead, it should be seen for what it is: a bad application of principles that are fundamentally designed to protect individuals.

    The right to be forgotten is valuable, but it should never have come close to impinging on the freedom to ‘receive and impart information‘ on that which is already lawfully published.

    * This interpretation is based on the UK Data Protection Act of 1998, which gave effect to Directive 95/46/EC – the EU Data Protection Directive.

    More reading:

    You can read the full text of the original application, the opinion, and the judgement of the ECJ over on Curia.

    The relevant (English) press release from the ECJ on the Google decision is here.

    Here is a helpful description of how Google’s new form dealing with right to be forgotten requests will operate.

    Stanford Law Review article on the Right to be Forgotten here.

    Article on the decision and censorship from Index here.

    ‘What you need to know about the ‘Right to be Forgotten’ – here.

  • TalkTalk Blocks Access to WordPress.com

    This past month, TalkTalk repeated past form and unilaterally blocked access to millions of WordPress.com blogs.

    It’s not clear exactly how they did this, or whether it was restricted to specific IP ranges, or whether or not this was part of any particular policy.

    Don’t think that ‘porn’ filtering will affect you? It already is.

    Read more from the Open Rights Group here.

  • Automattic/WordPress.com fight back against Censorship

    WordPress LogoAutomattic – the company behind WordPress.com, have taken a decisive step in the fight against bogus DMCA claims.

    Under the Digital Millennium Copyright Act, people can submit a takedown notice to web service providers where their intellectual property is being used without permission. This is the legislative attempt to protect hosts like Google, WordPress, Tumblr, etc from being held responsible for the content that their users post – provided that they swiftly restrict access.

    However, whilst this system is designed to give a balance between protection and enforcement, the reality is that many times it is abused by those who wish to silence critics, or to censor views with which they disagree. The Church of Scientology infamously issued thousands of DMCA takedown notices to stop the spread of anti-Scientology views on Youtube, for example. This tactic is highly effective, as the content is almost always restricted (at its peak moment of attention), and the process to challenge the notices (a ‘counter notice’) isn’t something that creators are, or arguably should be, familiar with. In effect, it becomes a virtual game of ping-pong, with the burden of proof shifting to the ‘author’ of the content to prove that they actually have the rights to publish. Sites themselves can take action, but with the sheer volume of notices that they receive, it is often impractical, and rarely a route that businesses want to go down.

    I’m both pleased and proud to see that WordPress are fighting back against two such bogus DMCA claims, as announced in this latest blog post, where you can find all the details of the two cases in question.

    For the full text of the original post from Oliver Hotham – one of those that fell victim to the misrepresentative DMCA, continue reading below, where it is republished with permission.

    (more…)

  • Twitter and S.112 of the Equality Act 2010

    Yesterday it was posted in the Drum that after receiving a number of threats including rape over Twitter, that the subject of these messages – Caroline Criado-Perez – has been approached by a lawyer with respect to a possible civil law action against the service. Under Section 112 of the Equality Act 2010, no person must ‘knowingly help’ another to do anything which contravenes the conditions laid out in the Act. Without commenting directly on the facts or merits of this case, if Twitter are to be held liable for the actions of its users in such a manner, the ramifications would extend far beyond the issues at hand.

    There are few that would argue that the social network knowingly and willingly designed their systems specifically to allow people to abuse others – it wouldn’t make good business sense for a start. Users don’t tend to stick around on services where they can’t filter out those that they don’t want to interact with, which is exactly why there is a ‘block’ function in place. Whether it is practical to be able to block thousands of different sources quickly and effectively is quite a different question, and one which is not new to the web – as any webmaster worth their salt will know. Block an offending IP address, and just as quickly another one will pop up: the ol’ virtual whack-a-mole.

    Twitter may have ‘knowingly’ created a system where people are free to disseminate information en masse, quickly, and with any content as they so desire, but to hold them to account for ‘knowingly helping’ people to breach Equality legislation seems farcical (not to mention out-with its intended purpose). If providers are to be held responsible for that posted by its users to such an extent, then we may as well proceed to shutdown all similar platforms, as any that allow people a level of freedom of expression, as they will always be mis-used. To apply the law in this way would have a chilling effect not just on the development of the web, but on free speech itself.