Three Native American Sites in the Northwest Georgia Mountains
This past Saturday, I visited two Native American sites located in the north GA mountains. I planned to visit a third located nearby, but there was so much to see at the first two, I didn’t have time. It’s remarkable that three sites, located within 50 or so miles of each other, can be so different from each other. New Echota, the capital of the Cherokee Nation from 1828 until the Trail of Tears, is just up the road from Etowah, the site of a busting town from the Mississippian culture (800AD to 1600AD), and both are not far from Fort Mountain, the location of a mysterious wall.
New Echota Printing Office (reconstruction)
New Echota is the latest historically of the three Native American sites. The location of a few Cherokee homesteaders, it rose to prominence in 1828 when it was selected as the capital of the shrinking Cherokee Nation. Years of land grabs and territorial encroachments had eroded the territory greatly. In the hopes of preventing further loss, the Cherokee Nation took steps to “civilize” themselves (essentially, emulate the white man). To take territory from “savages” is one thing, to take it from a modern, sovereign nation is another. The Cherokees established a three-branch government (legislative, executive, judicial), set up a printing press with the syllabary invented by Sequoyah, and built structures to house their governmental bodies comprised of elected officials. Because of intermarriage, many of the Cherokee leaders were of mixed ancestry, and English and Cherokee were widely spoken. The town of New Echota, though, small, was thriving.
Unfortunately, the sovereignty of the territory was critically threatened by the discovery of gold in the North Georgia mountains. White settlers entered Cherokee territory to pan and mine for gold, and the state of Georgia often turned a blind eye to invasions. When rules were set down to “protect” the Cherokee territory, they were often insulting. Cherokees were forbidden from mining gold on their own land and from testifying in any criminal or civil case against a white man.
The ability for the state of Georgia to even make laws governing the Cherokee territory was in question. A missionary, Samuel Worcester, was a great friend to the Cherokee and lived at New Echota. Under Georgia law, as a white man living in Cherokee territory, he was required to obtain a permit to live there. But the Cherokee asserted that, if Worcester were permitted by the Cherokee government at New Echota, no further permission was required. Worcester was arrested for failing to obtain the permit and remained imprisoned for two years while his case travelled all the way to the US Supreme Court, who ruled in favor of Cherokee self-government. Then-president Andrew Jackson was furious with the ruling. Having promised the state of Georgia that all Native Americans would be evicted “eventually,” Jackson decided that the time was now, and a US agent engaged with a few Cherokee leaders to sign the treaty of New Echota, which exchanged the remaining Cherokee territories for new reservation land in Oklahoma. Most Cherokees were furious at the treaty, arguing that the few signers of the treaty did not have legislative authority to speak for the whole Cherokee nation. But Congress ratified the treaty of New Echota despite these objections. The state of Georgia took possession of the remaining Cherokee territories, raffling off the land to Georgia citizens in a series of land lotteries. In 1838, Cherokees were rounded up in various locations, including New Echota, and escorted to the Oklahoma territory. This was the Trail of Tears. An estimated 4,000 Cherokees died during or shortly after the migration.
Today, New Echota is not as busy a place as it once was. Having been reduced to a level field after 1838, it is now a Georgia state historic site. Several important buildings have been reconstructed, and a few have been relocated to New Echota from other places. Reconstructions of the court house / capitol building, printing office, and a middle-class Cherokee farm are highlights, as is the sole remaining structure actually standing in new Echota in 1838 — the house in which missionary Samuel Worchester lived with his family and boarders.
Etowah Mounds
Because the events of New Echota happened in historic times and were recorded by outsiders and the Cherokee themselves, its history is much better understood than Etowah, just a few miles down the road. Etowah was a major town in the Mississippian culture, a loose confederation of tribes that shared certain physical, social, and religious characteristics. Etowah was a town of 1,000 - 4,000 people, built beside the Etowah river. A defensive ditch and high wooden fence protected homes, workshops, food storage, and impressive dwelling and burial mounds, the highest of which is 63 feet tall. Political and religious leaders lived in houses on top of the mounds, with higher-ranking leaders on the higher mounds. A large plaza of hard-packed clay was the site of markets, social gatherings, and sporting activities, such as the ball game. A large population of farmers and fishermen supported warriors, craftsmen, and religious leaders in a complicated, organized society with trade connections stretching for thousands of miles.
DeSoto’s expedition encountered the Etowah population center in 1540 and stayed several days. The Mississippian culture was already in decline prior to contact with white explorers and settlers, but the introduction of European diseases and instruments of war certainly hastened the collapse. By 1600, the Etowah site was abandoned. Over the centuries, some of the smaller mounds were plowed down for farmland. Later owners of the property recognized the importance of the site and prevented the largest mounds from being destroyed (but the owners did plant corn on the top of the mounds and constructed a ramp so that mules could get to the top for plowing). Excavations starting in the 1850’s and continuing through today have unearthed thousands of amazing artifacts, mainly from the burial mounds. Useful tools, like knives and scrapers and pottery, were found along with objects of pure art, including jewelry and statues. In the museum at Etowah are two spectacular, painted marble figures.
Etowah Painted Figures
Archaeologists hypothesize that these figures had a key role in the decline and abandonment of Etowah. They were broken and buried — perhaps a sign of a political or religious revolt, an invasion, or dereliction of culture caused by disease, encroachment, or something else. The real answer may never be known because, unlike New Echota, there is no written record from Etowah.
Wall at Fort Mountain
The third site, Fort Mountain, is the most mysterious. Fort Mountain is a Georgia state park, so named because of a wooden fortification constructed by white settlers. But their fortification is singularly unimpressive compared to the 855-foot stone wall built centuries ago at the crest of the mountain. The wall is only a few feet high today, though at the time of construction it would have been higher. Along its length are shallow pits, which the tourism industry of the early 1900’s called “Indian honeymoon suites.”
Theories on the origin and purpose of the wall abound. Did the Mississippians build it? Did DeSoto’s expedition? This seems unlikely, as DeSoto wasn’t in the area long enough to build such a monumental structure. Was it built by the Welsh prince Madoc, said to have landed in the southeastern United States in the 11th century? There is only scant, circumspect evidence that he arrived in the United States at all, and such a discovery would rewrite early American history. As a fortification, the wall seems odd — why build a wall at the top of a mountain, already a barrier against attack? Perhaps the wall was more symbolic — a boundary between tribes or cultures, or a structure of religious significance.
Exploring these three sites gives three very different pictures of Native American life in northwest Georgia. New Echota speaks of the attempts of the Cherokee to become “civilized” to defend themselves against an uncivil foe. Etowah, a few hundred years older, is evidence of how civilized the Native Americans were, with complicated social structures, long-distance trade routes, and the organizational and technical skills to build monumental architecture. And Fort Mountain’s mysterious wall reinforces how little we know of America’s history even a thousand years ago — our best guesses could be only hints at the true, complex history of the Native Americans.
QuickBooks Pro costs $40 more if you’re using IE
I’ve never really been a browser partisan, but today I found a very good reason to go with Firefox / Chrome over Internet Explorer. When I tried to buy an upgrade to QuickBooks in IE, it cost $40 more than the exact same upgrade when purchased in Firefox.
I am a reluctant user of QuickBooks for my small-business accounts payable and receivable. I’ve been using the 2006 edition because I didn’t need any of the features from the later versions. However, the Online Banking support for QuickBooks 2006 expired yesterday. I went to the Intuit website using Firefox to purchase my upgrade. The price was $119.
However, the Intuit website doesn’t work very well in Firefox. I was having trouble entering my current license code to upgrade. I switched over to IE, thinking that would work better. The website does work better, but the price for the upgrade is $159, $40 higher!
Screenshot showing that QuickBooks Pro 2009 costs $40 more in IE than Firefox
I know that companies engage in price discrimation, but I didn’t think that using one browser over another would entail a 33% price hike. The price difference is also present for initial purchases, not just upgrades (actually, it looks like there’s no price advantage for upgrading). The price difference for multi-user licenses is even higher. You’ll pay $110 more for a 3-user license in IE than in Firefox.
Price is $119 in Chrome. I don’t have Safari on this computer, so I can’t check that. Want to bet it’s higher than IE?
Here’s the product page in question:
And here’s my chat with “Ronald”, the customer-service robot:
Ronald: Hi! Thank you for chatting with us. May I have your name please?
you: My name is Tim.
Ronald: Hello Tim! Pleased to meet you online.
Ronald: How may I help you today?
you: When I visit your website in Firefox, QuickBooks Pro 2009 Upgrade costs $119.00
you: When I visit your website in IE, it costs $159.00. Why?
you: Any response?
Ronald: Currently we do have several offers on the website.
Ronald: Any of the offer that you select is good.
you: Yes, but why would I want to select the offer that is $40 more? Aren’t you ripping off people that use IE?
you: Your website doesn’t work very well in Firefox, the browser I usually use, and when I switched to IE to complete my order, I found that the price was $40 higher.
Ronald: No, as mentioned there are several offers available on the website.
Ronald: You can choose the $119 option.
Ronald: There wouldn’t be a problem with that.
you: Do you have an offer that will let me choose the $119 option in IE?
you: Perhaps a coupon code?
Ronald: I’m sorry. We don’t have access to coupon codes.
you: So, there’s no way someone using IE, which works better with your website, can get the Firefox price?
Ronald: I highly recommend that you contact the Customer Service Department for that need. We don’t have any control on the pricing offered on the website. I’m sorry for the inconvenience.
December 15th is Esperanto Day
Today, December 15th, is Esperanto Day, in honor of the birthday of the inventor of Esperanto, Dr. L. L. Zamenhof. In 1887, Zamenhof published a thin textbook with a basic grammar, dictionary, and sample sentences in his example language. Since then, Esperanto has become one of the most successful created languages, attracting enthusiasts from around the world.
People learn Esperanto for a variety of reasons - to travel, to meet people, to stretch their brains, to read new literature, to further some idealistic goals, to satisfy their curiosity about languages. I decided to learn Esperanto as a challenge to myself - I wanted to become fluent in a second language, and Esperanto was a fun choice.
It’s hard to find objective information about Esperanto. Almost everything written by non-speakers of Esperanto is wrong or overstated. Esperanto is a real language; it does have a literature and culture to itself; it isn’t a failed project. Similarly, almost everything written by speakers of Esperanto is overstated or exaggerated. Esperanto doesn’t have two million speakers; it has many failings, both linguistic and political; it isn’t going to become the world’s international second language.
But for many, including me, Esperanto has brought many benefits. I’ve learned more about the world, traveled to places I’d never thought I’d go, and met people both intriguing and bizarre. Learning and speaking Esperanto has been a great experience for me, and I’d recommend it to anyone with an interest in languages, travel, or literature.
If you want to learn more about Esperanto, I’d recommend http://www.esperanto-usa.org, the homepage of Esperanto-USA, the national organization of US Esperanto-speakers. (I’m the vice president of this organization.) Lernu.net is also a good resource for starting to learn the language.
Old Orchard Beach
Today, as I was writing some checks to authors for our laboratory continuing education program, I ran across an address for Old Orchard Beach, Maine. I was somewhat struck by this - it has a sort of “Yahoo Serious Film Festival” ring to it (”I know all those words, but that sign just doesn’t make sense”).
Anyway, I researched the town a bit. It takes its name from an apple orchard located on high land above a sandy beach, and this was a landmark to sailors. In 1820 a “Publick House” was built, and in 1837, a summer boarding house began the town’s march toward becoming a haven for summer tourism. In 1898, the town opened a 1,770-foot-long pier, but a combination of fires and storms in the early 1900’s ruined many early beachfront buildings, destroyed the “White City” that was built on the pier, and trimmed the pier to a (still respectable) 700 feet. A new pier and the amusement park that’s located there opened in 1980 (current pier length: 500+ feet). [http://www.oldorchardbeachmaine.com/History.htm]
Old Orchard Beach touts itself as the last remaining beachfront amusement park in New England. Sounds like fun!
Bob Dylan’s new “Bootleg Series” Album
The new Bob Dylan Bootleg Series album, Tell-Tale Signs, is streaming over at NPR:
http://www.npr.org/templates/story/story.php?storyId=95047293
The songs are a mix of alternate versions (like Time Out of Mind - era versions of “Mississippi” and a freaky “Most of the Time”), live versions of “Love and Theft” and “Oh, Mercy” songs, a few unreleased songs, and released songs from movie soundtracks that haven’t made it to an album before. As someone who bought the whole Gods & Generals soundtrack just to get “‘Cross the Green Mountain,” I appreciate this (no, it wasn’t on iTunes at the time).
Avid Bob collectors will likely have most of these songs already, but it’s nice to see some of the bootleg hits make it out to a larger audience, especially the more mournful cut of “Tell Ol’ Bill” that’s been circulating for awhile - I think it’s superior to the released, up-beat version. I think there may be a few cuts on the new Bootleg series disc that are completely new to the world, though, and that’s fairly intriguing.
Two CD set comes out on October 7th. (Pre)order from Amazon:
Tell Tale Signs: the Bootleg Series Vol. 8
iPhone Web Apps Aren’t Dead
When Apple opened the App Store, I thought we’d seen the end of iPhone web apps. App Store apps are clearly technologically superior and have better access to the iPhone’s hardware (camera, location). Perhaps more importantly, developers can sell their applications, which is much more difficult (but not impossible) for web apps. For many applications, advertising isn’t a viable business model.
Since the opening of the App Store, I have seen a dip in traffic to my web apps and an increase in the number of people who e-mail me asking for an App Store version or for download instructions (half the time, they mean adding a bookmark icon to the home screen). But the bottom hasn’t fallen out of the web apps barrel. Web apps aren’t dead.
In spite of their many shortcomings compared to App Store apps, Web apps have several advantages. And Apple’s own policies have recently added several items to this list!
You’re not locked into Apple. You don’t need a Mac / Hackintosh to write a web app. You don’t need to learn Cocoa / Objective C to write a web app. Your web development skills are 100% applicable.
You’re not locked into mobile phones. Web apps can more easily become traditional web pages, and vice versa. A well-designed web app, will appropriate separation of presentation and business logic, can be quickly converted into a traditional web page meant to be viewed on the desktop. Similarly, a well-designed traditional web page can get a customized presentation layer to become a web app. Aren’t you glad you took the time to build your layers right?
You’re not locked into the iPhone. If Google’s Android OS takes off, this will be especially important. Likely, an iPhone-optimized web app won’t need a lot of changes to be usable on an Android-powered phone. If changes are necessary, the same principle of well-designed web applications can speed development and help with maintenance.
No F#&@$#%$ NDA. Talk about ‘em all you like!
No developer’s program or license. Build web apps for free, distribute them for free.
No wait time on submissions, no rejected submissions. You can distribute your web app any way you like. If you want to go through through Apple’s web app directory, which is entirely optional, the review is casual and the terms are easy.
No sharing with Apple. You can keep 100% of your revenue.
No Jailbreaking. There are some great apps for Jailbroken phones, but I don’t think they will ever be mainstream alternatives to App Store apps or web apps. Ordinary people won’t “jailbreak,” even if it is extremely easy. Maybe it’s the name. Could we call it “cupcaking” maybe? “I cupcaked my iPhone to run Quake.”
Note: I think that these rules apply only to the iPhone, not the iPod Touch. The limited connectivity of the iPod Touch severely limits the usefulness of a web application. Clever developers have created some workarounds with queuing and caching, but I don’t see a bright future for growth in iPod Touch web apps – until we get our promised nationwide wireless Internet. I bet that would cost a lot less than $700 billion and have a strongly positive effect on the economy as well. In November, I will vote for the candidate that proposes universal wireless access over a Wall Street bailout.
I’m curious to see how the Google’s application marketplace will change the mobile application ecosystem. Will Google’s openness push Apple to be more open as well? Will the appearance of new platforms make people aware once again of the ability of web apps to bridge the gaps between those platforms? It’s why the Web was successful. We don’t have an Internet for PCs, an Internet for Macs, an Internet for UNIX. Why should we have an app store for just one phone?
A model for profitable, amateur iPhone web apps
A little background
I am a hobbyist iPhone developer (note), with no real intentions to expand far beyond a hobbyist level. That being said, hobbyist developers can and do create and contribute to excellent applications for the iPhone and other platforms. And, with the right plan, hobbyist iPhone developers can make a little scratch on the side.
My goal for developing iPhone web apps wasn’t to get rich. I don’t think that’s possible in the current web app environment. Monetizing a web app was more a “metric of success.” How would I know that my web app was successful? Because it made a little money. For me, this was more motivating that seeing an uphill graph in Google Analytics.
To start, I wrote a very simple tip calculator (the “Hello, world!” of the iPhone application developer). The only trick to this app was to implement a checksum based on an article featured on BoingBoing at the end of 2007. I dropped a Google AdSense block onto a simple JavaScript tip calculator that I wrote during class, submitted it to Apple Web Apps directory, and was shortly greatly surprised to see, within hours, over a thousand users for my silly little application. That was my first $10 of AdSense’s money.
Over the next few months, I added seven more iPhone web apps. Only two of these stored any data locally - the rest served more as front-ends for APIs, including Zillow, Google Base, LyricsWiki, and Google Translate, with AdSense blocks attached. None took more than a few hours to create. All were written in C#.NET and run off a $5.99 / month hosting plan at GoDaddy. Despite the simplicity, these apps proved to be fairly popular. Three of my web apps (TokTok Translator, WeightDate Daily Weight Tracker, and LaLa Lyrics Search) were chosen as Apple Staff Picks. At their height, the apps attracted about 15,000 users per day, which AdSense converted into $40 - $60 / day. Since launching the web apps in February, I’ve earned about $4,000 through AdSense.
Four grand isn’t going to make me quit my day job, and I’m not sure there’s too much more room for growth, except in adding more applications that can each earn their own daily $5 - $10.
The six-step model to profitable iPhone web apps
So, here is my suggested model for developing a profitable iPhone web app. None of these steps are revolutionary, but I haven’t seen any other blogs lay them out quite so directly. It may be a fear of competitor - there’s only so much room for weight trackers and daily budget calculators. I’ll try to sprinkle in a few tips and tricks that I’ve learned.
Step 1: Develop a web application
Develop a web application around a simple, focused idea that people will want to access frequently. Novelty isn’t going to win over a regular user base. An app that users will visit one time isn’t going to create daily revenue, day after day.
Step 2: Add Google AdSense code blocks throughout the application.
I had the most success with the four-ad, 250 x 250 block, located at the bottom of the page, combined with a one-ad block at the top of the page. On introductory and sign-up pages I hid the top ad block, to give the web app a cleaner look for first-time visitors.
Step 3: Submit the web app to Apple Web App directory.
People use the directory, and there’s no other large, authoritative directory of web apps available. Several other directories pick up on Apple’s RSS feed of web apps. I haven’t found the traffic on these to be substantial, however. If you’re looking for Google Juice, submitting an app to the Apple Web Apps directory nets you a nice, juicy PageRank 10 link (without a “nofollow” attribute!).
Step 4: Wait for Apple to review your web app.
Yes, Apple does look at your web app. The first searches on my Zillow property app HiHome were for Cupertino, CA. The review is not extensive. They are looking to make sure that the web app is usable on the iPhone, conforms to the description, and does not violate the Terms of Service (there are some naming requirements and the usual “adult material” caveats).
The review process typically only takes a day, maybe less, and then your app will be listed at the top of the chronological list of web apps. All the web app and category pages are listed chronologically, even the Staff Picks. You’re going to get far more traffic at the top of the list than after a few days. Apple does not have a rating or review mechanism for web apps, unlike in the App Store. So, the only way people will find your web app is through a name search, or because it’s been recently (re)submitted. See step 5.
Step 5: Resubmit your web app.
Apple gives you the opportunity to resubmit your web app when you make changes or updates. The caution here is that you actually need to make a change or update, or at least write about one in the “What’s New” field on the web app submit form. Not updating this field means that it’s far less likely your resubmission will be accepted, which means you won’t jump back to the top of the list. Being at the top of the list on several of my web apps is the difference between 15,000 visits and 3,000 visits.
Too many resubmissions will cause Apple to ignore your future resubmissions for awhile. I learned this the hard way, but at least I learned my lesson and did not get blacklisted.
The best time to resubmit is on Thursday or Friday. With the short delay for reviewing the resubmission, your web app will get bumped back to the top on Friday evening. Since Apple doesn’t update the web apps directory on the weekends, this gives you the longest time at the top, during the most active period for the directory.
Step 6: Profit!
Or rather, enjoy a modest AdSense income and the occasional congratulatory messages from some happy users.
That’s my model for a modest, hobbyist success from iPhone web apps. Do other developers have vastly different models? Are these more successful or less successful that what I’ve described? I’ve considered abandoning the advertising and putting up “if you like this app, consider donating through PayPal” links. Does this seem like a viable alternative?
If you have an iPhone and want to try out some of my web apps (developed under the moniker “TippyTops,” which was actually just supposed to be the name of the tip calculator but soon grew into a broader label), please visit http://www.tippytops.net.
(*) I do work as a professional web developer for MediaLab, who creates online compliance and continuing education courses as well as laboratory continuing education courses (CEU) for medical technologists. But we don’t do any iPhone development, and we don’t have an advertising-supported business model.
