It’s been an interesting few days at the end of the year and then right at the start.
A short timeline of things I saw as interesting and relating to the process of change:
DMFail:
A few days before the end of the year a site called DMFail launched at http://dmfail.com/
The premise is simple, publish twitter messages which should probably have been direct messages but because of a common typo ended up in the public timeline. While some considered it bad for posting these things it was fun and the data was public anyway. It even ended up on Techcrunch and then a lot of people noticed it.
Then something happened. Apparently the Twitter guys noticed this and considered failed DMs a problem so they went on and changed/fixed Twitter direct messages! Change happened, the site closed and we were left with a few fun memories and a better twitter.
MD5 considered harmful today: Creating a rogue CA certificate at the Chaos Communication Congress:
Since some years md5 is no longer considered a good hashing function but there still are people using it because if it’s not broken enough you don’t fix it. Some users of md5 included SSL Certification Authorities including RapidSSL (Part of Verisign).
On 30th of December at the 25th Chaos Communication Congress a team stepped on stage and started their presentation. The presentation about how using the md5 known vulnerabilities and other aspects of RapidSSL they managed to create a Rogue Certification Authority SSL Certificate, perfectly valid and which could be used to sign other certificates. This was a major problem and caused a lot of commotion.
So md5 was already though to be a bad choice but now everyone had proof. And then change happened again, Microsoft released a Security Advisory about the issue and more importantly the direct affected party RapidSSL quickly went and fixed the problem and also wrote a blog post explaining the situation. The response time for the fix was very fast by any standard and we were left with a very good technical article, a video of the presentation and overall better security and understanding from the companies issuing ssl certificates. Change for the better.
Twitter again, Twply makes a mess:
1st of January, new service Twply launches as a way to send your twitter @replies to your email inbox. The only information it needs is your twitter username,password and an email address. It spread quite rapidly since it used your account to send its ad when you signed up. While there was a mention of it doing this on the registration page it was quite hidden and they were accused of spam and bad practices by some.
Because of some email server problems they had to take it down and put the site up for auction and it was bought in a matter of minutes/hours, along with all your twitter login details and email addresses. Launched, sold, bough in the same day. And then the privacy issues/comments started coming in.
But change happens again, I just read some tweets stating that there’s a plan to release OAuth for twitter, at least in beta, very soon. What we wind up with is: people more aware of the danger of giving login details to third parties, a few interesting discussions around privacy, someone wound up with $1200 for Twiply and very soon a better Twitter with OAuth support for better API integration.
Summary:
I see a clear pattern here: Want to change something which is wrong, make that very public and maybe even abuse it. Then change happens.