This is unbelievably stupid of Paypal. I just got this email from them:
vinyl tap records would like you to use PayPal - the safer, easier way to pay and get paid online.
To send vinyl tap records your payment and see the details of this invoice, copy and paste this link into your web browser:
So much for “never click a URL in email”. Even worse, if you log in
separately, the request is not visible anywhere. Morons.
I got some NatWest phishing spam the other day and was amused to notice
<title>NatWest - Security Information</title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
<link rel="stylesheet" type="text/css" href="http://www.natwest.com/microsites/global/phishing_demo/includes/css/generic.css" media="all" />
<a href="http://www.natwest.com/"><img src="http://www.natwest.com/microsites/global/phishing_demo/images/h_logo.gif" alt="NatWest - Load home page" /></a>
Enterprising of them to actually uses NatWest’s explanation of phishing
to … phish.
To quote 123-reg customer support:
> When will you be supporting AAAA records?
There are no current plans to implement this but notifications will be
sent out if this takes place.
Late last year, I was forced to find a new host for
movementarian.org, as my previous hosting
provider (Blue Room Hosting, who were really great) were shutting down.
I went with VPS247, as they were local to
Manchester and seemed reasonable.
Unfortunately my experience has been terrible. They’ve failed to keep
the machines on the net, regularly causing ssh sessions to die. The
dmesg is full of warnings about the block drivers failing to write for
more than two minutes: evidently the SAN setup they have is totally
My VM went down for a significant amount of time and support were very
slow to respond. During the total outage, there were no status updates,
and no response on the support tickets or the forums. The penultimate
straw was when my filesystem was massively corrupted. Even though my VM
is hardly critical, I can’t be doing with unreliability like this,
especially when they’re not reachable when problems occur.
My final straw, though, was when I discovered they’d deleted all the
negative comments from the Client Comments section of their
That’s really, really, not on.
I’m now with linode and happy (so far).
I’ve started using pbranch
hg more seriously. It works nicely but is a little rough
around the edges, in particular:
No hg qpop/push equivalent
I really miss this. I find myself constantly doing
hg pgraph to figure
out where I am and then typing the patch above or below.
No way to shelve a patch
With MQ, I can easily guard a patch to temporarily remove it from the
queue. There doesn’t seem to be a simple way to do that with pbranch.
Editing patch messages.
You use peditmessage, but because this modifies the repository, you then
have to always
hg pmerge -all. This pops to the top and causes a bunch
of extra changesets, and it gets annoying quickly. And frustratingly,
these patch messages do *not* appear in the repo history. So your code
reviews of the main repo are just showered in useless merge messages,
instead of the actual commit message you care about.
I don’t know why, but there’s no way to automatically commit a patch as
a single changeset on the root default tip, then close the patch
Inserting and deleting patches is horrible
Yuck - I really
hope this gets easier soon.
Showing the current patch history
A little tip not mentioned on the pbranch site: the way to show the
changelog history of the current patch is to do
hg log -b patchname.
Create the following as
<?xml version="1.0” encoding="UTF-8”?>
Default X.org input configuration is defined in:
Settings here modify or override the default configuration.
See comment in the file above for more information.
To see the currently active hal X.org input configuration
run lshal or hal-device(1m) and search for “input.x11*” keys.
Hal and X must be restarted for changes here to take any effect
<match key="info.capabilities” contains="input.keys”>
and then restart hald and Xorg.
echo ‘gtk-error-bell = 0’ »$HOME/.gtkrc-2.0
Liferea has no keyboard shortcut editor itself, but “Toggle unread
status” demands the wrist-breaking chord action of Control-U. It expects
you to be able to edit the shortcuts via the editable menu feature of
Unfortunately that’s disabled on all modern GNOME installs, and there’s
no UI for re-enabling it. As usual,
gconf-editor to the rescue. The
key you need to change is
After re-starting Liferea, you can then edit via hovering over the menu
item and pressing the combination. Of course, this in itself is buggy:
if it clashes with a menu accelerator (as ‘r’ is), it will perform that
It’s simpler to directly edit the
accels file in your Liferea dot dir.
Browsing the net, you might get the impression that Epson Stylus
All-in-ones are well supported under Linux. Unfortunately this is not
the case. The pipslite driver you have to install is extremely flaky,
and Fedora SELinux doesn’t work properly with it. There’s no “draft”
mode for some bizarre reason; printing is extremely slow and often
randomly cancels half-printed jobs due to USB resets
The scanner doesn’t work at all with the iscan software, despite claims
to the contrary.
Audacity is somewhat of a broken joke these days, so I needed to use
Ardour to record. And that meant setting up JACK. Since JACK insists on
exclusivity, I also needed to route pulseaudio through JACK so I could
use other apps at the same time. Unfortunately, this is a bit of a pig
to figure out. I hacked it as follows:
/etc/pulse/default.pa, you need to add two lines:
In theory now, a restart of pulseaudio should start using JACK for
recording and playback, if jackd is running. However, it tends not to
work very well: you might find PA hanging and you have to kill -9 it.
This isn’t enough of course, now when you log in again, gnome-session
will try to start pulseaudio, but not jackd, so nothing works. It’s far
from the right way, but I edited
is started from a
/etc/xdg/autostart/ script), as follows:
amixer -c 0 sset 'Input Source' 'Line'
nohup jackd -d alsa &
/usr/bin/pulseaudio --start "[email protected]"
Note that I have to set the input source by hand: something in desktop
start up used to do this for me, but now I’m going through JACK it has
to be done by hand.