Image
EAN-139781146818551   EAN-13 barcode 9781146818551
Product NameAnnual Report. 1861-70, 72-1925, 30, 35, 38
CategoryBook / Magazine / Publication
Short DescriptionPaperback
Amazon.comA Buy on Amazon ~ 1146818556
SKU8941442
Price New20.42 US Dollars    (curriencies)
Price Used25.90 US Dollars    (curriencies)
Width0.86 inches    (convert)
Height9.69 inches    (convert)
Length7.44 inches    (convert)
Weight26.56 ounces    (convert)
Page Count424
BindingPaperback
Published03/07/2010
Long DescriptionThis is a reproduction of a book published before 1923. This book may have occasional imperfections such as missing or blurred pages, poor pictures, errant marks, etc. that were either part of the original artifact, or were introduced by the scanning process. We believe this work is culturally important, and despite the imperfections, have elected to bring it back into print as part of our continuing commitment to the preservation of printed works worldwide. We appreciate your understanding of the imperfections in the preservation process, and hope you enjoy this valuable book.
Created11-16-2012 7:24:50am
Modified04-30-2015 10:22:46am
MD54ec80707351bf5d5be6795abbceb60cc
SHA256efc532250cbb38d6a6acf26f7e5f3173c72263c7d9ceb467c0361852305d7fa9
Search Googleby EAN or by Title
Query Time0.0048668

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.


Close

Search

Close

Share