Further investigation shows that it was the tweet at http://twitter.com/Torbay_Council/status/10218385369 that was causing the issue.
Copying and pasting that tweet into gwibber and posting it seems fine, so maybe it's something to do with the way that the other client (HootSweet) has encoded it?
Further investigation shows that it was the tweet at http:// twitter. com/Torbay_ Council/ status/ 10218385369 that was causing the issue.
Copying and pasting that tweet into gwibber and posting it seems fine, so maybe it's something to do with the way that the other client (HootSweet) has encoded it?