I took some time to check various state corporation databases and actually managed to find who Nabu Press is. They are … BiblioBazaar / BiblioLife, a company started by former BookSurge partners after they sold their POD company to Amazon. It is no surprise that they print their POD books through Amazon.

How do I know this – take a look at the SC filing for Nabu Press LLC. The registered agent is for Nabu is:

ERIKA V. HARRISON
18-A CAROLINA
CHARLESTON, SC 29403

A search of the same site, reveals that only two other corporations have the same registered agent – BIBLIOBAZAAR II, LLC and BIBLIOLABS, LLC. BiblioLabs is part of BiblioBazaar as stated on their website.

So the final word is that Nabu Press is actually part of BiblioBazaar. HOWEVER, why did they NOT mention this on their website, and especially in the list of their imprints here? Could it be for legal reasons?

This standard covers the way ISPs report spam and other abuse messages to each other and is currently in used by companies like AOL, Yahoo, etc. Becoming an official IETF standard is a big deal since it will finally put into final shape what this standard looks like.

Congratulations to the MARF co-chairs for leading the process and all of the participants.

My document repository will be updated some time tonight with the new information as well as all of the drafts.

So he called McAfee’s customer service and guess what? They can fix the problem for a low fee of $90!!!!! They did not tell him to go online and lookup the instructions, or send him to Towson’s helpdesk since it is a corporate version – instead they are looking to make a quick buck because of a problem they themselves have caused.

This is shameful and they should be investigated.

UPDATE: McAfee posted that they will reimburse their customers for “reasonable expenses” incurred in fixing their computers. No details just yet.

The first draft as written by me in the beginning of 2005 after I left ASRG. The draft bounced back and forth over the last few years among an informal group of people at a mailing list maintained by Dave Crocker at MIPA. A large number of the list members were also members of MAAWG (of which I never formally participated but had the pleasure of speaking at their first conference in DC).

As I ran out of time, others have taken over the editing of the draft until the current editor, Murray Kucheraway took over. He has been very helpful in pushing for IETF standardization. A funny thing happened along the way as well – big ISPs started using the format – first AOL, then Yahoo and Microsoft.

This year, the IETF finally chartered a new working group which will now hopefully standardize this format and set it in a fixed version, so it can be used even more widely. Along with this, there is possibility of expanding different parts or uses of it as well.

A word of thanks goes out to all of the people that made this happen.

The system has reached the maxium size allowed for the system part of the registry. Additional storage requests will be ignored.

Once that happens, all kinds of weird behavior starts to occur beginning with the fact that USB devices no longer work. The cause of this is due to the fact that every time a USB device is inserted, it creates registry entries. Apparently, with storage devices like Flash drives it is even worth, since there may be multiple devices – one for the drive, one for the actual physical key, and possibly a bridge as well. While Windows XP is not supposed to have such limits, it does occur, especially on systems using the “3GB” switch for bootup.

The solution – download the VxScrub utility from Veritas/Symantec which will clean out your registry from any old entries.

The best one so far that I found is BitDefender’s RescueCD which can be downloaded here. A nice feature is that if you plugin a network cable, the CD will download the latest virus definitions before scanning.

You can check this Russian site for full instructions and tools, or use this tool.

For the technical among you – there seems to be an issue with the statically linked package for Ubuntu. The dynamic package for Debian seems to work better.

A groundhog has been attacking our garden for the past few weeks. After a call to the exterminator he has been finally caught. You can see it in the picture waiting to be transported out of the city.

It seems that while officially Google Base supports Unicode and utf-8 encoding in XML feeds as stated here. they don’t support it fully. Apparently it seems that instead of taking plain UTF-8 text, Google Base requires it to be encoded at Unicode entities like &xxxx; where xxxx is the Unicode codepoint. This was originally found by this blogger.

The solution in XSLT at least is to use us-ascii encoding which forces entity creation. In Perl you can probably use Encode.pm or iconv.

Many thanks to Michael Fourman of the Mac Tips blog for this.

1and1 (fails running PHP 4, but works with PHP 5. Add the line: AddType x-mapp-php5 .php to the file .htaccess in your main wordpress directory to enable PHP 5. This also appears to not only affect Core updates but some Plugin updates as well.)

(Something about many eyeballs and bugs rings a bill here)

A creepy crawler recently sighted. Otherwise known as the house centipede or Scutigera coleoptrata.

1. Transform PlayList.com’s ASX playlist into Podcast RSS via this link:

http://www.w3.org/2005/08/online_xslt/xslt?xslfile=http://www.shaftek.org/code/asx2rss/asx2rss.xsl&xmlfile=http://www.playlist.com/playlist/XXXXXXXX/asx

Where XXXXXXX is the Playlist.com user ID.

2. Use the resulting postcast with your podcatcher, or mobile phone. Or even cooler, use PodLinez.com or FoneShow to listen over a regular phone.

DISCLAIMER: I am not responsible for any illegal behavior that results. You should keep in mind that PlayList.com may be indexing illegal music which you will end up downloading via the podcast RSS. It is your responsiblity to check.

#!/usr/bin/perl

use Net::Amazon::S3;

my $s3 = Net::Amazon::S3->new(
{   aws_access_key_id     => 'ACCESS_ID',
aws_secret_access_key => 'ACCESS_KEY',
retry                 => 1,
}
);

my $bucket = $s3->bucket("BUCKET") or die $s3->err . ": " . $s3->errstr;
my $response = $bucket->list or die $s3->err . ": " . $s3->errstr;

foreach my $key (@{$response->{keys}}) {
my $key_name = $key->{key};
print "Deleting '$key_name'\n";
$bucket->delete_key($key_name) or die $s3->err . ": " . $s3->errstr;
}
exit;