I got way more interesting results by switching to "Almost Natural".
Ask HN: Please, review wordoid.com, a smart naming webapp
71–79 of 79 posts
Re: Ask HN: Please, review wordoid.com, a smart naming webapp
#72I like it. It wasn't immediately obvious to me what some of the features did though - the search button and the unique/common graph next to it for example. I'm also a little disapointed it won't generate names in Klingon - after all, it offers to! :)
Re: Ask HN: Please, review wordoid.com, a smart naming webapp
#73Earlier quoted context omitted.
ironkeith, this most likely is a HN effect (luckily? :) The webapp has been developed with performance in mind, however I've already noticed some glitches to fix.
More on this: The website received about 3500 visitors during 12 hours after I posted this review request here on HN. Thank you guys! Thanks HN! It has been way more than I expected! There's a bottleneck somewhere in the algorithm that creates wordoids. That's why wordoid.com is irresponsive sometimes. The webserver and the database seem to run smoothly.
Re: Ask HN: Please, review wordoid.com, a smart naming webapp
#74I like it... combining English words with a foreign language seems to make for some really interesting combinations. Seems to be very quick as well which is great. Would be cool if it would check .com .net and .org variants as I wouldn't settle on a name unless all three were available (+ .co.uk as I'm in the UK!). On another note, while I was playing with it, the name 'effection' came up and effection.com was showin…
Yeah, i saw "carlover.com" in green and thought "you've got to be kidding, i'd buy that in a heartbeat" (I love cars). Unfortunately, it was kidding.
Re: Ask HN: Please, review wordoid.com, a smart naming webapp
#75Very nice, I've been looking for something like this that actually works and isn't trivial. I got some really nice results. First (nitpick point): You've got a misspelling in the page: scarse instead of "scarce" underneath the bars that show frequency. The UI on the right is a bit confusing and busy. I suggest removing all the text around each of the options. I might then put them at the top of the screen with the "g…
Re: Ask HN: Please, review wordoid.com, a smart naming webapp
#76For example, I may only want VERB wordoids.
Also, you should measure how easy and unambiguous the SPELLING is.
Re: Ask HN: Please, review wordoid.com, a smart naming webapp
#77Earlier quoted context omitted.
ironkeith, this most likely is a HN effect (luckily? :) The webapp has been developed with performance in mind, however I've already noticed some glitches to fix.
Well done Oleg but where's the Russian language on the side? =) I don't know if it's in the works or what, because wordoid just generated veter.com for me (which is still available). Would definitely be fun.
However, I'd consider it an advantage for Russian speakers to NOT have Russian on the list. As a speaker of another language also not on the list, I wouldn't want any automated competition on coming up with words with that basis. (My other language has been a gold mine for me. ;) )
Re: Ask HN: Please, review wordoid.com, a smart naming webapp
#78Earlier quoted context omitted.
Yeah, i saw "carlover.com" in green and thought "you've got to be kidding, i'd buy that in a heartbeat" (I love cars). Unfortunately, it was kidding.
Wordoid.com checks domain availability by querying a DNS server. This is not completely accurate, since some domains don't have DNS records. The right way is to query a whois server. That's tough, because i don't know of any whois servers that would allow me send bulk queries.
Re: Ask HN: Please, review wordoid.com, a smart naming webapp
#79Thanks for a useful resource.
If you change your DNS lookup method, I think you'll have fewer false positives where you list domains as being available, when they actually aren't.
For example: readia.com is not available, but the wordoid site says it is.
If you do a DNS lookup at the .com core servers, rather than your local resolver, you'll get a list of NS servers for the domain - if it's blank there, then you know the entry doesn't exist.
The current problem is occurring because your resolver library is trying to walk the DNS tree all the way to the DNS servers that are supposed to manage the domain. When those servers are down or unresponsive, wordoid is marking the domain as "available" - even when it's not.
Here's an example that I think demonstrates the problem, and a potential way around it:
dig ns readia.com. @a.gtld-servers.net. ... ;; ->>HEADERNote that it indicates no error.
For a nonexistant domain the results are different. The NXDomain means "no such domain". dig ns this-really-does-not-exist-at-all-1321.com. @a.gtld-servers.net. ;; ->>HEADEROf course, you'll need to switch between the relevant gtld-servers so that you're a good network citizen, and cache results. See "dig ns com." for a current list of GTLD servers.
Also, I'd like to echo the comments of other readers - if you place a "go" button near the input form, rather on the top left, it'll improve the user-interface significantly.
Thanks again, and I hope the above helps you.
Oskar Pearson