Its been a good load of years since I visited a promising startup in South Park, San Francisco called Twitter. Oh have they changed…
There has been a whole number of stories and posts about how Twitter is locking down the API calls and access to data. Not only that they are being very shirty with some of the clients and services around it.
Its ironic we use to praise Twitter for there business model formed around creating a ecosystem around its self by leveraging APIs. It was one of the web 2.0 darlings but something happened…
Twitter right from the start had people asking how were they going to make money to keep going?
Well what ever direction they decided to go in, its meant breaking what made it hugely popular.
The question is what will people move on to? Since Twitter for the longest time have sucked the air out of the microblogging ecosystem and seen off most of the alternatives including Plurk, Pownce, etc…
Jaiku Engine is a opensource project after Google bought it and open sourced it. However it lacks something which status.net and identi.ca had built in from day one. Federation… Jaiku engine has also gone quiet since Google plus launched too. I wonder, what if distributed social networking also come to the rescue and provide a nice mix of social networking like facebook/google+ and federated microblogging?
Twitter has done some great things but frankly the business model they have chosen is rubbing up against too many of my and other peoples freedom. I now wonder if I will ever be able to get a dump of all my tweets, dm’s and mentions? (Dataportability!) Google and Facebook have actually been quite good about this, Twitter much less so.
I use to tweet from my Kindle to tweet interesting things I was reading but people and followers complained there was no link to the actual article or post. And to be honest they were right.
Its frustrating that the Kindle can do so much but Amazon’s ecosystem refuses to support self-published content.
However I finally given up on the Kindle for tweeting interesting news bits. Don’t get me wrong, its still my device for long form reading – because frankly the e-ink screen is still the best screen to read text on for me.
This change was made easier with GReader and Plume Twitter client on the Samsung 7+ Tablet. Plume will hold the twitter messages in a queue till I get back online, which is usually at home or work. This also slightly eases the need to enable wifi teathering on my HTC One X (something I can no longer do, till I root it).
The only issue is, when I’m finally back online, all the tweets are posted one after another, which can look like a bit of a tweet flood to some.
I’m also thinking about paying for Instapaper because its rather handy for sending stuff to my kindle (I know I can do it via the free.kindle.com address but I quite like the fact it groups them and sends one a day when theres something new). On top of that Ars Technica’s subscription model isn’t so bad. And access to the full text RSS feeds would be very handy.
I always wondered why XBMC wasn’t available on Android, its been on iOS for a long while now. I assume its the different types of hardware which might have caused the massive delay?
Well its happening and today there was an announcement on the XBMC site with the above video to show its true.
Exciting time! Still waiting for a Nexus Q port 🙂