So the next question is, what now?
For the major labels, it's over. It's fucking over. You're going to burn to the fucking ground, and we're all going to dance around the fire. And it's your own fault. Surely, somewhere deep inside, you had to know this day was coming, right? Your very industry is founded on an unfair business model of owning art you didn't create in exchange for the services you provide. It's rigged so that you win every time - even if the artist does well, you do ten times better. It was able to exist because you controlled the distribution, but now that's back in the hands of the people, and you let the ball drop when you could have evolved.
IT'S a little known fact, but if you type 'google' into Google: you break the Internet.
HOWEVER, it's very important that you don't do this.
AT least not until I've finished downloading it to my hard drive.
THANK you for your pleasant co-operation.

-----BEGIN PGP MESSAGE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: firegpg.tuxfamily.org
hQIOA1qc/9sTj5nSEAf/bE+r4zqhDAjDCwa0yuBmCRgYrf/q3psKSTXfKPIsLbbz
o17VbK/fv57VdjM3H+JmxGVdzveUYC/+2uJXTwX0TMLd9LbDdY83/qcjRE0qLBQK
84toFwourpfwyDJiVAn8vP09XVx6P3hOAiOj9aMnezzMTw3/uXbfunjRTtE02a0z
LlJRD9crmEX5ujkVzycDY2DMeE3LGAyxXQ4czVWjoCMyPqwkk0uN3b7bUfSPRFCx
sTH9gMeJ7RpfwBVA/50GVHMPhUSAJl5MRV5cEC/8boxeVHKiFSo1fcFJLS6Mm4av
Tx/AMDokjs88TzJWc/bVdoojuu9EAg4uH0X7/Atdagf+IT4WNSQ5pvQ07QPLyBRn
v9nANd8Ckit0tt4WkQKHePupwW0pYImcHAsts8BiujTifYoR5eyBDKjiRnwuaShE
JlfRaY68pIcUVkYCWZ+gaq3YgkAOkHK6mDIxWwQkVBUDeP9Xd+dWpRb/KWRJzxmU
52os72fiQ+oqKiauy6qOHAsI1AAJLdBnvFvQgiPFsqJST6pc39EdnBlfMIt0BHXD
3dJZOR45I20OTi92+Y5toW6KH/cQHoiqQxp4dquaUDYJo/Gzj4FvSr1VE+Ou5Q2Y
p11h0yKYIGSbbvCTr0IQ2lf/6WgtdXxX3RAErMoiwV75GEIYMlJEAUmq63ZIMuBO
z9LA1gGfLRjGq6VwlQh9DFwtGPHZKpOVAo8YrAIQH7K0IYQIxPsOAFSYSzqXvyA0
dyDFe6nE6vuXn5qZ33AI85y4P7i2RkpW73NEUZRDdkOoRGDGDfECNus51MJsvFuc
N9APLDQjeJqj721Uw6gGxiWe1Pyf/qE2BF/pOxHYXl9gPNnoSZ/QbvtrXOzzDZAu
WcbU5Nurim69HyPtsRgw7XDDodcWvv79TPMTGAzUdCZ/qq/7xVDtnky/+xFA01i4
nx7hpcve2MVk1dGZwJ555eajueGZ3cvooRXVA7wgoyWnjgB6z74xjhnAAQZgVVsX
2HVrT4nLfHlCKP83gEz9Dl/Sh2BwLpylTRVucrjl31lx5adsZFTsu+pWY/lgXRKd
ibIqPo1qjKr2ec0hR2uufOLker0xbVRtf5Tje6ftfYVMjDmLImfijMCJkHfwoYOP
hTvgVyVSGpAalPnnkVEC4FQtHg+SL+y4Km2x2NodNABTr6Sw/X17IRvB1BJ2MK4I
5hPfDge/nWe9GU3Y5xtm/9VgprbzqDZ/E9A=
=1GNf
-----END PGP MESSAGE-----
Oh, and Gmail Notifier is great for switching between multiple accounts.
Can't use global $_ in "my" at ./database_attractions_files.pl line 191, near "my $_ "
Execution of ./database_attractions_files.pl aborted due to compilation errors (#1)
(F) You tried to declare a magical variable as a lexical variable. This
is not allowed, because the magic can be tied to only one location
(namely the global variable) and it would be incredibly confusing to
have variables in your program that looked like magical variables but
weren't.



Introduction
A patch describes a change to the tree. It could be either a primitive patch (such as a file add/remove, a directory rename, or a hunk replacement within a file), or a composite patch describing many such changes. Every patch type must satisfy the conditions described in this appendix. The theory of patches is independent of the data which the patches manipulate, which is what makes it both powerful and useful, as it provides a framework upon which one can build a revision control system in a sane manner.
Although in a sense, the defining property of any patch is that it can be applied to a certain tree, and thus make a certain change, this change does not wholly define the patch. A patch is defined by a representation, together with a set of rules for how it behaves (which it has in common with its patch type). The representation of a patch defines what change that particular patch makes, and must be defined in the context of a specific tree. The theory of patches is a theory of the many ways one can change the representation of a patch to place it in the context of a different tree. The patch itself is not changed, since it describes a single change, which must be the same regardless of its representation.
So how does one define a tree, or the context of a patch? The simplest way to define a tree is as the result of a series of patches applied to the empty tree. Thus, the context of a patch consists of the set of patches that precede it."
continued...