Changes in this version of imapfoo:

* add --netrc option
	Adds support for authentication data in .netrc
* retired --connect
	Replaced by --login, --host and --port

Starting with this release, Hover will respect case of search terms and no longer replace it with the one you specified, e.g. the following links are all generated with one definition:

Hover, hover, HoVeR, hOVEr, …

I recently updated my NC10 from lenny to squeeze. After that xbacklight stopped working:

$ xbacklight -set 50
No outputs have backlight property

Looks like the solution is to upgrade to the latest BIOS (11CA, available from samsungpc.com).

I created a FreeDOS USB stick with information available from Smörgåsbord and fdos.org, copied the BIOS to it, bootet from the stick and successfully flashed my NC10.

Now xbacklight works again.

The new version of imapfoo adds support for:

• generating checksums and testing them again.

• reading config options from file.

• reading password from file, possibly STDIN.

First public version of imapfoo, a tool to quickly add random or generated mails to a specified IMAP folder. The freshmeat project entry should appear soon.

This release adds Text Widgets support to Hover. Thanks to John Terry for the patch.

NetworkManager in Lenny writes it’s PID to /etc/resolv.conf:

### BEGIN INFO
#
# Modified_by:  NetworkManager
# Process:      /usr/bin/NetworkManager
# Process_id:   2869
#
### END INFO

This leads to etckeeper displaying a change every reboot:

This patch to the debian package stops NetworkManager from writing the INFO block to /etc/resolv.conf.

Alternatively, there is a backports package for lenny with an updated version of NetworkManager.

A couple of days ago Blizzard decided to ban my Diablo 2 key from Battle.net, effectively cutting me off from online play.

After contacting their Online Support I was told, that my key was banned, because I had violated their Terms of Services, namely using “Third Party Software”.

Now the interesting part is, that I haven’t.

My first reaction was simple, “Well guys, I haven’t. Looks like a mistake, please fix”.

Their response however was that it was clear to them. I had been using some Software I was not allowed. Case closed.

I tried to get more details, e.g. what software I allegedly have been using and what I supposedly did wrong.

They replied by closing the support ticket and sending me a link to a feedback from where I was told “Please note, you will not receive a response regarding any information provided in this webform”.

I went back to my support contact and asked them (again) to provide a comprehensible explanation on what I did wrong exactly.

Guess what, they closed the ticket again.

In the end Blizzard banned my key for some reason which they refuse to tell me.

This leads to an interesting problem: Suppose I would buy another copy of Diablo 2 (which I won’t) to be able to play again. How can I be sure that I won’t get banned again? I have no idea what I allegedly did wrong. How am I supposed to not do it again?

For me, this leaves only one conclusion: No more Blizzard games.

Dear Blizzard, if you treat me like this, I don’t want to be your customer anymore.

A new version of Hover is available. This release fixes an https related problem with the internal checks, problems with popups containg the character ’ and introduces support in domTT for IE8.

Also the regex used for finding hovers has been changed, which leads to a minor incomatibility with the current scheme used by conditional replacement.

Please read the **UPGRADE **file contained in the archive.

Here I found something to change the default label width for the whole document (note that I changed ’lyxlist’ to ’labeling’):

%adjust the labelwidth in the LyXlist environment
\newlength\extrawidth
\setlength\extrawidth{1eM} % default value

\renewenvironment{labeling}[1]
{\begin{list}{}
{\settowidth{\labelwidth}{#1}
\addtolength{\labelwidth}{\extrawidth}
\setlength{\leftmargin}{\labelwidth}
\addtolength{\leftmargin}{\labelsep}
\renewcommand{\makelabel}[1]{##1\hfil}}}
{\end{list}}