HassleMe, mySociety’s nifty little reminders site, will continue to send ‘semi-unpredictable’ emails to subscribers – but under new ownership.
Not gone yet
Some canny commenters noticed that we’d tagged HassleMe in our post about closing down some of our sites, but then hadn’t actually included it in the list of projects that were due for closure.
That came about because, although we’d initially added HassleMe to the list of sites headed for the dumpster, there was also some internal debate about saving it.
A small cohort of mySociety staff members were so fond of the site that they wondered whether they might take on its running and maintenance in their own time.
If you have an active Hassle, you’ll have received an email to inform you of this change in ownership (and offer an opt-out, if you’d prefer).
A bit of HassleMe history
HassleMe began as a small piece of script, intended purely for internal mySociety use.
Back in mySociety’s early years, there were only a few members of staff, almost all coders. They knew it was important to keep communicating with the public about what they were doing, but blogging often fell by the wayside in favour of other tasks.
HassleMe was a coders’ solution: a programme that would periodically send an email to a random member of staff and tell them that it was their turn to blog.
Crucially, the reminders were not equally spaced: they would come *about*, but not *exactly* as frequently as you’d set them to. This element of surprise seemed to make the reminders more effective.
Clean the toilet, walk the dog, write a poem
In time, HassleMe was turned into a public service, and people used it for all kinds of things.
Perhaps it was the hassles set to the longest frequencies that were the most interesting. Hassles could be set to recur at frequencies up to ten years, and so people soon realised that they could send messages to a future self. Some of them were prescient:
Are there men on Mars already? What are the plans?
Check back in another ten years with that one, we’re almost there.
Of course, we’re fond of all our projects, past and present, but we’re glad to be able to tell you that HassleMe has a future, under new ownership. If you’d like to set up your own little reminders, or send a letter to your future self, you can do so here.
As mySociety Services continues to develop, we seek a new member to join the team.
We’re looking for a Sales Consultant who will bring their own experience and give us the capacity to discover and explore new leads. As with all mySociety positions, it’s a work-from-home job, but will be based around the Bath/Bristol areas where several of the mySociety Services team are already situated.
mySociety’s commercial work supports our charitable projects, so every new project for a client also does good in the wider world.
Do you know someone who might fit the bill? Send them over to this page where they can see all the details.
We’ve recently secured a small amount of innovation funding from the DfT’s Transport – Technology Research and Innovation Grant and that means that we’re in a position to add new features and functionality to Collideoscope.
Your chance to guide Collideoscope’s development
We’d like to hear your suggestions for new features on Collideoscope—or perhaps you’ve spotted something that could work better.
Please send your suggestions to firstname.lastname@example.org, or use the site’s contact form. We need them in by March 18th, so you have two weeks to gather your thoughts.
What Collideoscope already does
If you’re involved in a cycling collision or near miss—whether you’re the cyclist, a motorist or a pedestrian—you can report it on Collideoscope.
The site sends your report to the relevant local highways authority, and also publishes it online (where there’s the option to remain anonymous).
More than this, though, Collideoscope acts a repository for data on incidents and near misses. In time, anyone will be able to use that data to spot accident hotspots, and the places where accidents are waiting to happen.
This data is available to all, but is especially designed for councils, police forces, road planners, and healthcare providers in their efforts to conceive safer roads, more effective accident deterrents and better emergency care strategies.
And what we’re planning to do
We’ve already committed to a few developments. We’ll be:
- developing better reporting to local councils;
- working with the police to notify them of issues that might require their attention;
- releasing anonymised reports as open data within the next 12 months
…but we’re not planning on stopping there. Your ideas and opinions will guide further development and help us raise further funds for the site.
We thank you all in advance for your time!
Today, after several months of quiet planning, I’m announcing that I will be stepping down as Director of mySociety, although I will remain in the post for the next few months to ensure a smooth handover. An open call for my successor will be published within the next two weeks.
Why now? Quite simply because the coming year will be the most stable period, in terms of effecting a leadership transition, that mySociety has ever had. I want to seize the opportunity to hand over before I start to tire of a job that has been the great privilege of my life.
Thanks to our generous donors and our commercial team’s success we have an unprecedented window of financial security, a terrific team of wide-ranging talents, and a clear three year plan that’s already starting to roll out (I’ll be writing more on this plan, soon). In short, we’ve got a good map, a solid car, and we’ve got enough money for fuel. When could be a better time to change the driver?
For those of you who are our partners, whether charitable or commercial, and wherever you are in the world: don’t worry – this switch isn’t going to change any of our plans to support you and your use of mySociety’s open source technologies. In fact I expect my successor to double down on serving your needs.
And what will I, Tom, do next? I really don’t know – I’ve not got a job lined up, and I’d really like some time off to think about it before I make any big decisions. My main reward – very rare for any founder – is that I get to hand over an organisation that is stable, harmonious, mission-focused and with bags of talent onboard. I greatly look forward to seeing what mySociety’s amazing staff and volunteers achieve next.
Update: the job advertisement for the mySociety CEO position can now be seen here.
Much of mySociety’s work is only possible thanks to generous funding from a number of philanthropic foundations.
Today, we are delighted to announce that we have been awarded a major strategic investment from Omidyar Network totalling up to $3.6m over three years.
This is the third time we’ve been supported by Omidyar Network, and this represents the biggest investment we’ve ever had. Alongside organisations like the Open Society Foundation, Google.org and the Indigo Trust, Omidyar has been central in our transformation from a tiny UK-focused non-profit, to a global social enterprise of nearly 30 staff.
Being supported by Omidyar Network means more than just vital financial support. It means access to their amazing networks of other investees, and advice and guidance from a range of sources. And, also crucial for an organisation that seeks technical excellence, it means the stamp of support from an organisation that ultimately traces its DNA back to the giant internet successes that are eBay and Paypal.
What is the money for?
mySociety’s main ambition, over the next three years, is to help a couple of dozen other organisations, spread around the world, to grow popular citizen empowerment tools that are big enough to really matter to the citizens of a wide range of countries. This means building and growing tools that help people to check up on politicians, demand information and answers, or report and track problems, in hugely varying contexts.
In addition to this, we will continue to maintain and grow the network of users of our technology and support the growing Poplus federation.
It’s a tough goal, and one that will require even more from the organisations we partner with, than from our own colleagues. But the very fact that we can even try to help groups at this scale, is because Omidyar Network enables us to imagine it.
This is a problem we have been warning about for some time. Islington Council were fined £70,000 for a similar incident in 2012. In light of this fresh incident we again urge all public authorities to take care when preparing data for release.
As with the Islington incident, the information was in parts of an Excel spreadsheet that were not immediately visible. It was automatically published on 14th November when Hackney Council sent it in response to a Freedom of Information request, as part of the normal operation of the WhatDoTheyKnow website. All requests sent via the website make it clear that this will happen.
This particular breach involved a new kind of hidden information we hadn’t seen before – the released spreadsheet had previously been linked to another spreadsheet containing the private information, and the private information had been cached in the “Named Range” data in the released spreadsheet.
Although it was not straightforward to access the information directly using Excel, it was directly visible using other Windows programs such as Notepad. It had also been indexed by Google and some of it was displayed in their search previews.
The breach was first hit upon by one of the data subjects searching for their own name. When they contacted us on 25th November to ask about this, one of our volunteers, Richard, realised what had happened. He immediately hid the information from public view and notified the council.
We did not receive any substantive response from the council and therefore contacted them again on 3rd December. The council had investigated the original report but not understood the problem, and were in fact preparing to send a new copy of the information to the WhatDoTheyKnow site, which would have caused the breach to be repeated.
We reiterated what we had found and advised them to consult with IT experts within their organisation. The next day, 4th December, we sent them a further notification of what had happened, copying the Information Commissioner’s Office (ICO). As far as we are aware, this was the first time the ICO was informed of the breach.
From our point of view it is very disappointing that these incidents are still happening. Freedom of Information requests made via WhatDoTheyKnow are a small fraction of all requests, so it is very likely that this kind of error happens many more times in private responses to requesters, without the public authority ever becoming aware.
Our earlier blog post has several tips for avoiding this problem. These tips include using CSV format to release spreadsheets, and checking that file sizes are consistent with the intended release. Either of these approaches would have averted this particular breach.
We would also urge the ICO to do as much as possible to educate authorities about this issue.
Every general election there are a load of projects that all need the same thing – a nicely formatted, accurate list of the candidates who are standing at the election.
Loads of people need this data – journalists, app builders, campaigners, Wikipedians, everyone.
But the government doesn’t actually publish the lists until right before the election, and when it does the data isn’t the least bit suitable for modern use (think unstructured PDFs and worse). It’s way too little and way too late.
YourNextMP.com is a totally free, open database of candidates, that is made partly from screen scraping and partly from volunteer contributions from people who think that having a single good quality list is a sane idea. It publishes the open data gathered both through a nice clean website, and through a nice modern API. Soon it’ll also provide csv export,too. And it means we can have nice shared identifiers for candidates, meaning greater potential connectivity between election-related journalism, tools, sites and projects run by different people and organisations.
The builders of YourNextMP have also taken steps to ensure accuracy and deter abuse, most strikingly by forcing all new data to be sourced, and keeping nice public logs of all the changes (and who made them).
To be clear, YourNextMP is not a mySociety project. We are just very happy to endorse the idea, and to supply one of our open source tools (PopIt) to help store and share the data in useful ways. Plus some of us have been chipping in in our spare time, for instance by adding data.
How can you help?
There are two main ways:
1) Add data! The main thing needed today, 146 days before the election, is the most basic data on who is known to be standing, today. We think that YourNextMP is probably already the most up to date candidate list out there, despite being very much unfinished.
Additional data, about candidates’ Facebook pages, birth dates and so on, isn’t such a high priority right now. You can help by looking up your constituency on the site, or choosing a random constituency, and just using your best Googling/telephoning skills to find out who’s definitely standing this time.
If you want to chat to other people who are doing the same thing, use the #yournextmp hashtag.
Don’t feel you have to stop when you’ve filled in your own constituency – there are plenty more to complete.
2) Spread the word that a single, high quality, free and shared database of candidates is just A Good Thing that people should support.
Who loves time-wasting? Nobody! What is YourNextMP if not an anti time-wasting project? Nothing! So, please, if you’re planning an election-related project, tell people that YourNextMP is a good idea, and consider letting them use your logo on their site, as a sign of good will.
And if you see someone in your office about to pay for a proprietary database of candidates, why not suggest they give the money to YourNextMP instead?
NB: No agencies please.
Party Conference season is upon us again, and, with it, a new set of fine promises and rhetorical flourishes, as each party’s top dogs take the podium. But what happens to those pledges, vows and forecasts once the banners are taken down and the party faithful turn for home?
Cast your mind back to November 2013, and you may recall that there was bit of a fuss about the fact that the Conservative party had removed old speeches from their website.
Not just that, but they’d also effectively erased them from the places where you can commonly find retired internet content… unless you really know where to look.
Was it a sinister rewriting of history, or a simple spring clean of elderly content? Well, that depends who you believe – but here at mySociety, we do think that you should be able to hold political parties to account for promises they made in the past.
Not only that, but we happen to have a splendid tool for publishing the spoken word: SayIt.
So we thought we’d track down that missing content and put it online for anyone to search and browse. And because we are a wholly non-partisan organisation, we did the same for Labour.
Note: we’re not intending to update these collections regularly – it’s a one-off initiative, designed to fill a gap in the public archive. And within the confines of this project, we’ve only published Labour and Conservative speeches.
On the other hand, if you’re interested in setting up similar sites for the other parties, or even taking over these ones, SayIt is very simple for anyone to use: just get in touch.Image by Klaus Riesner (CC)
An analysis, with code and data, of which Commons votes would have had different results, if Scottish MPs’ votes hadn’t been counted since 1997.
By Richard Taylor and Anna Powell-Smith.
PublicWhip is a wonderful thing. Founded and still run by independent volunteers, it contains the results of every House of Commons vote since 1997, scraped from the official web pages and presented as simple structured data. Here at mySociety, we’ve used it to power TheyWorkForYou for many years.
Most recently, it helped our staffer Richard create the new voting analyses on TheyWorkForYou’s MP pages. Want a quick, simple summary of your MP’s voting history on same-sex marriage or climate change, or on any of 62 other major issues? You’ll now find the answer on your MP’s TheyWorkForYou page, all based on PublicWhip data.
But here’s the most exciting thing about PublicWhip. If you know how to get around its slightly forbidding exterior, it contains a treasure-trove of data on MPs’ voting patterns, all structured, openly-licensed and ready for anyone to analyse.
A data challenge
Recently, while discussing the upcoming Scottish referendum, Richard posed a question to Anna: could PublicWhip data tell us which House of Commons votes would have had different results, if Scottish MPs’ votes hadn’t been counted?
This is interesting because if the Scottish people vote “yes” to independence on September 18th, we may see (probably not as soon as 2015, but perhaps soon thereafter) a House of Commons without Scottish MPs. No-one really knows how such a Parliament would be different.
While it was widely reported that that Scottish MPs’ votes carried the decision to introduce student tuition fees and foundation hospitals in England, those were just two high-profile votes. To our knowledge, no-one has published a comprehensive analysis of all votes that were carried by the Scottish MPs.
Anna chose to accept Richard’s challenge, and to use PublicWhip data to carry out this analysis. You can see all their code, and the data they produced, on GitHub.
The headline finding is that only 21 votes (out of nearly 5000 since 1997) would have gone differently if Scottish MP’s votes hadn’t been counted. This surprised Anna, who expected more.
Secondly, if there’s any visible pattern, it’s that English MPs seem to have a stronger civil-libertarian bent than their Scottish counterparts. High-profile votes on 42-day detention, “glorifying terrorism”, allowing the Lord Chancellor to suspend inquests, and on control orders: according to Anna’s analysis, all would have gone differently if Scottish MPs had not been in the chamber.
Other than that – Anna comments – the key finding is perhaps the absence of any other strong trend.
Here is the full list of votes that would have gone differently – click on the date to see the full vote details on PublicWhip. If Scottish MPs hadn’t been in the chamber:
- 5 Sep 2014 The majority of MPs would have voted to send the Affordable Homes Bill to a Select Committee rather than a Public Bill Committee.
- 29 August 2013 The majority of MPs would have voted to agree that a strong humanitarian response to the use of chemical weapons in Syria was required from the international community, and that it may, if necessary, require military action. (You may remember that David Cameron called MPs back from their summer break to vote on this, and MPs rejected the motion.)
- 29 Jan 2013 The majority of MPs would have voted against postponing a review of the boundaries of parliamentary constituencies until 2018 and against delaying a review of the effect of reducing the number of MPs.
- 31 Oct 2012 The majority of MPs would have voted against calling on the UK Government to seek a real-terms cut in the European Union budget.
- 24 Apr 2012 The majority of MPs would have voted to require products containing halal and kosher meat to be labelled as such.
- 24 Feb 2010 The majority of MPs would have voted for restrictions on the amount of carbon dioxide electricity generation plants are permitted to emit.
- 9 Nov 2009 The majority of MPs would have voted against allowing the Lord Chancellor (a minister) to suspend an inquest and replace it with an inquiry and against allowing the use of intercepted communications evidence in inquests.
- 8 Dec 2008 The majority of MPs would have voted to immediately starting the proceedings of a committee of MPs to investigate the House of Commons procedures in light of the seizure by the police of material belonging to Damian Green MP.
- 12 Nov 2008 The majority of MPs would have voted to require membership of new regional select committees to be determined taking account of the proportion of members of each party representing constituencies in the relevant region and for at least one member from each of the three largest parties to be on each committee.
- 11 Jun 2008 The majority of MPs would have voted against extending the period of police detention without making any criminal charges of terrorist suspects from 28 days to 42 days.
- 2 Jun 2008 The majority of MPs would have voted to require the National Policy Statement to contain policies which contribute to the mitigation of, and adaptation to, climate change.
- 15 Mar 2006 The majority of MPs would have voted against a proposed timetable for the Parliamentary consideration of the Education and Inspections Bill.
- 2 Nov 2005 The majority of MPs would have voted against making glorifying the commission or preparation of acts of terrorism an offence.
- 2 Nov 2005 The majority of MPs would have voted to make the offence of Encouragement of Terrorism only apply to cases where an individual intended their actions to encourage terrorism.
- 28 Feb 2005 The majority of MPs would have voted to give a greater role to the courts in relation to the imposition of control orders.
- 22 Apr 2004 The majority of MPs would have voted against installing a security screen separating the public gallery from the House of Commons Chamber.
- 31 Mar 2004 The majority of MPs would have voted against the introduction of variable university tuition fees (top-up fees) of up to £3,000 per year in place of the previous fixed fee of £1,250 per year.
- 27 Jan 2004 The majority of MPs would have voted against allowing university tuition fees to increase from £1,125 per year to up to £3,000 per year, and against making other changes to higher education funding and regulation arrangements.
- 19 Nov 2003 The majority of MPs would have voted against introducing NHS foundation trusts, bodies with a degree of financial and managerial independence from the Department of Health.
- 4 Feb 2003 The majority of MPs would have voted for an 80% elected House of Lords.
- 29 Oct 2002 The majority of MPs would have voted against starting sittings of the House of Commons on Tuesdays at 11.30am rather than 2.30pm.
In the 1997-2001 Parliament, Anna’s code found no votes that would have had different results.
IMPORTANT DISCLAIMER! We can’t conclude that all of the above would necessarily have become law if Scottish MPs had not been in the chamber. Bills don’t become law until they have passed through the House of Lords – not to mention the many other forces of history that would have acted differently.
Get the code and the data
You can see the code used for this analysis, and the full datasets, on GitHub. You can adapt it yourself if you want to do your own analyses.
This analysis is the work of one volunteer: we welcome any corrections. Like PublicWhip itself, the whole point is that it is out in open for anyone to analyse and improve.
Image by Catherine Bebbington. Parliamentary copyright image reproduced with the permission of Parliament.