Posterous theme by Cory Watilo

CoveritLive gets hacked

So this morning brought a "We've been hacked!" email from CoveritLive with the assurance " We regret any inconvenience that this password change process may cause you". Frankly, an enforced password change is a small price to pay... hopefully that's the full extent of it. 
 
From: CoveritLive 
Date: 14 January 2012 01:22
Subject: Important CoveritLive Password Notification
 
CoveritLive recently discovered that certain proprietary data files were accessed without authorization starting on or about January 7, 2012. We have not yet determined if, or to what extent, CoveritLive account information (i.e., user names, email addresses and/or passwords) was accessed. We do know, however, that no financial account information has been compromised.

Our investigation is ongoing, and, as a precautionary measure, we will implement required password resets for all active CoveritLive accounts. We plan for this process to begin Saturday January 14, 2012 at 12 AM EDT (5 AM GMT). The next time you log in after the process has begun, you will be asked to change your password before you will be allowed into your account. NOTE: we do not anticipate that you will experience a disruption in your event if you are using CoveritLive while the change is invoked.
Your password and all account passwords are encrypted as a standard CoveritLive information security practice, and we have no evidence that an unauthorized individual has actually retrieved, or is using such data. However, out of an abundance of caution we recommend that if you registered for CoveritLive using an email address and password combination that you use for other online accounts, you should immediately create unique passwords or new login credentials for those other sites and accounts.
We take this matter very seriously and will continue to work to ensure that all appropriate measures are taken to protect your personal information from unauthorized access. We also would like to take this moment to remind you of a couple of tips that should always be followed:

  • Do not open emails from senders you do not know. Be especially cautious of "phishing" emails, where the sender tries to trick the recipient into disclosing confidential or personal information.
  • Do not share personal or sensitive information via email. Legitimate companies will not attempt to collect personal information outside of a secure website.
We regret any inconvenience that this password change process may cause you. Please do not hesitate to contact us at passwords@coveritlive.com if you have any questions.
Sincerely,
CoveritLive Team


Google Wave closing down

Goodbye Google Wave. It seems so long ago that we were all selling our grannies for invites...

***********************************************************

From: Google Wave <wave-noreply@google.com>
Subject: Google Wave Sunsetting in 2012
To: alisongow

Dear Wavers,

More than a year ago, we announced that Google Wave would no longer be developed as a separate product. At the time, we committed to maintaining the site at least through to the end of 2010. Today, we are sharing the specific dates for ending this maintenance period and shutting down Wave. As of January 31, 2012, all waves will be read-only, and the Wave service will be turned off on April 30, 2012. You will be able to continue exporting individual waves using the existing PDF export feature until the Google Wave service is turned off. We encourage you to export any important data before April 30, 2012.

If you would like to continue using Wave, there are a number of open source projects, including Apache Wave. There is also an open source project called Walkaround that includes an experimental feature that lets you import all your Waves from Google. This feature will also work until the Wave service is turned off on April 30, 2012.

For more details, please see our help center.

Yours sincerely,

The Wave Team

© 2011 Google Inc. 1600 Amphitheatre Parkway, Mountain View, CA 94043
You have received this mandatory email service announcement to update you about important changes to your Google Wave account.


Future of Journalism conf: notes from plenary speaker Emily Bell #foj11

I spent a couple of hours this morning at the Future of Journalism
conference in Cardiff, where the plenary speaker was Emily Bell,
director of the Tow Center for Digital Journalism at Columbia's
Graduate School of Journalism and former director of digital content
for the Guardian.
Her talk was titled The (Many) Future(s) of Journalism, and my notes
are below, if you missed the live stream of the event...

1. The 'stop talking start doing' complaint about conferences

"I'm glad to be here talking about the future of journalism because in
1987 the only discussion we had about. Future of journalism was to do
with printing strikes, it was nothing to do with the newsroom."
She said that at one stage academia existed to put people into jobs
that were heavily templated.
It was accepted that the best way to do journalism was the way it had
always been done, and answers were not easy: "There are no silver
bullets because journalism is less defined by the business that
supports it. We are left with a shapeshifting proposition that dodges
definition."
The whole 'citizen journalist' and pro/am debate is a cul de sac:
"Arguing over who may or may not be a journalist is futile. I [cannot
be arrested] for pretending to be a journalist.
"We can stretch the metaphor and say in the future everyone will be a
journalist for 15 mins. The pro and the am are increasingly
indistinguishable able so go pick one future is hard because it has a
future as a process, business and profession."

2. Future of 'good' journalism and future of 'bad' journalism

The argument of five years ago was that the future would be good for
bad journalism because there would be fewer journalists doing good
journalism.
It would open the opportunity of journalism to anyone who wanted to
pretend to be a journalist and 'peddle lies'.
"It would strap us to a hamster wheel of live reporting, sacrificing
analysis in-depth complex journalism for a torrent of live stream
information. It would be dominated by technologists. We saw this as a
bad thing."
But actually, she continued, these elements favour good journalism and
will help render bad journalism all but irrelevant.

The idea that journalism would be picked apart by others - such as
search engines, aggregators etc - is actually a benefit to journalism.
It allows journalism to learn from other fields and bring it back to
improve itself. It has been in defence mode for a long time and is
starting to break out of it's boundaries.
The future of journalism lies beyond its borders.
It is about having to understand tech and platforms that deliver it.
Columbia University has journalism courses that run in tandem
alongside computer sciences.
"These students are asking if there are better ways to do things, and
to innovate how to deliver journalism well. You see lots and lots of
solutions coming out of technology minded people in newsrooms and that
is no longer the preserve of technology companies."
She outlined using Storify to liveblog an event, and how exciting they
found it. Soundcloud Document Cloud, Twitter etc are the students'
new toolkit.

The inclusion of non journalists has been beneficial, contrary to what
may have been though. Eg wikileaks cables collaboration with
mainstream media, also the Japan earthquake saw a pop up blog set up
and run by students who explained what the data and metrics from the
quake monitoring site meant, and it was part of the system of
journalism aggregated and pointed to by other news organisations,
Core skills will be how to make the best of collaboration. Eg NYT
linking up with a local radio station.
Guardian coverage of the England riots was a social activity - relying
on crowdsourcing. There is almost no evidence to show whether David
Camereon was right to say social media was behind the riots. The
Guardian collected and analysed tweets and is now using its' Twitter
analysis to work with Rowntree Foundation and LSE to see if that is
the case.

3. "Instant journalism is bad journalism"

The most galvanising thing to happen to journalism is social web and
mobile devices.
Journalists felt challenged by this. [quick observation from me: I
don't think we all did!]
She used Andy Carvin as an example of working beyond platforms. Also
the Watershed Post, set up by two people in the Catskills who felt
they had toolittle media representation.
The livestream of journalism, the involvement people who are not journalists
In the traditional sense and the technological tools we use benefit
good journalism.

4. "The lack of money is good for journalism"... "Or it's the reality
we live in."

There is not going to be the same level of revenue coming in to
digital journalism as there was in legacy media and we will be working
in reduced means.
Journalism as a working business model is fetishised. The most
profitable journalism can be the worst journalism - so bad it closes a
newspaper. It shows the problem when the primary focus becomes
profit. Now it is sustainability and profit is not the defining factor
of why journalist go into the business.
She used the Journal Register as an example of how sustainability and
a rethink has caused such a dramatic change. "We don't know how this
will work or if it will, but we know that if we don't try it how the
story ends".
Propublica model has Pulitzer prizes, is one of the most advanced in
data use in the world.
"Data, mobile, cms, all of these and the benefits they bring to good
journalism could be discussed at length. There is a huge amount of
this that is not properly understood."

5. There is no clear answer to what journalism will look like in five
years time but there are clues

The future is there to be defined. We have a collective capacity to
make this work but it can only be done by looking out and upwards.
Digital costs a lot less to do. It doesn't have the legacy costs. The
Guardian has money to spend because it gets money from Autotrader, a
purely digital product. If you understand the cost of what you are
doing it helps - a lot of good journalism comes out of things that
don't make money.

Groupon buys Whrrl... Whrrl closes

Voucher giant Groupon has bought Pelago, the company behind geo social mobile app Whrrl, with the ensuing result that Whrrl is shutting "for now". 
Or, as they put it: 

"The opportunity to take the collective brain power and technology of our two companies and point them at a phenomenon already at huge scale is virtually impossible to refuse.

"What does this mean for Whrrl? We've made the decision to close the curtain on Whrrl for now. Think of it as the end of the first act of a long and complex play. You would be right to expect that the ideas underpinning Whrrl and many of the inventions contained within may reemerge under the Groupon banner."

I signed up but never used it much; turns out none of the geo apps clicked with me like Gowalla (sorry Foursquare, Rally Up, Facebook Places et al).
Anyway, goodbye Whrrl. 

More ripples in the Twitter API clampdown

Interesting email from 140kit team, not least because I didn't realise TwapperKeeper - where you can archive your own and, export and download tweets - was affected.
However, there are still good people out there; 140kit has come up with a workaround that satisfies new Twitter guidelines, and helps non-coders access once-freely available data:
"...we plan on re-structuring this system to a point where it is trivial to download a scratch copy of our service, test one’s own analytics locally, then send the analytical process to the site for vetting, which would be a simple process. If the language you work with isn’t included in our system yet, we’ll add it. If you don’t know how to code, tell us the general algorithm and we’ll code it if we have the time and resources."

The email below explains it in more detail but I was particularly struck by the last few pars on why 140kit was established:

"[we] realized that if we generalized the process of data collection and analysis, we could open the door to doing very meaningful comparative analysis of datasets, which in turn could help us actually figure out A. If Twitter matters, B. If it does, what its impacts are, and C. What this implies for the internet and social networks as a whole. We have never been in this for money - we have never looked for funding, this has never been our job, and our systems were given to us by the Web Ecology Project and are hosted at Harvard’s Berkman Center for Internet and Society. We have one machine we pay for, which in May will be coming out of our own pockets (the machine was purchased for a year as part of a class Ian and I slapped together at Bennington College). We are solely interested in the data and its implications, and this is a labor of love. We are more than happy to continue on this project"
 
Cool people.
 
 
---------- Forwarded message ----------
From: 140Kit Team 
Date: Fri, Mar 4, 2011 at 12:29 AM
Subject: 140kit: Regarding Twitter's API Change

Hello,

You’re receiving this e-mail because you signed up for our service, 140kit, sometime in the last 8 months. We are writing you to inform you about the current state of data exports, as well as our solution to the problem currently being presented. 

A few weeks ago, Twitter caused some news by publicly stating that no more whitelisted IPs would be granted for any purposes - this essentially ends any REST based data collection for new researchers (doing collections of tweets based on User names, for instance, requires this access). Within a few days, they also sent a letter to TwapperKeeper, another major data collector, which compelled their leadership to turn off all export services as of March 20th. The same has basically happened for all other collectors, including ours. In short, the time where a researcher could export a full, unfiltered, unadulterated dataset, is completely over. 

The particular section of the TOS that is violated by export clearly states (Section I.4.a., at http://bit.ly/9LD7XQ): 

I. Access to Twitter Content

4. You will not attempt or encourage others to:

a. sell, rent, lease, sublicense, redistribute, or syndicate the Twitter API or Twitter Content to any   third party for such party to develop additional products or services without prior written approval from Twitter;

Where Twitter Content is defined as: All use of the Twitter API and content, documentation, code, and related materials made available to you on or through Twitter

Meaning that 140kit, as a service, cannot provide the datasets wholesale, where they use products/services basically to mean anything, even academic reports. For many of our users, this effectively shuts them out of the ability to research the platform. If one doesn’t know how to code, its very difficult to do this alone - this problem is compounded when you don’t have the access levels needed to research a given subject. We at 140kit have more than enough access, however, and still retain the right to keep our data, so we came up with a novel solution, which Twitter has agreed to. 

On our site, we have a library of analytical process, which in turn have their own online viewers, and a few of which contain their own exports. All of our services, from CSV export to gender analysis, runs via a modular library of analytics which have their own administrative structure. We built this system with a view that someday, we would open up our system for researchers to build out their own analytics, add them to our site, and all researchers would have access to these processes as well. We wrote our project in Ruby, but want to make this plugin system work with any language, which should actually be quite easy. 

Over the next few months, then, we plan on re-structuring this system to a point where it is trivial to download a scratch copy of our service, test one’s own analytics locally, then send the analytical process to the site for vetting, which would be a simple process. If the language you work with isn’t included in our system yet, we’ll add it. If you don’t know how to code, tell us the general algorithm and we’ll code it if we have the time and resources. 

In this way, as the library increases, we will be able to answer more of the most core questions researchers are interested in, and at a certain threshold, all the important questions will have their analysis on the site already. Since we can keep our data, we would be able to re-calculate analysis on any previous dataset. In short, we can’t give you the exports of data, but we can answer any question you want answered. It’s not the best solution, but it will save many projects from the grief of doing this alone.

This project was started in October 2009, between two people, myself (Devin Gaffney)and Ian Pearce. We were profoundly interested in analysis I was doing about the Iran Election, and realized that if we generalized the process of data collection and analysis, we could open the door to doing very meaningful comparative analysis of datasets, which in turn could help us actually figure out A. If Twitter matters, B. If it does, what its impacts are, and C. What this implies for the internet and social networks as a whole. We have never been in this for money - we have never looked for funding, this has never been our job, and our systems were given to us by the Web Ecology Project and are hosted at Harvard’s Berkman Center for Internet and Society. We have one machine we pay for, which in May will be coming out of our own pockets (the machine was purchased for a year as part of a class Ian and I slapped together at Bennington College). We are solely interested in the data and its implications, and this is a labor of love. We are more than happy to continue on this project, and are glad you have used our service. Our hope is to be more on the ball with tickets, issues, and other problems as we go through this re-structuring, and come out of this making analysis even easier for people. Thank you for reading this admittedly long e-mail - A more full description of the current situation is located on our front page currently, if you need any more details. For any other questions, feel free to personally reach out to us or contact us via this email account.



Read the full report here: http://bit.ly/ddarvF


Thanks much, 


Devin Gaffney and Ian Pearce