Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: I taught ChatGPT to find cool domain names – with availability check

huehive.co

Post reply on HN
Print view View original

31–40 of 49 posts

Re: Show HN: I taught ChatGPT to find cool domain names – with availability check

#33

Post by mikkom »

I get very poor results from this. I get much better results when I just use chatGPT directly with some custom prompt that asks for good domain names. Here is just one example

> trading investment prestigious innovative fund quant

< trendsnetworking.com

Re: Show HN: I taught ChatGPT to find cool domain names – with availability check

#35

Post by alexvitkov »

giancarlostoro wrote: post #27
SketchySeaBeast wrote: post #15

Earlier quoted context omitted.

Not just slower, far more compute intensive. We're at this weird point where devs will both complain that VSCode is slow and bad because it runs on electron, and then insist that every decision and line of code they make runs through a giant Rube Goldberg machine before they type it.

My only complaint about VS Code is the naming. I'll be googling for actual Visual Studio (2021, 2019, 2015, etc) specific things, and find myself with VS Code specific results all the time. I wish Microsoft would have given it a better more SEO friendly name, they didn't learn from naming SQL Server I suppose. Go has the same problem, which annoys me, a search engine company didn't think that one through. Please, maj…

Adding "-vscode" or "vs2019" to the query usually does it for me. With go I pretty much always search "golang".

Re: Show HN: I taught ChatGPT to find cool domain names – with availability check

#37

Post by amelius »

reddalo wrote: post #9
anonymouse008 wrote: post #3

Just don’t front run us, ok?

That's what I always wondered about this kinds of services. They could easily sniper all the cool domains they found for you.

They, in turn, will be front-run by the availability checking service.

Re: Show HN: I taught ChatGPT to find cool domain names – with availability check

#38

Post by RexM »

SketchySeaBeast wrote: post #30
giancarlostoro wrote: post #27

Earlier quoted context omitted.

My only complaint about VS Code is the naming. I'll be googling for actual Visual Studio (2021, 2019, 2015, etc) specific things, and find myself with VS Code specific results all the time. I wish Microsoft would have given it a better more SEO friendly name, they didn't learn from naming SQL Server I suppose. Go has the same problem, which annoys me, a search engine company didn't think that one through. Please, maj…

I agree that's frustrating, but I doubt Microsoft will be able to ever outdo itself with its .NET Framework/.NET Core/.NET naming convention nonsense.

Don’t forget .NET Standard.

Their naming for all of this is a disaster.

Re: Show HN: I taught ChatGPT to find cool domain names – with availability check

#39

Post by jefc1111 »

dutchbrit wrote: post #2

Cool - not sure I'd want my prompt to be seen by others (which you can achieve by changing the incremental id in the url). Maybe use a uuid instead if you want to make it shareable?

Upvoted as I think it needs to be front and centre that the searches are public.

Re: Show HN: I taught ChatGPT to find cool domain names – with availability check

#40

Post by meowface »

SketchySeaBeast wrote: post #15
RileyJames wrote: post #6

How is this more useful than the current state of domain name idea generators, which also do a search for the availability of the domain? It just seems, slower? The feat of doing that with ai alone might make an interesting blog post. But the end result as a product isn’t something I’m going to use just because it’s using ai. The job to be done is not to use ai to do x. Tho I would be interested to read the blog post…

Not just slower, far more compute intensive. We're at this weird point where devs will both complain that VSCode is slow and bad because it runs on electron, and then insist that every decision and line of code they make runs through a giant Rube Goldberg machine before they type it.

>and then insist that every decision and line of code they make runs through a giant Rube Goldberg machine before they type it.

If you've ever used Copilot, it's surprisingly fast. It definitely leads to net less time spent typing.

Post reply on HN