The other day, I needed to set up a Linux virtual machine to test out some commands for installing and configuring my conky script so I figured I’d give it a try.
We’re going to integrate our bug-tracking software shortly too but that’s not the subject of this post.
A more useful means of using this task is to parameterise the Twitter target to take a specified message so that it can be called from different deployment targets: There are lots of extensions from this idea such as updating Twitter with continuous integration results, failed builds, code coverage metrics.
gwibber was working fine and dandy, until one day i could no longer get twitter updates through it, it just gives 'HTTP error 400: bad request" in the little error viewer. I even tried purging gwibber and reinstalling but no luck.
Tweetz loaded up all my tweets INSTANTLY and I even did a test tweet which it sent and refreshed right away.... It loads up my tweets (slowly, but for obvious reasons). I post an update and it immediately sends and refreshes.
A few seconds later and I'm on a 234Kbps connection! (Remember this is the SAME machine, absolutely no changes at all besides the Bell stick).