However, let's be honest: your name is not going to make or break you. Don't let choosing a name hold up real progress. If you're sitting there trying to decide what to name your svn/git repo, just call it "myapp" and move on.
The name was professionally chosen and got favorable write-ups at the time (2000 era). Though memorable, it somehow had a wrong feel for the nature of the company's business (selling tech-related books in Silicon Valley).
Still got the cap!
Fatbrain sounds more fun.
Case in point: I have an app (an interactive, online programming notebook), and it was originally called http://knoboo.com. Over the first year or so I agonized over people's butchering of the name, and confusion over the meaning. Over time, I was able to find a better name, http://codenode.org, and I'm very glad I did.
I do, however, stand by the notion that a name can have a net negative impact on a product, especially in a day and age when much product discovery comes through search engines.