According to Bazaar docs:

“When you push a branch to a remote system, a working tree will not be created. If one is already present the files will not be updated. The branch information will be updated and the working tree will be marked as out-of-date. Updating a working tree remotely is difficult, as there may be uncommitted changes or the update may cause content conflicts that are difficult to deal with remotely.”

The push-and-update plugin solves the problem by carrying out the push as normal but then SSHing into the account and carrying out the ‘bzr update’ command to update the working tree as well. The only problem with running this on Windows is that the plugin assumes you have the ssh command available. So if you’d like to use putty’s plink instead, open the push_and_update.py file and change this line:

cmd = ['ssh', user+host+port, remote_bzr, 'update', path]

to

cmd = ['c:\path\to\plink.exe', user+host+port, remote_bzr, 'update', path]

To avoid editing the file completely, you can download and rename plink.exe to ssh.exe and place it in one of the directories listed in your system PATH variable. (Note: the Bazaar client may throw errors if you leave plink.exe in a directory listed in your PATH variable - at least it did for me - so make sure it’s renamed if you experience a similar problem.)

This appears to be a known bug.

“It goes roughly like this: 9/11 was horrific, its driving ideology was totalitarian, the totalitarians were Muslims, all Muslims follow a book they believe to be the immutable word of God, I don’t believe that, therefore all Muslims are idiots, and basically bastards. Idiot bastards moping around the Middle East in a paranoid funk just cos they lost their empire, and what a rubbish empire it was, too, by the way. Now, what is your balanced view of these primitive wife-beating idiotic bastards?”

Chris Morris, The absurd world of Martin Amis, 25 November 2007

The idea is to make it easy to:

• find libraries in London (for now) and the rest of the UK (later)
• find books in these libraries without dealing with difficult interfaces

Finding Libraries

I’ve started putting together a database of London libraries and their coordinates. You can see locations of almost 400 London libraries on librarylookup.org.uk.

You can also find libraries nearest to you by entering your postcode at the end of the URL — it can be the first part (outward code), but using a full postcode will give you more accurate results. E.g. http://www.librarylookup.org.uk/W6 0QL will show you the libraries closest to the Lyric Theatre in Hammersmith.

I still need to work on the interface. It’s using Google Maps at the moment, but I might consider alternatives. You won’t see much information about the libraries at the moment, but I’m going to include the full address and website address of each library.

Finding Books

The plan is to use existing book sites as the Web interface for book searches. I’m working on a Greasemonkey script that will, when complete, run on a number of book sites and the librarylookup website mentioned above. On the librarylookup website, the user selects his/her favourite/nearest libraries and the Greasemonkey script records it. Those preferences will then be used when browsing Amazon to query the library’s (or libraries) online catalog for the book being viewed. You will then be notified if the book is available/unavailable.

Library Lookup Web Service

So far I’ve written code that can check Hammersmith and Fulham, Bromley and Norfolk libraries. I plan on implementing the lookup process in Javascript (to lessen the load on the server) when the project is ready, but for the time being the Greasemonkey script sends its request to a PHP script that returns JSON formatted results:

Supported libraries:
librarylookup.org.uk/service/libraries/
ISBN lookup:
librarylookup.org.uk/service/libraries/hammersmith/0745324827
ISBN lookup:
librarylookup.org.uk/service/libraries/norfolk/0552773328

The code also uses the xISBN Web service when a library has no record of the requested ISBN. The xISBN service returns ISBNs associated with different editions of the same book, so if a library doesn’t have the exact one we’re looking at on Amazon, we’ll still be told if there are other editions that it does have.

Screencast: The Script in Action

Credits

These sites/articles helped a lot:

• Jon Udell: The LibraryLookup Project
• Using Prototype and Scriptaculous with Greasemonkey
• xISBN (Web service)
• LondonLibraries.org

• Following configuration now works: ordering set to ASC and fill_last_page enabled.

Download Paged Comments plugin for WordPress.

30 minute video of the 1996 interview between Andrew Marr and Noam Chomsky. Still interesting and relevant. Read transcript and the Media Lens review: Where Egos Dare.

You can download a better version from ChomskyTorrents.org.

More and more sites are displaying Google (AdSense) or Yahoo (YPN) ads. I thought I’d post up 4 simple ways you can get rid of these ads, and, if like me, you’d still like to know which sites use them but don’t really want to see the ads, there’s even a solution to replace them with boxes. Solutions 1-3 require Firefox—I’ve only tested with Firefox 2.0. Solution 4 should work with any browser on a Windows system.

Note: these solutions are targeted at Google and Yahoo ad services, to remove other ads you can use Adblock Plus along with one of the many filter sets available. Solutions 1, 2 and 4 only remove the ads, solution 3 also replaces them with boxes where the ads would have appeared.

1. AdBlock Plus extension

Install Adblock Plus and add the following two filters:

http://ypn-js.overture.com/*

and

http://pagead2.googlesyndication.com/*

If you’re already running AdBlock Plus, you can subscribe to my Google and Yahoo ad remover filter set, I’ll be adding to it soon.

2. CSS solution—no additional addons required

Edit userContent.css (use ChromEdit Plus or read Editing Configuration Files if you need help) and add the following two rules:

/*
 * Remove Google ads
 */
iframe[name='google_ads_frame'],
a[href^='http://pagead2.googlesyndication.com']
{ display: none ! important; }

/*
 * Remove Yahoo ads
 */
iframe[src^='http://ypn-js.overture.com']
{ display: none ! important; }

Save and restart Firefox.

3. Replacing Ads with Greasemonkey

Install Greasemonkey and then my Replace Google/Yahoo Ads script.

Before and after screenshot:

4. Windows hosts

This is based on Tech Support Alert’s in-depth guide to Removing Google Ads Using the Windows Hosts File. Read that if you’re unfamiliar with the Windows Hosts file.

Locate the hosts file. It’ll be found in one of these locations, depending on your version of Windows:

Windows XP = C:\WINDOWS\SYSTEM32\DRIVERS\ETC
Windows 2K/NT = C:\WINNT\SYSTEM32\DRIVERS\ETC
Windows 98/ME = C:\WINDOWS

Open it with a plain-text editor, e.g. Notepad, and add the following two lines:

127.0.0.1    pagead2.googlesyndication.com
127.0.0.1    ypn-js.overture.com

Any feedback appreciated.

Ads on Google and Yahoo websites

The methods above will not block ads appearing on Google or Yahoo’s own websites, e.g. Gmail or Yahoo Mail, as most of those ads are fetched server-side and not through the easy-to-use HTML snippets most webmasters receive when signing up to AdSense/YPN. You will however find Firefox extensions and Greasemonkey scripts targeting those sites specifically. For example, the excellent CustomizeGoogle extension removes ads from Google search results, GMail, and more.

I’ve been listening to it a lot and it just gets better and better. If you’re new to White Town, listen to tracks from the new album, read a review, an interview with Jyoti, then buy it! It’s available to buy on CD Baby and iTunes.

See Bzangy Groink for more…

Changes include:

• Easier to install—no file editing if you’re happy with the default settings.
• Updated K2 template included—Paged Comments now works with the new K2 theme.
• Bug fix: Query strings and comment page URLs now play well together. Thanks Mark.
• Bug fix: Invalid permalink URL with default_page issue resolved. Thanks Mark.

Let me know if you come across any problems. More updates on the plugin coming soon.