Day 5 on Google Earth

I really am a first order geek.

I recently wrote a lengthy account of my “Big September Gig,” in which I spent six days flying around northeastern Arizona with a team of 15 or so Russian photographers. You can read the first part of the story here.

On Day 5, I flew from Monument Valley to Shiprock Airport to Farmington Airport, by way of the San Juan River. What I didn’t mention in my account of that flight is that I had my GPS on and running, creating a track log of the trip. (Geek alert!)

Today, I was reading messages in an aerial photography forum I follow. One of the members, in an answer to another member, mentioned a Mac OS program called GPSPhotoLinker, which can link photographs to GPS data. I figured I’d pull the data off the GPS and record the coordinates of a photo location in the photo’s EXIF tags.

GPSPhotoLinkerI sucked the data off the GPS in Mac OS with a one-trick pony program called LoadMyTracks, which saves in both the GPX format I needed for GPSPhotoLinker and KML (Google Earth) format. I brought the file into TextWrangler, my text editor of choice, and deleted all the unnecessary data to trim down the file. Then I loaded it into GPSPhotoLinker, pointed the software to a folder containing the 18 or so photos I’d taken during the flight, and sat back to watch the results.

Disappointment. The clock on the damn camera was wrong. Since the software uses time to match coordinates with photos, there were no matches. I have to reset the clock on the camera — preferably with my computer so the time is right — and try again on another trip. But this gives me a geeky project to work on. (As if I needed another one.) When I get it all working smoothly, you’ll probably find an article about it here.

Google EarthAnyway, there is a side benefit to this. I also ran the KML version of the file though Google Earth. If you haven’t wasted time with Google Earth, you’re missing out on a great time-sucking experience. Without going into a full blown description or review, I’ll just say that you can take a GPS track, like the one from my trip, and open it in Google Earth. You can then do a “tour” that follows the track just like you’re flying along with me (but at least 3000 feet higher). If you’ve got nothing better to do, give it a try.

I Don’t Like Being Seriously Dugg

The activity finally winds down — I think.

In yesterday’s post, “Getting Seriously Dugg,” I reported the history of a blog post that rose quickly to stardom in the world of Digg users. But that report was done early in the day, before the shit hit the fan (so to speak).

The Heat is On

The Digg count continued to rise throughout the day. And the hits kept coming. All morning long, there were at least 100 visitors online at my site at once. This is not normal here. And it was rather frightening. I kept expecting something to break.

But it wasn’t just the popular Digg post that was getting hits. It was the post about getting Dugg, too. Soon, it had more hits than the dugg post — even though it wasn’t dug by anyone at all. I’m still trying to figure that one out.

Things came to a head at 11:15 AM when I got an e-mail message from my ISP:

Our Hosting Operations Admins have alerted us to an issue with your hosting account. The account has overutilized resources within the shared environment. As a result, the account has been moved to an isolated server for Terms of Service violators. You have 30 days to research and resolve this issue. After this time, the account will be evaluated again. If the issue is resolved, the account will be migrated back to the shared environment. If it persists, you will need to move to a full Dedicated server.

I got on the phone immediately and called my ISP. To my knowledge, I hadn’t violated any terms of service by getting hits. My plan allows 2,000 GB of bandwidth per month. The billing month starts on the third — that day. So far, in all the years I’ve hosted there, I’ve never exceeded 6% of my monthly allowance. Just because I was getting 30 times the usual number of hits I get in a day, it was still not much more than I’d get in a total month. So there was no way I’d even come close to 10% of the monthly allowance — let alone exceed it.

The guy who answered the phone was extremely polite but equally clueless. He had to talk to Advanced Hosting. He couldn’t let me talk to them. They gave him a song and dance about too many domain names pointing to the same site. He attempted to hand the same thing to me. I told him that that shouldn’t matter since none of those domain names were advertised anywhere. Besides, there were only about a dozen of them pointing to one site and maybe 15 pointing to another. I wasn’t aware of any limitation.

“I’ve been dugg,” I told him. When I got no answer, I asked, “Do you know what that means?”

“No,” he said.

I explained that it meant that one of my blog’s posts had become very popular and that people were flocking to my site to read it. I told him this was a temporary thing and that it should be back to normal by the end of the day. I hoped.

He told me that if I continued to get so many hits to my site, I’d have to get a dedicated server. I told him I’d evaluate after I’d seen my stats for the day. (My account is updated daily in the middle of the night.)

We hung up.

A Brief Intermission

I went flying. I took a couple from Virginia on an hour-long helicopter tour in the Wickenburg area. I showed them mine sites and canyons from the air. We saw a lot of cows, too. Afterward, I goofed off at the airport, chatting with two jet pilots who’d come in and were waiting for passengers. Then I went shopping for dinner. I got home and had a snack. Then I looked at Digg. It was 4 PM.

What Happened in Five Hours

The post that had started it all now had more than 1,200 diggs. It had been viewed almost 30,000 times. The post about that post, which hadn’t been dugg at all, had been viewed more than 40,000 times.

But thankfully, there were only 33 people online. So the flood had begun to subside.

On the Digg Technology page, my dugg post was listed near the bottom, under newly popular. (Ironically, on the same page, near the top, was a post about how Digg was losing popularity. That had more than 1,200 diggs, too.)

The Morning After

It’s the next day. I can now look back objectively on my blog’s day with a Digg Top 10 Tech post by studying some of the stats for the day and how the differ from other days.

My ISP reports that for the first day of my billing period — yesterday — I used up .55% (that’s just over half a percent, folks) of my monthly bandwidth. That means that if every day was like yesterday, I’d still come in at less than 20% allowable bandwidth. So I don’t know what “terms of service violation” they were whining about.

W3Counter, which I use to track page hits and visits, says I got just over 27,000 page hits yesterday. Look at the chart below; it makes my site look flat-line dead before yesterday. Honestly — it wasn’t that dead.

Hits

Today’s hits are about 3 times a normal day. Nice, but I’m willing to bet it drops down to normal within the next few days.

W3Counter also sent me an e-mail message warning me that their free service doesn’t cover sites that get more than 5,000 hits a day.They say I need to upgrade to a pro account for $4.95/month. We’ll see how long before they disable my current account — I’m not paying them to tell me how many hits I get when I can easily set up some stat software with a free WordPress plugin. (ShortStats, which we wrote about in our WordPress book, comes to mind.)

(I have not been able to reconcile page hits as reported by W3Counter with article reads as reported by a WordPress plugin. I have a sneaking suspicion that the WordPress plugin counts bots.)

Digg, as a source of hits, kicked Google out of the top spot on my site. Google used to account for 54% of my visitors. Now, for the 14-day period tracked by W3Counter, Digg is the big source. Google doesn’t even make the list any more, with all the different Digg URLs people used to find my site. So my sources stat is completely skewed and pretty much useless for the next 13 days. And 93% of the hits in the past 14 days have been to the 18-year-old mouse story.

Meanwhile, WP-UserOnline reports that yesterday saw the most users online at once on this site: 375. I don’t think this site will ever see that many concurrent users again.

My RSS feed subscriptions have more than doubled. That’s great. (If you’re a new subscriber, thanks for tuning in. And don’t worry — I don’t write about Digg every day.) It’ll be interesting to see if that number continues to climb or if I manage to scare all the new folks off by failing to provide more Diggable content on a daily basis.

My Google AdSense revenue for yesterday was right in line with an average high day. When you consider that I got about 20 times my normal number of page hits yesterday, you might think that I’d get 20 times the revenue. I didn’t. Obviously, Digg users don’t click Google ads.

The last I checked, the 18-year-old mouse story got just over 1,357 Diggs. I think that I actually encouraged the extra Diggs by placing the Digg icon at the top of the post. I’ve since taken it away from all posts.

I’ve realized that I don’t want to be seriously Dugg. Other than the surge in new RSS subscribers, there really isn’t any benefit to it.

What do you think?

Have you been slammed by being dugg? How did it affect your hosting account or other services? Use the Comments link or form to let the rest of us know.

Bridge Over Deception Pass

An example of geometry in construction.

We finished up our recent Alaska vacation with a few days in the Seattle area, visiting Mike’s cousin Rick. Rick took us on an overnight trip out to the islands northwest of Seattle. Although we initially got on the wrong ferry (and wound up on the wrong island) we eventually made it to our destination on Whidbey Island.

Along the way, we stopped at Deception Pass. This is a narrow straight of water with an extremely fast current during tide movements. According to Wikipedia, which has separate entries on Deception Pass and the Deception Pass Bridge:

In the spring of 1792, Joseph Whidbey, master of the HMS Discovery and Captain Vancouver’s chief navigator, sailed through the narrow passage that is now called Deception Pass and proved that it was not really a small bay as charted by the Spaniards (hence the name “Deception”), but a deep and turbulent channel that connects the Strait of Juan de Fuca with the Saratoga Passage, which separates the mainland from what they believed was a peninsula (actually Fidalgo Island and Whidbey Island).

Deception Pass BridgeThe Deception Pass Bridge crosses over this strait, about 180 feet above the water (depending on the tide). There are actually two spans to the bridge with a small uninhabited island between them. There’s limited parking on both ends of the bridge with plenty of places to stop and take in the view.

Deception Pass BridgeThe bridge includes a 3-foot wide sidewalk on each side, which is definitely not recommended for those who are afraid of heights. We walked across on one side and back on the other. To prevent people from crossing the relatively busy roadway, a flight of stairs leads to a pathway under the bridge on either bank. That’s where I took this photo. I liked the symmetry of the construction and the fact that I could frame the photo in such a way that the pattern seemed to go on forever. This is a theme I try to capture in my photos when I can: infinity.

There were kayakers down on the water, braving the strong current. And lots of people walking around in the vicinity of the bridge. If you’re ever in the area, sop by and check it out.

Buy on RedBubbleThe full-frame version of this photo is available for sale as cards and prints at RedBubble.com.

Google/Blogger Complies with My DMCA Complaint

An update to my recent copyright infringement article.

Last week, I reported finding a pirate Web site that was offering, among other things, one of my books for free download. The site was hosted on the blogspot domain name, which is Blogger’s. Blogger is owned by Google. I sprung into action and began issuing DMCA notices.

Yesterday, I got the following e-mail from Blogger:

Hello Maria,

In accordance with the DMCA, we have completed processing your
infringement complaint and the content in question no longer appears on
the following URL(s):

[omitted].blogspot.com/2007/06/putting-your-small-business-on-web-by.html

Please let us know if we can assist you further.

Sincerely,
The Blogger Team

I followed the link and, sure enough, the page was missing. I then went to the home page of the site. The site was still up and running and still offering pirated ebooks and software.

I replied to “the Blogger Team”:

Yes, you can assist me further. You can take down the entire site at [omitted].blogspot.com. It’s a pirate site that offers illegal access to eBooks and software.

So far, I haven’t gotten any response.

My efforts to get the book file off the file hosting servers were successful. All three hosts removed the file.

eBook Copyright Infringement

An author’s worst nightmare.

I use Google Alerts to get a daily list of posts that match keywords I provide. Among the search phrases I have alerts for is “Maria Langer.” Yes, I’m trying to see if anyone else in the blogosphere is writing about me.

Just back from a 2-week vacation, I started going through the alerts. There usually aren’t many for me, so I did those first. And I came across something that made my blood boil: a blog that includes free download links to copyrighted eBooks. And, as you might imagine, one of them was mine.

My book is being distributed as a Compiled HTML Help File (.chm) file, complete with hypertext TOC and all screenshots. Other books are being distributed as PDFs. Where did these books come from? My publisher has not responded to that question. Could it be that publishers are releasing books in unprotected, easily shared formats? Could they be that stupid?

I immediately went into defense mode. First, I confirmed that the download links gave me a free copy of the book in question. It did. Then, I called and e-mailed my editor to tell her about the problem, providing her with a link to the blog. Then I composed a DMCA notice to Google and faxed it to them and my editor. Next, I contacted some of the other publishers whose books appeared on the page. Finally, I went to the sites hosting the ebook files and reported the file links as abuse.

All this ate up about 2 hours of my day — on a day set aside to catch up after vacation.

Now I’m waiting to see what comes of my actions. At the very least, I want the entire blog and files removed. I think that may happen quickly.

But what I really want is for the people who posted the links to be arrested and tried for copyright infringement. I don’t care if they get off — the legal fees alone for their defense should teach them a lesson. But I don’t think this will happen.

The thing that bothers me most is this: I discovered this one pirate blog. How many others are out there that I haven’t discovered?

And how many authors are having their work ripped off?

Update: 2:55 PM

I discovered soon after writing this post that the blog in question is a pirate blog that’s also got a lot of limited interest software available for download. One of the makers of this pirated software is AT&T. I called their sales staff and told them about their software being listed for free download in an effort to get AT&T involved. They have a lot of clout (as you could imagine). The sales guy said AT&T is very interested in this kind of thing.

One of the sites that was hosting my book file has deleted the file at my request. I’m hoping the other two do so quickly, also.