base64: bThvW3JKYz16bXpUWDIufkl2OllseC4maV1gMjtVYXNtb2RyZ3czbkQzQDtnZnRdMVZuZkIqVTJpIGlxa2xubkAoaTRueGdQaGN0YyRjTGN1WGlUbzF5VU5qcz50KmRwZXlncGN0dA==
text: m8o[rJc=zmzTX2.~Iv:Ylx.&i]`2;Uasmodrgw3nD3@;gft]1VnfB*U2i iqklnn@(i4nxgPhctc$cLcuXiTo1yUNjs>t*dpeygpctt
letters: $&(48:=>BDIJLNPVY[`aehjkquvw~*.13;@TX]dflprsxyz2Umogintc
counted: 111111111111111111111111111111222222222222222222333345556
progressively hiding infrequent letters:
m o r c zmzTX2. lx. i] 2;U smodrg 3n 3@;gft]1 nf *U2i i lnn@ i nxg ctc c c XiTo1yU s t*dp ygpctt
m o c m 2 i 2 U mo g n g t n U2i i nn i n g ctc c c i o U t g ctt
c i g n g t n i i nn i n g ctc c c i t g ctt
c i n t n i i nn i n ctc c c i t ctt
c c c c c c
One small glitch: it seems that on the page http://boardlite.com/category/computers/list/ some vertical gray border is missing on the left side of "1 post" and "16 views", where the light blue headline becomes narrower and says "Tracking ID: 400000001" etc. Same problem on the FAQ page at http://boardlite.com/faq/ ...
Point taken. I have now integrated the display of taken (and parked and error) top level domains again, trying to make it useful but not too distracting.
Yes, that was the previous version that I announced here on January 1st. I figured that usability is more important than fine-grained control over the score weights, because the sort order is not terribly critical. Basically, the user should be able to adjust the trade-off between short and popular names. But it's a brainstorming tool, we're not trying to get one particular name to the very top of the list.
Because it's a search engine for short names, using a large database of unused and expired domain names. Try searching for "hack" + "ne", or "hack" + "e" for even more results.
Actually, I have now enabled the search indexes for the following prefix+suffix combinations: 4+1, 3+2, 3+1, 2+1, 2+2, 1+1, 1+2, 1+3, 2+3, 1+4. I may add longer combinations later, but for now they will be shortened and filtered, e.g. 5+3 will use cached 4+1 and then filter the results in the browser with JavaScript.
Yes, I know the combined prefix and suffix search doesn't work properly yet. The reason is that the App Engine datastore doesn't support fancy search, only sorting with custom indexes. All results for a GQL query must be adjacent in the index. The indexes for combined prefix+suffix search are still building but should be ready in a few days.
1) You're right, but the boxes (and columns of numbers) are probably going to disappear in the next version. Maybe we'll have sliders or radio buttons to adjust between "Important" and "Don't care" for some properties.
2) Real substring searches are not supported because they are expensive. But your example is supported: type "debate" in the second keyword input field for suffix matches.
You're right. At some point I'm going to start using http://getsatisfaction.com/ or think about moderation/filtering. But for now I really like the direct feedback from users, so I'm going to delete bogus entries manually from time to time.
Congratulations to our first customer! Since my post on HN we had 612 hits on moniker.com, with 1 conversion for $0.31 commission. I also spent $1.60 today for 22.43 CPU hours on Google App Engine. Almost all of the 17k requests today were AJAX queries for domain searches.
Because we can't run DNS queries inside Google App Engine. Instead, I query the DNS results from my home computer and feed them into the datastore using remote_api.
Yes, that would be interesting because the startup time for loading the zipped Django 1.1 package is significant. Maybe app-engine-patch can be tweaked to use_library()?
I understand that's annoying, and hope to improve it. The system reports digit.com free because it doesn't have an A record, but I will fix this by checking SOA records in the future. I'm not sure why 6af.com is reported free, maybe there was a temporary DNS problem when I checked it. It should be updated in a couple of days.
My list is a fairly random sampling of the huge search space of available domain names. I'm planning to keep adding more names in the future, trying to strike a balance between good names (short but readable) and more names (requiring more storage). Fortunately, the App Engine Datastore has linear complexity for the number of query results, so adding more names doesn't slow down the searching.
Python script: http://pastebin.com/7Jv891zg