I updated Nozbe2XMind a bit, published all project sources, and moved distribution to PyPi so it can be installed using standard easy_install.

I created my BitBucket account and started publishing some of my code.

So far I pushed two projects there:

I updated the greader2org script (see previous article for the description of how it can help you to manage Google Reader subscriptions):

• Google password is not stored as a plain text anymore, instead it is saved in GNOME Keyring, KDE Kwallet, or other platform specific password storage.
• manual edits of feeds.ini are no longer necessary, the script just prompts for the necessary parameters on the first run.

The Watchbot games feed changed it's address and is currently available as http://feeds.mekk.waw.pl/WatchbotInterestingGames. Old address should be properly redirected, but I recommend updating it. New feed should handle less popular or older readers better and be faster (technically: it is filtered through feedburner).

Per-player feeds remain unchanged and work as described previously.

The feed notifies about games which:

Having tried many RSS readers I finally stayed with Google Reader. It's not perfect, but works - and let me track my feeds from many computers.

Still, while I am happy with Google Reader as a reader, I am by far less excited with it's management functions. Renaming feeds, reorganizing folders, disabling feeds, replacing them with alternative versions, etc - all those functions are difficult, or not present.

So I wrote a small script which let me export my subscriptions as a simple text file, manage them in the usual text editor and save edits back to Google Reader.

New WatchBot feature. It is now possible to publish WatchBot games on external websites. So, for example, you can show the game you played on your blog.

Here is the example (one of my TeamLeague) games:

Have you ever been curious how is WatchBot picking the games to observe and save? Here is the explanation.

New WatchBot  feature: Atom feeds are now available, so one can use RSS reader to be notified about new games.

The following feeds are available:

• interesting games,
• player-specific games.

In the previous Nozbe2XMind announcement I promised illustrated, detailed instruction. But I finally decided to make a screencast.

So here it is: Nozbe2XMind in action:

Big, important update to my export Nozbe as a mind map script. It is now possible to save changes made on the mind-map back to Nozbe!

Smaller changes also present in this release:

• download actions as CSV file (to be viewed in OOCalc, Excel or other spreadsheet),
• more information on the map (project tags, marking repeating and shared actions).

I updated a little bit my export Nozbe as mind map script. The script is still one-sided (upload to Nozbe is not yet implemented), but the generated map looks a bit better.

Before going into details, some pictures. Example map:

I've read quite a few of articles claiming that blog software is very simple and that one can quickly create his (or her) own blog in a day or two.

To verify this claim (well, building my own blog with - say - Django or Pylons is a tempting idea), I dumped notes of what my current blog software is doing for me.

I recently decided to try GTD (Getting Things Done) to make my life more organized. As I use 3 different computers, web application seemed to be a logical choice. After reading a few reviews, and briefly testing five sites, I finally settled on Nozbe, mainly because it seemed as a place which may help me to learn GTD instead of just making it possible to use it.

It is too early for any conclusions, but in general I like Nozbe while I am collecting my tasks and checking my ToDo's. But since I put noticeable number of tasks there, I find it difficult to do a solid review. No way to see the whole thing (and it is not only a Nozbe problem, other sites also do not seem to offer much help here).

So I wrote a tool which helps me to see all my projects and tasks together and at once.

Fifth article of the FICS bot writing tutorial. In this chapter, I am to discuss different methods a bot may use to communicate with players.

Fourth article of the FICS bot writing tutorial. In this chapter, I am to reimplement the simple registration bot described in part II using techniques introduced in part III (Python, Twisted and FICS block mode). This version makes far better foundation for complicated multitask bot, would somebody want to write one.

In fact, you are to see some parts of WatchBot core here.