EAN-130016351078087   EAN-13 barcode 0016351078087
UPC-A016351078087   UPC-A barcode 016351078087
Product NameTexas Worried Blues
CategoryElectronics / Photography: A/V Media: Music
Short DescriptionHeight:4.92 inches / Length:5.59 inches / Weight:0.21 pounds / Width:0.39 inches
Amazon.comA Buy on Amazon ~ B000000G8B
Price New11.34 US Dollars    (curriencies)
Price Used10.00 US Dollars    (curriencies)
Long DescriptionHenry "Ragtime Texas" Thomas (1876-?) was a railroading hobo from the Lone Star State whose style and repertoire were obsolete long before the first of his two recording sessions in 1927. His last recorded song, "Don't Leave Me Here," a plaintive version of his "Don't Ease Me In," was his bluesy take on the popular early 20th-century standard "Alabama Bound" and is one of many gems in this unique collection of extra-Delta country blues, "rags," and medicine show or vaudeville tunes. With Thomas punctuating most of his songs by tooting on pre-harmonica quills, or panpipes, these colorful numbers offer a glimpse into a vanished world. After recording such delights as "Railroadin' Some," "Jonah in the Wilderness," "Red River Blues," and "Honey, Won't You Allow Me One More Chance?," the mysterious minstrel disappeared--unless that really was Thomas on the corner of Crawford and Capitol during Houston's winter of 1949. --Alan Greenberg
Similar Items0799582100528: Complete Recordings 1928-30
0714298500424: Furry's Blues 1927-1929
Created03-12-2013 9:46:47am
Modified04-28-2020 3:01:34pm
Search Googleby EAN or by Title
Query Time0.0149031

Article of interest

We are not hosted at GoDaddy, but we are registered there and have our DSN settings stored with them. So when Anonymous attacked GoDaddy, we were impacted too.

It is very sad that hackers don't think about all of the people that will be impacted by their actions. Even though we were not attacked directly, we were impacted and most of our users were also impacted.

Our site was up and running the entire time and because many DNS servers cache the address to our site, we had a steady flow of traffic during the attack. But the number of visiters to the site was clearly lower than normal. We had a significant drop in visitors and even after things were fixed by GoDaddy things weren't quite normal again until quite late in the evening.

If you or your applications were impacted by this attack we are deeply sorry but there was nothing that we could do to prevent or recover from this. Just like you, all we could do is wait for GoDaddy to deal with the situation.

Here are some news links you can read relating to the attack:

Update 9/13/2012 - It appears that this may not have been an attack after all. GoDaddy is saying that this was not an attack but a configuration error that cascaded through their routers taking their services off line for about six hours. Be it an attack or an accidental configuration issue makes no real difference to the end users that couldn't gain access to the web sites hosted on or registered with GoDaddy.

From GoDaddy:

Although this was all very annoying, no personal information seems to have been accessed such as passwords, credit card numbers, addresses, phone numbers or alike. Personally, being a technical person, I feel GoDaddy handled this situation quite well. I am not happy that it happened or that our users were unable to get to the site. But the tech team at GoDaddy did a very good job at correcting the problems.