UK Web Focus (Brian Kelly)

Innovation and best practices for the Web

  • Email Subscription (Feedburner)

  • Twitter

    Posts on this blog cover ideas often discussed on Twitter. Feel free to follow @briankelly.

    Brian Kelly on Twitter Counter

  • Syndicate This Page

    RSS Feed for this page


    Creative Commons License
    This work is licensed under a Creative Commons Attribution 2.0 UK: England & Wales License. As described in a blog post this licence applies to textual content published by the author and (unless stated otherwise) guest bloggers. Also note that on 24 October 2011 the licence was changed from CC-BY-SA to CC-BY. Comments posted on this blog will also be deemed to have been published with this licence. Please note though, that images and other resources embedded in the blog may not be covered by this licence.

    Contact Details

    Brian's email address is You can also follow him on Twitter using the ID briankelly. Also note that the @ukwebfocus Twitter ID provides automated alerts of new blog posts.

  • Contact Details

    My LinkedIn profile provides details of my professional activities.

    View Brian Kelly's profile on LinkedIn

    Also see my profile.

  • Top Posts & Pages

  • Privacy


    This blog is hosted by which uses Google Analytics (which makes use of 'cookie' technologies) to provide the blog owner with information on usage of this blog.

    Other Privacy Issues

    If you wish to make a comment on this blog you must provide an email address. This is required in order to minimise comment spamming. The email address will not be made public.

Twitter Export Functionality Returns to Twapper Keeper

Posted by Brian Kelly on 24 Mar 2011

On 17 March Twitter updated the terms of service for use of their APIs:

You may export or extract non-programmatic, GUI-driven Twitter Content as a PDF or spreadsheet by using “save as” or similar functionality

In light of these changes, as described on the Twapper Keeper blog, John O’Brien, the Twapper Keeper developer has “decided to bring the “Save as Excel” link back online when viewing an archive. This will allow you to get the currently viewed content into an Excel file for review.

This will be good news for those who were not able to take action following last week’s post that there were only “A Few Days Left to Download a Structured Archive of Tweets“.

The changes in Twitter policies on use of its APIs will have been a result of a backlash following Twitter’s announcement that it was more rigorously enforcing its terms and conditions which appeared to be inhibiting development of third party Twitter applications such as Twapper Keeper.

It should be noted, however, that the terms of service state that:

You will not attempt or encourage others to: sell, rent, lease, sublicense, redistribute, or syndicate access to the Twitter API or Twitter Content to any third party without prior written approval from Twitter.

and go on to add:

Exporting Twitter Content to a datastore as a service or other cloud based service, however, is not permitted.

The first condition is clearly intended to ensure that Twitter is in a position to commercially exploit its content and services (note back in February there were stories being published which speculated that twitter could be sold for up to $10 Bn). It should be noted that the second condition would appear to prohibit Twitter content from being hosted on cloud services for use by others, even if there is no financial gain. Twitter, it seems, is turning itself into a silo, with only limited capabilities for data export and reuse. Perhaps it is seeking to emulate Facebook’s approaches in this respect.

Is this an unacceptable approach from a private company which, like Facebook, seems to be seeking to maximise financial gain from content provided by its users? Should we not be looking to move to an alternative microblogging environment, such as, which Wikipedia states: “While offering functionality similar to Twitter, StatusNet seeks to provide the potential for open, inter-service and distributed communications between microblogging communities. Enterprises and individuals can install and control their own services and data.

I think we ought to be very careful before making such moves. In part this is because of the importance of one’s social network to effective use of such social web services and also in light of the importance of the variety of tools and services which have been developed around Twitter and its ease of use on a variety of devices and environments – including watching TV programmes such as Question Time, for which use of Twitter as a back channel is now well established.

But in addition we need to consider whether, in light of the current political and economic climes, we should be over critical of organisations which make money out of services we use for free. We should also recognise that services developed in UK Higher Education may also prohibit commercial exploitation of content.  For example the policies for the University of Bath’s Opus institutional repository states that:

The metadata must not be re-used in any medium for commercial purposes without formal permission.

This policy was created using the OpenDOAR policy tool. My understanding is that the policy described above is intended to prevent others from commercially exploiting repository metadata. Is this fundamentally different from Twitter’s statement that:

You will not attempt or encourage others to: sell, rent, lease, sublicense, redistribute, or syndicate access to the Twitter API or Twitter Content to any third party without prior written approval from Twitter.

I think it is unfortunate that Twitter have chosen to make it more difficult for others to make use of twitter content, whether for commercial gain or not. But if a broad aim of higher education is to help stimulate the economy, shouldn’t we be permitted (perhaps, indeed, encouraging) others to reuse our content – and if this generates income to fund such initiatives, should this be a problem?

2 Responses to “Twitter Export Functionality Returns to Twapper Keeper”

  1. […] Go to Source This entry was posted in new. Bookmark the permalink. ← Russia: Life of Migrant Workers in Pictures […]

  2. Chris Rusbridge said

    Hmmm. “The metadata must not be re-used in any medium for commercial purposes without formal permission.” What does this mean? I am, for instance, no longer in academia, and occasionally take part in paid activities which would qualify by most people’s definitions as “commercial”. I don’t buy or sell stuff, but people sometimes pay me to do things. Can I not use the metadata in Opus? If not, why ever not?

Leave a Reply

Please log in using one of these methods to post your comment: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: