131 karma · joined December 1, 2011
Step 2) Humbly request the wizards of Github to port a suitable form of the site suited to this endeavor.
Step 3) Contribute!
1) Way over-estimated the "time to bounce" for an event. It happened to be just over an hour from occurring and when I changed the start time to "manually" account for rough travel time, a more reasonable Bounce time was suggested.
2) Throws "unrecognizable event location" for a typical address (which Google Calendar takes no issue with): Location Name, Street Address, City, ST ZIP
(Wanted to see if back-to-back events made recommendation based on being at the preceding event location, but... see previous error)
I like BustAName's AJAX-powered containment of the features, though a redesign is in order.
Aside from design considerations, you may want to look at how you can point users in the right direction before they arrive at the results page and then have to starting filtering or start over to achieve more desirable results.
For example, you could offer corrections to potential typos. If a typo is not detected (or disregarded), provide some likely criteria for the eventual results, starting with common scope limiters for domain names.
I acknowledge that your product name is "lean" but there are possibilities for domains that I can safely opine that a significant majority of users will be uninterested in, and I'm not sure from the results page effectively communicates whether those have been sifted out or not.
Seems there is still demand, and room, for simplified domain search. Cheers!
Superior in practice: http://www.bustaname.com/word_maker
Though I prefer where you've started.
Also, your favicon is... suggestive of something entirely different. Perhaps a less literal image would be better?
What will the leading actors in security theater wear, then?