api

Weekly Social Media Update

Twitter Threatens Third Party Clients

Developers are worried that Twitter may begin to limit their ability to create third party clients. An announcement from Ryan Sarver on Twitter’s development mailing list has angered the developer community by suggesting that the proliferation of alternative apps and clients is damaging to overall user experience.

“Twitter will provide the primary mainstream consumer client experience on phones, computers, and other devices by which millions of people access Twitter content (tweets, trends, profiles, etc), and send tweets. If there are too many ways to use Twitter that are inconsistent with one another, we risk diffusing the user experience.”

This is bad news for companies like HootSuite, with its newly introduced tiered pricing system for pro users, and TweetDeck, recently acquired by UberMedia for £19m. While it is unlikely that Twitter will revoke API access for the most popular clients, it is possible that new restrictions will be imposed on positioning of ads and elements of interface design. Let’s hope Twitter doesn’t allow a desire for control to stifle innovation on the platform.

Anonymity, Authenticity, Privacy and Circles

Interesting article on ReadWriteWeb discussing anonymity and authenticity as part of a SXSW debate. 4chan founder Chris Poole makes the case for anonymity: “Anonymity is authenticity… It allows you to share in an unvarnished, unfiltered, raw and real way. We believe in content over creator.” Robert Scoble, on the other hand, argues that “real change comes from people putting their necks on the line”: investing in an argument with their real identity, in a community where they are known and have status.

The introduction of Facebook-powered comments on third-party sites brings the issue of identity to the forefront: users have to decide whether they want every blog comment to be tied to their real name, and visible to their real-world connections. The adoption of multiple personas and the difficulty of segregating content for consumption by different circles in our real life networks has led some to speculate that there is a gap in the market for a tool that can help us navigate these privacy challenges. Rumours that Google is set to unveil a new social network called Google Circles show there is appetite for such a service, though Google has repeatedly denied any such product is in development.

Social Tools for Japan Earthquake

In the aftermath of the Japanese earthquake and tsunami, everyone has been doing what they can to help. Google created a Crisis Centre, along with the Person Finder tool allowing relatives and friends to both search for and contribute information on missing people. Twitter has compiled a useful list of accounts and hashtags to follow for crisis news. As mobile networks suffer outages, people have been communicating via Skype: the service is apparently providing free WiFi and 80 yen of free credit for all Japanese users.

You can donate to the relief fund via Facebook on the American National Red Cross Causes page, and you can even donate through iTunes.

Diesel Island

The new Diesel Island campaign has been building buzz over the past couple of weeks. Visitors to the island are encouraged to sign in with Facebook to become a resident: residents can then become citizens in the community, and claim their own territory as a settler. You can tell the island’s government what you dislike, propose new laws, or run for president.

Tags: , , , , , , , , , , , , , , , , , , , , , ,

0 comments Add This

Get your own vuvuzela news widget!

Just copy and paste the code at the bottom of this post onto your own blog or website and you too can show your appreciation of all things vuvuzela (content courtesy of the Guardian’s Content API)

Toot your vuvuzela!

All the vuvuzela news that fit to print!

Copy this bit (you'll just get the news, not the photo or any styling):

Tags: , , ,

0 comments Share

Interface Development team weeknote (week 1029)

A weekly note detailing the joy and the pain of LBi’s Interface Development team.  One of the apparent conventions of the weeknote format (which started with the esteemed BERG, according to Russell M Davies in this Wired article) is that the week numbering scheme runs from the date of the business’s incorporation.  LBi has a long and interesting history, but I managed to trace it back to the earliest incarnation of the group: Linkhand, date of incorporation 03 September 1990, hence the spectacularly high week number.

Week ending 21/05/10:

This week Will spent a few enjoyable days appreciating the benefits of working to a single platform when he put together an iPhone-specific implementation of one of our clients’ sites. It’s probably a bit hush-hush for now so we’ll do a big reveal of that at some point in the future, but let’s just say it’s “kinda interesting”.

After an enquiry from a colleague as to the existence of a platform-independent version of the popular performance analysis tool dynaTrace Ajax Edition, Ray started to put together a “node.js traffic proxy analysis tool thingy” which has the beginnings of something very useful. It lets you route all your http requests through a node.js webserver, where you can analyse the request headers for all sorts of interesting information. Some further tinkering with this will prove fruitful.

Andy and I continued work on our top secret iPad-targeted webapp. We’ve already spent a few weeks developing the client-side architecture, where we employed an MVC pattern to manage the app, made use of mobile Safari’s offline storage capabilities to take care of state, and layered on our own touch interaction system. Now we’re taking a deep dive into the rendering of the views, which it looks like we’re going to split out into a smaller, independent module and which, thanks to some impressive design work, presents some unique challenges. We’re delivering this module with its own test suite of QUnit unit tests, and we hope it will be integrated into a larger continuous integration workflow.

Our fortnightly Interface Development team meeting had two presentations — Filip talked about the HTML5 geolocation API, and I showed an outline of “How To Design A Good API” which will be pertinent to some of the code libraries we’re developing in-house. We also got some amazingly good biscuits.

We currently have around 20 interface developers in the team so we’ll feature a few here each week and try not to bludgeon you to death with detail.  We’re also looking for some more great interface developers, so if you like what you read here then get in touch!

Tags: , , , , , , , , , ,

0 comments Share