Showing posts with label twitter. Show all posts
Showing posts with label twitter. Show all posts

Friday, March 10, 2023

Nobody cares why you follow an influencer

The rise in popularity. of social networking sites in recent years has led to a corresponding growth in the number of influencers.

Some people follow influencers for positive reasons (e.g. they admire  their fitness/beauty regime). In other cases people follow influencers that they dislike (e.g. people might follow Andrew Tate so they can criticise his statements). However, the sponsors who pay the influencers don't care why you are following someone - they simply care that you read the influencer's posts.

You should be aware that if you read postings from someone like Andrew Tate, you are effectively paying his salary.

Sunday, November 12, 2017

The life and death of the @llweather weather station


It seems that my personal weather station is going to be off line for several months (or maybe forever), so I thought I ought to write a short blog post to explain the history of the station and why I have to take it off line. It is a good example of how much work can be involved in keeping a service running despite the fact that the service is supposed to be completely automatic.

Here is the history:
  • My story started during the cold winter of  2010 in Ireland. The weather was so severe that this cold snap has it's own wikipedia page. As a result, I became very interested in weather and I dropped a strong hint that I wanted a weather station kit from Maplin as my Christmas present.
  • This kit included some software to upload my weather data to the internet. This seemed like a cool idea to me, but the software only worked on Windows and I didn't like the idea of leaving a windows PC running 24/7.
  • I used Google to look if there was other software I could use and found several open source options. Eventually I picked a python library pywws and I staredt publishing to my personal weather underground site in March 2011 with a Tonido Plug  (an Ubuntu Linux based plug computer) doing the hard work.
  • In April/May 2015 my plug computer died a natural death due to overheating. Instead of buying a new plug I replaced it with a Raspberry Pi because that had been released in the meantime and it was the new cool thing to use for hobby projects (it was also smaller and cheaper than a new Tonido plug).
  • As part of setting up the Raspberry Pi, I downloaded a new version of pywws. I noticed that  it now had support for uploading to a number of new services including Twitter and so I established the @llweather account to store my tweets. 
  • I though other geeks might be interested in what I did an so I spoke at 3Dcamp Limerick in May 2015  At this talk, an audience member warned me  that I was lucky to have a station still working because the normal lifespan is 2-3 years. This prediction was proven true when shortly afterwards the indoor weather hub smashed to pieces in an accident Apparently it is normally the outdoor equipment that dies due to the severity of the weather it is monitoring, but due to my own clumsiness my home office was a more severe environment than any Irish storm. It wasn't possible to buy a new hub unit so I bought a completely new kit. Luckily my old software configuration worked fine with the new hardware and service was quickly restored.
  • The software was completely automatic, but I found that sometimes my site stopped sending updates and although it was normally easy to fix the problem, it took me some time to notice that there was an issue. Therefore I implemented a monitoring service based upon tweets or lack of same. Since my employer IBM had recently launched the Bluemix service I implemented this in NodeRed running on Bluemix.
  • The monitoring software would send me a Twitter DM whenever it noticed that the weather station had stopped sending tweets or if it started sending blank tweets. There were several possible causes but I noticed that they were normally solved by tightening the USB cable and/or rebooting the Raspberry Pi. After a while I stopped investigating the cause and just tried simple solution. I only investigated the issue when this failed to solve the issue.
  • In early 2017, the station started warning much more often often. Since these problems often solved themselves, I loosened the rules about when to issue a warning (e.g. 40 minutes without a tweet instead of 25 and ignore the first 2 blank tweets). However. the problem got even worse and I couldn't ignore it anymore. I suspected that the raspberry pi was at fault because it was getting old, but a new replacement was not significantly better. I eventually thought to replace the power supply and problem went away for 1 month.
  • When I investigated. I noticed that the indoor hub was getting either no data or crazy data e.g. 51 degrees centigrade in Ireland. If this was Dubai it could mean hot weather, but in Dublin could only mean equipment malfunction. A quick Google said it was most likely a problem with dampness in transmitter unit. When I disassembled the unit there was indeed signs of water damage. Unfortunately, the recommended solution of leaving it in the hot press for a few days didn't solve the problem so I decided to buy a replacement transmitter.
  • The only supplier of spares is Maplin (or amazon/ebay) but all said that they were sold out. I then went to local Maplin store and they said none anywhere in Ireland. 5 available in English Maplin stores but they couldn't tell which store and it might be a computer error. Their web store won't have any in stock until Feb 2018 and I couldn't place an order now even if I was willing to wait
  • The Maplin guy said that it might be possible to buy a spare from another supplier, but he couldn't tell me which brands were compatible with Maplin N96GY. I found some websites selling sparese for the Nevada WH1080PC weather statio which is allegedly co,patible, but when I found one online their picture looked slightl different to mine so I was reluctant to buy

I eventually decided to retire the station for now and reconsider in Feb if I buy a spare when they become available. Overall I must admit I was surprised at how much work was involved in keeping a relatively simple service online.

Wednesday, March 15, 2017

Personalised weather warnings

One of the benefits of having a personal weather station in your back garden is that you should know about local bad weather events quite quickly after they happen. However, the reality is that I don't constantly check the weather data published by my station, so I decided to implement a personal alert system driven off the data.

The obvious protocol for such an alert system is MQTT. However, the MQTT interface module  of the pywws software that I am using to manage my weather station doesn't seem to want to upload any data. After spending time debugging Python (confirming my dislike of the language), I gave up and decided to pursue an alternative strategy based upon the Twitter updates from the station. I implemented a NodeRed  flow on the IBM BlueMix service which monitored the twitter feed and took various actions depending upon what it saw.

The warning rules I decided to implement were:
  • The station is supposed to tweet a weather status every 10 minutes. If 15 minutes or more have passed since the last tweet something has malfunctioned, so the weather station twitter account (@llweather) sends a direct message to my personal account (@bodonovan).
  • When it starts to rain (an all too frequent event in Ireland), the weather station sends me an @reply message to advise me to bring in any washing hanging on the line.
  • The dashboard in my car warns of possible icy roads when the temperature drops below 3 degrees centigrade. Therefore I decided to get my weather station to also send me an @reply message when this happens (luckily this alert gets triggered less frequently in Ireland, but if I moved to Alaska I would need to tweak the threshold).
  • I don't want to be annoyed by repeated tweets about the same weather event, so I put in some code that alerts of the same type won't be repeated more often than once every 6 hours. 
  • The application is configured not to send any warnings between midnight and 7am. I am interested in weather, but not interested enough to lose sleep over it.
It is quite unusual for the temperature in Ireland to drop below 3 degrees at this time of year. Rather than wait for several months to find out if the temperature warning was working I temporarily set the limit to 10 degrees and this is an example of what I got:
Unfortunately, I didn't have to wait too long to get a real rain warning e.g.:

At some stage in the future I will put some more effort into fixing the MQTT problems (partly as a way to learn Python better). But, for now the system seems to be working fine.

Saturday, August 30, 2014

My Weather Station comes back on-line

My old weather station equipment suffered damage and so no data has been reported for the last few months. Luckily I got a birthday present of a new weather station and so my weather site is back online again. Unfortunately the twitter feed is not being updated, but I will fix that soon.

As I was setting up the new station I realised that the clock on my Tonido plug was seriously wrong. For some reason the date skipped forward from 2nd of December 2013 to 16th of April  2030. This means that the forecast data I have been collecting was incorrectly dated. When I get a chance I will write a script to fix up all of the data.

Thursday, May 30, 2013

What tool do I use for interacting with Twitter?

Because, I am a frequent user of Twitter, many people ask me what is my favourite tool to use. I like to be helpful, but the reality is that I do not have a single favourite tool and I use many different tools depending upon the circumstances.

Luckily Twitter keeps a record of the tool that is used to publish each status update, so I decided to write a tool which would automatically analyse my feed.

The following table shows tools that I used for the 1,000 most recent tweets from my account (ignoring the tools which were responsible for less than 1% of the Tweets each):

Percentage Count Tool
31.67% 317 web
24.38% 244 TweetCaster for Android
11.49% 115 foursquare
10.79% 108 LinkedIn
4.00% 40 Tweet Button
3.70% 37 HootSuite
3.30% 33 Facebook
3.30% 33 Twitter for Android
2.50% 25 NetworkedBlogs
1.60% 16 bitly
1.30% 13 Flipboard

Another thing that people sometime comment upon is whether Twitter is a broadcast service or a conversational service. So I also looked at what percentage of my tweets were replies to other people (8.7%). However, almost half of my tweets (42.8%) are accounted for by retweets of content originally Tweeted by someone else.

An academic once told me that my social networking style was "to collect interesting information and share it with my friends". However, a more honest explanation would be that I am lazy and it is much easier to click on a "retweet" button than to think up original content to Tweet about.

My colleague Andy Stanford-Clark was recently featured on a list of Tech Execs that smart people follow and so I decided to compare his activity to mine. More than half of his tweets (67.5%) were replies to other people and retweets accounted for only 10.8% of his tweets. Therefore it is clear that he uses Twitter as a conversational service more than I do.

He also used a much smaller set of tools to interact with Twitter. He only used 8 different tools (as compared to my 18) and over half of all of his updates (65.4%) were done directly on the Twitter web site.

Percentage Count Tool
65.40% 654 web
8.80% 88 Twitter for iPad
8.70% 87 TweetCaster for Android
6.80% 68 txt
5.40% 54 Twitter for Android
4.70% 47 TweetChat
0.10% 1 HTC Peep
0.10% 1 Tweet Button

It is also interesting that Andy is a much more prolific user of Twitter than me. I had to go back as far as 23/Nov last year (about 6 months) to get 1,000 tweets from my feed, while I only needed to 10/April this year (slightly over a month) to get 1,000 tweets from Andy's feed.

It would be interesting to a similar analysis on a wider sample of Twitter users, because I guess there is no such thing as a typical Twitter user.

Friday, May 10, 2013

Tweeting about local weather conditions

I am quite proud of my personal weather station and the fact that it automatically makes reports available through a dedicated page on the Weather Underground site. However, until recently I was embarrassed to admit that the weather station didn't have its own twitter feed. Yesterday, I rectified this situation and I can now boast to my fellow geeks that the station is Tweeting hourly weather reports as @LLweather which is a new Twitter account I created for the weather station. In fact it is one of a large network of private weather stations in Ireland tweeting weather reports with the #iwn hashtag - this should not be surprising because most Irish people are obsessed by weather.

Initially I tried to write a short python script to do the updates, but then I discovered that this feature was already supported by the PYWWS package that I was using to upload the data to Weather underground. There were even clear instructions available on how to configure the software on their web site (I had to upgrade to v12.10 to get it to work).

After I set it up I was surprised to notice that the weather station was apparently giving weather reports about 20-25 minutes into the future. When I investigated I found that the clock on my Tonido plug was running alarmingly fast. I tried to set up the NTP deamon to keep the clock synchronised, but this proved complicated because the plug is running a very old version of Ubuntu. I corrected the time manually and will keep an eye on it until I get around to configuring NTP properly.


Thursday, August 25, 2011

Circles, Friends and Followers

There has been a lot of interest in the recent launch of Google+ social networking service. One of the features that has gained most attention is the fact that  Google+ use the concept of circles to track the relationships between people as distinct from how Facebook uses Friends and Twitter uses Followers. However, many people are confused about how Google+ uses circles so I thought it might be helpful to write a brief explanation.

Facebook was originally based upon a simple model of symmetric friend links, this means that for if Tom is Jane's friend then Jane must also be Tom's friend. It is for this reason that when you add a new friend on Facebook the other person must confirm that they also wish to add you as a friend. This simple model of friendship works well for the friendships that we establish in school (and hence it is a good match for Facebook which originally was most used within a school setting). However, real world relationships are much more complex and hence mode advanced models of social relationships are sometimes needed.

Not all friendships are the same. For example, most people would have different criterion for what they would be comfortable sharing with their work colleagues and what they would like to share with their close friends and family members. For this reason, Facebook introduced a feature called 'lists' where you can divide your friends into different catergories. When you share something on Facebook you can choose whether you want to share it with all of your friends or else restrict it to only the members of a particular list. Since this feature was not originally in Facebook when it launched many users are not even aware of its existence and hence they tend to share everything with all of their friends (and this is the default anyway).

The other weakness in the Facebook friendship model is the fact that it is not necessary true that the people whose updates you would like to read are the same as the people whom you are happy to allow read what you post to the site (Facebook uses your friend list for these two different purposes). Systems like Twitter recognise this difference by implementing asymmetric links that they call 'followers'. By default all updates sent to Twitter can be read by anyone. If I add someone to my 'follow' list it simply means that I would like their updates to appear in my default stream and does not imply that there is any relationship between us. For example, I follow the Dalai Lama on Twitter because I am interested in reading the profound thoughts that His Holiness posts to twitter, but I have no reason to think that His Holiness is interested in reading the boring stuff that I post. For this reason the Dalai Lama has over 2.5 million followers on Twitter, although he doesn't follow anyone.

Google circles are asymmetric links (like Twitter) because you can add anyone you want to your circles and there is no need for them to approve this and/or add you to one of their circles. However, Google circles are not like Twitter follow lists because circles are used to control who can read your updates as well as whose updates are presented to you in your default stream. Everytime you post something to Google+ you are asked to specify which of your circle's members should be allowed to read the update (there is a special group called 'public' that you can share with if you don't care who reads this update).

By default Google+ shows you all of the updates you are allowed to see from any of the people in any of your groups, but you can also click on a circle name to only show updates from people who are in that circle. Therefore in order for you to see a particular update it will be necessary that you have added the person who posted the update to one of your circles and it will also be necessary for you to be a member of one of the circles that the person posting the update chose to share it with. Hence the logo shows intersecting circles.

Wednesday, February 9, 2011

The Irish General Election is really using social media

The campaign is now well underway for the Irish general election which will take place on 25th of February. One thing that has struck me about the campaign so far is how almost all candidates have finally appreciated the importance of leveraging the internet and social media tools.

I suppose much has changed in the four years since the last election. This report from the RTÉ Drivetime program reviews how the various candidates are engaging with social media - while some candidates are clearly more successful than others, all of them are trying to win the on-line battle.

The election reports on the nightly TV news is typically started with a summary of the political Twitterings of the day. Most of the relevant Tweets are tagged with #ge11 so it is easy to follow the conversation.

Thursday, September 2, 2010

How much notice should service providers give their customers when the terms of service change?

One of the cool things about the Twitter service is the fact that they don't send many emails to their subscribers to let them know how wonderful their service is. They have a very unusual attitude in that they expect that the usefulness of their service should be able to speak for itself. Therefore when they sent me an email today entitled "Update: Twitter Apps and you" I decided to actually read the email.

It started out quite well:
Over the coming weeks, we will be making two important updates that will impact how you interact with Twitter applications. We are sending this notice to all Twitter users to make sure you are aware of these changes.
Then I read the next paragraph:
Starting August 31, all applications will be required to use OAuth to access your Twitter account.
At first it sounded reasonable, but then I realised that this email was being sent on 2nd of September!!! I know internet time is different from normal time, but how can they use the phrase "in the coming weeks" to refer to 2 days ago!!

Suddenly the penny dropped and I realised why BlueTwitSidebar stopped working with Twitter yesterday. I pinged the developer of this tool to let him know of the issue, but it turned out that he already knew about it becuase everyone was screaming at him.

Surely this is a very unfair way to treat users by telling them of a significant change in authentication policy after it has already been implemented :-(

Wednesday, September 1, 2010

Report on Blogtalk 2010 conference last week

A number of people asked me to write up a report on the Blogtalk 2010 conference that I attended last week. This was a really interesting conference with lots of interesting topics being discussed, but since most of the people there were really great at using social media tools and they were all posting commentary all the time I don't think I can do really much better than to point you at the very active Twitter feed for the conference using the hashtag #blogtalk2010 or Emer Lawn's excellent summaries of day 1 and day 2.

I will write up a few blog posts later on specific topics that came up during the conference, but my general impression was to be amazed at the amount of buzz and excitement which can be generated when a bunch of like minded geeks get together. I was also delighted to see that my Alma Mater NUI Galway is looking both completely new and modern, while at the same time being reassuringly familiar from 30 years ago (when we used to call it UCG).

You can see the slides for my own talk with Gabriela Avram below. It went down pretty well despite being in a bad slot as the second last presentation of the conference when everyone was tired (including the presenters). A number of the other presentations are also available on SlideShare, but there is no unified feed for them available (yet). I believe that the conference site will be updated shortly with links to all of the presentation and video's of the various presentations (every move was captured on camera).

Thursday, July 29, 2010

Is Twitter a conversational mechanism

I hear a lot of people says that Twitter is a great tool for enabling conversations. In my experience Twitter can be used for conversations, but it is far from ideal for this purpose. I think that what people are really saying is that they are surprised how much conversations happen on Twitter given that the platform was designed primarily as a broadcast mechanism (for distributing news about what you are doing).


A conversation takes place when a person reacts to what they hear someone else saying either by responding to the original speaker or by passing in the message they heard to others. In some ways, Twitter is seen as a replacement for email. In order to judge whether Twitter is more likely to be used for conversations than email I decided to compare the what percentage of the contents of my email inbox and my Twitter stream involve conversations. The results are summarised by the following table:

ChannelReTweets or ForwardsRepliesNeither
My Email Inbox
11%22%67%
My Twitter Feed 
11%4%85%

It is clear that I see much fewer conversations happening via Twitter than via email, because although 22% of the emails I receive are replies, only 4% of the Tweets that I read are replies (to my email or someone else's). It seems that both mechanisms are used equally good at spreading news because 11% of the messages on either format are forwarding an email from someone else or re-tweeting a message that someone else twittered.

These results are skewed by the fact that not all emails or Tweets come from normal people. Some of the emails I receive are from automated programs e.g. the automated software build system we use will notify when a new build is available. In a similar way, some of the Tweets appearing in my stream come from semi-automated sources e.g. the Irish Times feed is really just an automated series of links to news stories on their web site. I am not sure I am a totally normal person (if such a concept even exists), but I decided to analyse the statistical profile of what I write:

ChannelReTweets or ForwardsRepliesNeither
My Sent Emails 
14%64%22%
My Tweets39%18%43%

Although the numbers are different here, I still see that I clearly use email more for conversation than I use Twitter - the vast majority (78%) of my emails are either replies or forwards of someone else's message while only 57% of my Tweets involved either replying or forwarding someone else's message. I think that the relatively high percentage (39%) of my Tweets which are re-tweets of someone else message is an indication of the fact that I am not very confident that I know how to use this new medium and so I play it safe by re-tweeting other people's content whenever I find it interesting.

I don't claim to be an expert in advising people about the best way to use Twitter, but it is sometimes easier to identify people using the platform badly. I was amused to see the twitter feed for Poolbeg (an Irish book publisher). The feed was established on 16th of January and started off well with several tweets in the first few days, but at the end of the first week they posted a status message "Evening all - it's been a busy week for Poolbeg. Wine time now though!". Then there are no more tweets in the intervening 6 months. Clearly the person who was responsible for updating their Twitter account thought that drinking wine more interesting than Tweeting :-)

Saturday, February 20, 2010

Comparing Connections glue to StatusUpdater and WildFire

Connections Glue is a popular tool for keeping up with your Lotus Connections and Twitter networks. Following my earlier post where I compared Status Updater and Wildfire tools for doing the same thing a few people asked me to do a comparison between these tools and Glue.

I had never used Connections Glue before and so I found this video demonstration gave me a very quick look through the features:


The main difference between Glue and the two other tools is that it is implemented as an Adobe AIR application rather than a Notes/Sametime plugin. If you (like me) keep Notes and/or Sametime running on your machine all day long, it is handy to use a plugin for your microblogging, but if you don't a tool like Glue would be a much more light weight.

The main limitation with Glue is that it only supports Lotus Connections and Twitter. In addition it can only support a single instance of the Lotus Connections service (like Status Updater, but unlike Wildfire). However, in common with most AIR applications I have seen, Glue has  a very slick UI. I said before that the Satus Updater UI is smoother than Wildfire, but Glue takes things to another level:
  • When minimised Glue hides unobtrusively in the system tray
  • When new Tweets or profile updates are received in your network you are notified by a subtle semi-transparent pop-up which will dismiss itself after several seconds.
  • You can re-tweet the tweets you are reading with a single click.
  • When browsing through updates from someone outside your network you see a + sign which you can click on to add them to your network if you like.
  • Glue provides you with an interface to the files functionality in Lotus Connections as well as the profile updates.
In summary I think that Glue may be an interesting tool for users who don't normally keep Notes or Sametime running on their machines, but for anyone who does I think they would prefer either Wildfire (for non-IBMers) or Status Updater (for IBMers).

Friday, February 12, 2010

Comparing StatusUpdater and WildFire

I am sure there are many people like me who try to stay involved on several different micro-blogging sites. This can be difficult and so it is good to find tools which can help. Both WildFire and Status Updater are Notes/Sametime sideshelf plugins which allow users to read and write to several micro-blogging platforms at the same time. This blog post compares the two tools.

Just in case you think I have a conflict of interest, I should declare that I was involved with an IBM internal project to develop MicroBlogCentral (MBC) that was later released to OpenNTF under the name Status Updater. It seems that there was a totally independent effort carried out by a business partner in Australia to develop a similar tool which they called WildFire which seems at first glance to be very similar. Both tools offer you an option to configure several micro-blogging accounts on different services and then you can enter a status update into a text box and have that status update automatically posted to whichever micro-blogging services you choose.

However, there are a number of aspects where they differ:
  • Widlfire supports significantly more services than Status Updater. Status Updater can only support Twitter, Sametime and Lotus Connections services, while Wildfire also supports Bebo, Facebook, GTalk, PingFM. Plurk, Tumblr and WordPress. Even I don't have accounts on all the services that Wildfire supports, so I wasn't able to test them all. It seemed to work fine for me on Lotus Connnections, Facebook, Sametime and Twitter, but I couldn't get it working on PingFM (this is probably a configuration error on my behalf).
  • To be fair the IBM internal version of Status Updater does also support BlueTwit, Fringe and Beehive/SocialBlue, but this is hardly of interest to people outside of IBM.
  • A really significant advantage of Wildfire is that it supports multiple instances of a service. This means that you can use it to post to two different Twitter accounts (e.g. if you have a personal Twitter account and you also post to your company's official Twitter Feed). It also means that you can participate on more than one implementation of Lotus Connections (e.g. you might interact with different communities on the Bleed Yellow and Lotus Live sites).
  • A big limitation of Wildfire is that although you can use it to send updates to several sites, it only presents to you your friends updates from Twitter. In contrast Status Updater shows you updates from all of the services you have configured. There is a drop down menu which users can choose what exactly is presented in the windows (although I suspect many people don't realize that this menu exists so I show a picture of it below)

  • In general the Status Updater UI is more smooth than that of Widlfire - this is probably due to the fact that the originator of the project works for IBM's UX team. For example
    • It provides a system tray icon for rapid access when Notes/Sametime is minimized.
    • When you click on a username, you will be navigated to a list of that person's status updates presented within the plugin UI rather than launching a separate browser window.
    • Status updates from each of the services appear with a different background colour so you can see at a glance which service a message was posted upon.
    • For the Lotus connections updates you see an indication of how many people have commented on the status update and with a click you can read these comments and add your own (again without leaving the plugin's UI).
  • The following screenshots give you a quick idea of what the Status Updater UI looks like. The updates with a light blue background are from the IBM internal BlueTwit system, the updates with a Yellow background are from BeeHive/SocialBlue (another IBM internal system) and the updates with a dark blue background are from Twitter. I obscured some of the text to protect confidentiality, but I left in some text to give you a flavour of how the platform is used:


  • The Wildfire UI uses icons which are not intuitive and hence I find very hard to remember what they do without hovering over them and getting the tool-tip to appear. Another problem I have with the Windfire UI is the way it presents whether or not an update has successfully been posted. After you click the submit bin you see a nifty icon beside each service you selected indicating that Wildfire is trying to post your update to the service. When the update is completed the icon changes to a tick if it was successful or a big red X when it fails for any reason - the trouble is that the X or tick goes away after about 2 seconds so if you are not keeping your eyes on the screen you can easily miss the status notification and hence might not realize that a status update failed to register. The sequence of screenshots below illustrate how it looks (which is great except for the fact that the status disappears so quickly).

  • Wildfire was developed with windows support only in mind (a big minus for a Linux fan like me). However, it is actually just the configuration process which is Windows specific. It would not be hard to make the application work across all platforms (I posted a note to their forum telling them how to do this so hopefully they will pick up on this).
  • Another difference at the code level is that Status Updater has a clean division between the code application and the plugins providing support for each of the services. This means that support for additional servcies can be developed independently of the core application. On the other hand, having the code split into several plugins does make it slightly more complex - not only for the developers, but also for the users who will need to install several plugins to get the same functionality.
Either of these tools could definitely be useful for someone who wants to be active on more than one micro-blogging platform. As you can see both tools have significant areas where they are stronger than the other. Therefore I can't reach a definitive conclusion about which tool to recommend and each user would need to decide based upon which requirements are more important to them. I would guess that many IBM internal people would prefer Status Updater because of its slightly smoother UI and its support for the IBM internal platforms. Most others would probably choose Wifdfire because its platform coverage is so much more extensive.

Personally I would love to see the two projects merging to produce a tool which combines the best of both. I have spoken with Jessica who is the main developer behind Status Updater and she is in favor of this idea. I will renew my efforts to contact the people involved in the WildFire project to see if I can insterest them in such a merger.

Monday, January 25, 2010

Can MT help you have Twitter interactions across langauge barriers

IBM has been involved with the Centre for Next Generation Localisation (CNGL) which is is a research group funded by Science Foundation Ireland. However, this is not an ivory-tower research group. They are tacking very practical problems about how to improve translation and localisation technologies so that they can be applied to new challenges that are emerging in the modern world.

For example, many machine translation systems only perform better on long texts where the words are appearing in context, but Tweets posted to Twitter are very short with no obvious context. Furthermore, they may contain abbreviations, mis-spellings and specialised terminology. As a result the GNGL team have launched a special project to tackle the issues that arise in this specific context.

They are now looking for volunteers to test out their system and even better provide them with feedback. Ideally they would like testers who follow people who tweet in different languages from their target set (English, French, German, Spanish and Italian).

Here are the instructions directly from the author:
My name is Declan Dagger and I work on DCM3 in Trinity College with Vincent Wade. We have built an application called twanslator on top of the twitter micro-blogging network that allows you to translate tweets into different languages. Initially we are looking to collect user centric data on the capabilities and limitations of text analytics and MT in limited character/context environments such as twitter.
 
I would appreciate your help in conducting this research. You can get involved by doing the following:
  1. Go to http://www.myisle.org/twanslate and login in using your twitter account details (if you don’t have an account you can sign up at http://twitter.com).
  2. When your tweets arrive there is a simple drop down menu of languages available which the tweet can be translated in to. When you translate a tweet, a rating system is then available (thumbs up / thumbs down) to indicate whether the translation was accurate or not. You can also add comments to the translation using the comment feature. Please rate all the translations you invoke as this is critical to our research.
  3. We appreciate any feedback, comments and/or suggestions you may have on how to improve the twanslator application. To leave general feedback, please click on the “app feedback” icon on the left of the page. You can also make suggestions by tweeting them to “@myisle #twanslator”.
  4. We will be adding new features to the application over time and ask that you follow @myisle so we can keep you informed of any updates.
  5. As we need a relatively large user base to conduct our research, we would be grateful if you could suggest to your followers and colleagues to also use twanslator.
  6. We would encourage you to suggest tweeters to @myisle that you recommend following for CNGL regardless of the language they tweet in. For example “@myisle you should follow @joe_bloggs [a French expert in localisation]”.
 
Part of the MyISLE goal is to build an open research platform for CNGL members within the social networking space. As such, twanslator has been developed using web services, workflow and customisable interfaces. So for those in CNGL interested in using twitter as part of a research study, please contact me at Declan.Dagger@cs.tcd.ie and I would be more than happy to make these services available to you.


The initial user interface is somewhat rudimentary, but I am sure it will improve over time. I have sent some feedback to Declan and I would encourage all of you to do the same (the more people who ask for the same feature the more likely it will be implemented).


Friday, January 22, 2010

Review of the IBM stand at the Young Scientist and using social software for connecting with children #ibm4btyse

Last week I was involved in helping run the IBM stand at the BT Young Scientist and Technology Exhibition. One of the areas that I focused on was using social software to help publicize what we were doing on this stand. This was a hectic week. Now that I have had time to digest what happened, I decided to write this blog post which  will review how effective the stand itself was and how/if the various social software channels we used helped connect with the young people attending the exhibition.

In common with many other exhibitions there is a tradition that companies running stands at the Young Scientist will attempt to attract visitors by giving gifts to the people who visit their stand.  IBM followed that tradition with 4 diiffernt things we were giving away to our visitors. This was very sucessful - at one stage on Friday it was not physically possible for anymore people to enter our stand. However, I was surprised that the popularity of the different gifts did not relate to what they cost:
  1. Anyone who visited the stand and made a token attempt to appear interested in our stand was given a YoYo with the IBM logo. We had a total of 10,000 YoYos were available in a variety of colours and they were all distributed over the 3 days. They were  hugely popular with the students and were probably responsible for a huge percentage of the visitors to the stand. A typical interaction with a student almost always sarted with the question "is it true you are giving out YoYos?". Of course we relied "yes, but not that you are year would you like me to tell you about IBM ..." The students felt morally obliged to feign interest in our messages in return for their valued prize.
  2. Each visitor to the stand was asked to enter an idea on our web site for how technology could be used to make the world smarter. Most students were enthused by the competition and put a lot of thought into their entry. This was a good way of ensuring they really understood the Smarter Planet theme we had for our stand. We were giving out a prize fof a laptop for the best idea, but very few of the students showed any interest in the prospect of winning a laptop.
  3. Each day we held a draw for a Nintendo Wii. All they had to do to enter the draw was write their name on a ticket. There was some interest in the chance of winning a Wii - but the scramble to enter this was much less than the scramble for free YoYos. I think the mood was captured by one young boy (I would guess aged about 8-10) - when asked if he wanted to enter the draw he said "I already have a Wii, but I suppose I could always sell it on eBay" - clearly a youngster with business acumen :-)
  4. We were also giving out Ubuntu Live CDs and copies of the "IBM Open Client for Smart Work" at the pedestal where we were demonstrating Open Source software. There was very little interest in this from the younger kids, but some of the older students and their parents did show an interest. Some of the visitors to the stand were already using Ubuntu, but were fascinated to learn why IBM was promoting it. In fact a large number of the CDs were given to the IBM volunteers who planned to install it on their own PCs.
The communications team were keen to use social software tools to promote the stand to students since they heard that the students would all be keen users of these tools. I was asked to advise them as an expert in social software. I don't consider myself of an expert (expertise is relative), but I found that Laura Cowen and Sacha Chua were only to happy to fill in for the gaps in my knowledge.

The social software tools we chose to use were:
  1. We created a Wordpress blog and we planned out a schedule for which of the team members would post each day so that it would not be forgotten. Much to my surprise we kept to the schedule and even posted a few additional blog posts when ideas occured to us during the week. We managed to get IBM employees to comment on the blog by using subtle pressure on them, but I don't think only 2 of our commenters were not IBM employees (of course I could be wrong because am not 100% certain of the identity of all of the commenters).
  2. We used the existing IBM Twitter account @IBMIrelandEvent and also the hashtag #ibmbtyse - the reaction to this was good, but again I suspect we were more successful in letting adults know about the stand than in attracting youngsters. The young people did use Twitter, but generrally were more intersted in interacting with their own social social circle than in interacting with IBM. A few students who were keen ubuntu fans did send us messages via Twitter so I guess it was high quality interactions even if not high quantity.
  3. The people manning the stand took lots of pictures and posted them to Flickr (e.g. my photos), Picasa (e.g. Donnacha's photos) and other web sites, but we did not organise them in a way that allowed people view all the content together. The communications team did produce some fairly professional looking videos and posted them to the YouTube channel. Speaking to IBM people they were very impressed, but I am not sure how many others viewed them.
  4. We created an identica/StatusNet account @IBMIrelandEvent but did not really use it. The communications team were using HootSuite for managing all of the social media channels and since we never connected the identica account with HootSuite nobody remembered to manually cross post. In any case I don't think many students would use identica so our omission was not noticed.
  5. We created a Facebook event page, since we were advised that most of the students would be very keen users of Facebook. We didn't hook this up with HootSuite either since it seems that HootSuite will only post to a person's Facebook home page and not to an event page (maybe we don't fully understand HootSuite). Nevertheless I manually posted links to most of our content as it appeared and also posted links to articles about the event in the mainstream media. I think that this pages was also used more by IBMers than by the target audience - 15 of the 19 confirmed guests and 9 of the 15 people who said they were "maybe attending" were IBM employees. I think the problem is that Facebook invites can only be sent to your friends and the people at the exhibition were not our friends on Facebook. Indeed the common wisdom is that the students would be advised against interacting with us on Facebook since we are all dangerous adults.
In summary it was a great experience and I think people attending got a good impresssion of IBM. This video gives you a quick flavour:


Update 23/Jan: I forgot to mention the Facebook page in the initial post so I added a paragraph about that.

Thursday, October 29, 2009

Your Twitter followers are not your friends

There has been a lot of excitement recently about the fact that Twitter have introduced a lists feature At first glance it seems similar to the Facebook feature where you can make lists of your friends. However, the comparison is not totally valid because Twitter uses the concept of a "follower" which is not the same as the Facebook of "friend". If you make the mistake of confusing your followers for friends, you will be making a big mistake.

Facebook was initially aimed at young people. The conventional wisdom is that it is dangerous for young people to speak with strangers, so the default setting in Facebook is that your updates can only be seen by people that are formally recorded as your "friend". Friendship is a two-way relationship, so in order to record a friendship link both users have to confirm that the friendship exists.

As everyone knows the term "friend" covers a wide variety of relationships. Robert Dunbar famously proposed that people can maintain a maximum number of about 150 real friends. However, a friend on Facebook just means "people whom I don't mind if they read my status updates". This is a very loose definition of friendship and many people who are very open can have hundreds and even thousands of friends on Facebook.

To help people who have large lists of firends, Facebook has a feature called lists. This is a way of recognizing the fact that not all friendship links are the same. For example, I might divide my friends into three lists named "family", "work-colleagues" and "drinking-buddies". This allows me to project a different image to each of the types of "friend". With careful use of the Facebook security features, I can ensure that members of my family will only see updates containing cute pictures of my children, my drinking buddies will see details of my wild revelries and my work colleagues only see updates which contain thoughtful insights in relation to our business. Of course the lists can overlap so that my brother who works for the same company and also joins my in my wild social life will see a complete picture of my activities.

Twitter does not formally record friendship in any way. By default all twitter updates are public and can be seen by anyone. It is possible to place access control on your twitter updates, but hardly anyone does that. Twitter has a concept of "followers". If you record the fact that you follow someone, this simply means that you want updates from that user to appear on the default page shown to you when you log into Twitter.

If any of my friends are on Twitter I normally add them to the list of people I follow - I am sure many of them also follow me. Most people follow this principle so there is a tendency for the "followers" network on Twitter to resemble the "friends" network on Facebook. However, a very significant difference is that while the "follows" relationship can be bi-directional it does not have to be.

Most people follow a similar number of people as who follow them and there is a large overlap between each group, but there are a few notable exceptions to this rule and these exceptions make a big difference to the overall structure of the network. For example, I follow the Irish Times feed to get notified of news stories, but the Irish Times does not follow me (the feed is probably produced by a software program rather than a real person anyway). Many influential Tweeters significantly change the flow of information through the Twitter network. For example, the software pioneer Mitch Kapor has 14,037 followers but is only following 322 people. Similarly the publisher Tim O'Reilly is only following 583 people but has 1,243,295 followers. It seems that there is probably a limit to how many people you can follow (the actual number depends on how much time you spend on Twitter), but there is no limit on the number of people who can follow you.

I created the following lists which grouped the people that I follow by the reason why I follow them. Obviously the lists are not mutually exclusive (e.g. I put any Irish journalist on both the journalists list and the paddies list):
  • Journalists - this list contains professional journalists and official newspaper feeds (actually I originally mis-spelt this as "Jornalists" but I fixed it for fear of getting a reaction like Gordon Brown). I doubt very much if any of these people follow me back.
  • Paddies - people who have some association with Ireland. Some (but not all) of these are friends of mine and might follow me back
  • Gadgets - people who tweet about cool gadgets (mainly a subset of journalists)
  • Linux - people who tweet about Linux and open source software
  • Thinkers - people who write thoughtful articles. I know this is a list I might get some stick about, it could also be called a list of people whose opinion I value.
  • IBMers - people who work for IBM
  • Lotus Related - people who tweet about Lotus products and/or social software in general
As I was playing with the lists interface I realized that you could put people on lists that you are not following. I leveraged this fact to unfollow some of the official IBM feeds (since they are still in my ibmers feed I can easily check them out whenever I want and I don't need to clutter up my home page with too many boring work related Tweets). It is also possible to follow a complete list in one step. I used this to follow Robert Scoble's list of the most influential in technology. This allows me to effectively delegate to Scoble the job of finding influential people writing about technology.

When I initially joined Twitter I was anxious to build up a network and clicked the "follow" button quite liberally. As a result there were a few people on my follow list that I didn't really know who they were and hence I could not decide which list they should be on. I decided that it was probably best to unfollow these people. After this exercise, I see that of the people 157 who follow me, I follow 100 of them back. I think that this probably a good ratio, because it is not good to be in a clique where all of my friends are also friends of each other and we only talk to each other.

In general the lists feature makes Twitter more useful, but most importantly the exercise reminded me on the key difference between friends and followers.

Update: I just found this useful article which gives advice on how you can use Twitter Lists.

Monday, May 25, 2009

I don't want to have to update my status several times

I have accounts on several different social networking sites (mainly just to try them out). As a result it is a major pain for me to keep an up to date status message on each of them. What I would really like is to be able to update my status on one site and have that updated status automatically propagate to all of the various sites which provide a status tracking service.

I haven't (yet) found an ideal solution, but I have at least found two different ways to update my Facebook status without ever having to directly launch Facebook.
  1. I installed the Twitter application on Facebook, by following these instructions. Now each time I update my twitter status I can have the status update automatically propogate to Facebook by simply appending #fc at the end of the status message
  2. I linked my Plaxo account to my Facebook account by logging into Plaxo and clicking on "edit my profile", selecting "websites" tab and then clicking on the Facebook icon and entering my credentials. Now any time I update my Plaxo status it automatically generates a Facebook status update with the same text and visa-versa.
Am I the only person who thinks it is a major pain to keep updating my status on all these sites? Does anyone know of a cool solution that they can point me to?

[Update 26/May] - It turns out that the Plaxo/Facebook connection is bi-directional and not one way as I originally stated (the Facebook to Plaxo update just happened very slowly so I thought it wasn't working)

[Update 4.June] - Robi Brummer pointed me to ping.fm which is a great site for updating several sites at once. The list of services that work with ping.fm is truly amazingLink