"Sniped" makes it sound like they did something wrong, but they didn't. I reject the idea at the end that there were ethical lines crossed. You need to buy your domain when you name the project, not when you release it. If you don't have the domain then you don't have the name. Buying the domain is naming it. Take the lesson for next time.
Domain Sniped on Launch Day
11–20 of 51 posts
Re: Domain Sniped on Launch Day
#12I'm sorry, but aren't GitHub repos private by default?
edit: see down-thread, but they are private by default in GitHub Desktop, which is what I have used to create new repos for years. However, they are public by default on github.com.
Re: Domain Sniped on Launch Day
#13:facepalm:
Re: Domain Sniped on Launch Day
#14Hot take:
We should work towards dethroning .com as the default so that all the people who trade domain names lose all the money they had never earned. I'm also for a more expensive .com base price. Some of the things that make moving away from .com hard is the blanket gtld level email/traffic bans in Sophos and other security firms
Re: Domain Sniped on Launch Day
#15They way how it currently works is bad for the SaaS/app developers, bad for the content creators, and bad for the users.
It is ridiculous that nowadays you cannot buy a good domain name, because someone mass registered all of the meaningful combination of words in every existing tld, in hope that they can sell some of them for a few thousand dollars to someone who is willing to pay for it.
Not to mention these obviously unethical cases like this.
Re: Domain Sniped on Launch Day
#16Honestly, there have been so many businesses and individuals that lose out on their domain because they just didn't buy it as soon as they saw it was available. I don't understand why - in the grand scheme of things a 5, 10 or even $100 domain isn't going to break the bank. Just buy the thing as soon as you find it and avoid this mess.
Re: Domain Sniped on Launch Day
#17Re: Domain Sniped on Launch Day
#18"Sniped" makes it sound like they did something wrong, but they didn't. I reject the idea at the end that there were ethical lines crossed. You need to buy your domain when you name the project, not when you release it. If you don't have the domain then you don't have the name. Buying the domain is naming it. Take the lesson for next time.
That's life. Lesson learned.
Re: Domain Sniped on Launch Day
#19"Sniped" makes it sound like they did something wrong, but they didn't. I reject the idea at the end that there were ethical lines crossed. You need to buy your domain when you name the project, not when you release it. If you don't have the domain then you don't have the name. Buying the domain is naming it. Take the lesson for next time.
Watching folks build something, seeing them prep to launch it, then buying the domain in response to that (in the hope that they'll pay more for it)? Totally legal (and IMO should be!), but anyone doing that is absolutely crossing an ethical line.
Re: Domain Sniped on Launch Day
#202. The post is a big list of "I made mistakes and had to face the consequences" — not one, but multiple. (Open repo, legalese comms to NC, non-actionable email to registrant) I've got a lot of sympathy, but I don't know if there's any learning besides "think -> do -> check -> repeat".
3. Congrats on the launch! For what it's worth, kill-saas.com looks more pleasing to my eyes than killsaas.com :)
Bonus Point 4.: I had a similar idea for a website with the same name a year or so ago when I was cancelling all my Netflix, Spotify, etc. subscriptions. There's evidence in my Whatsapp convos. Then again, I don't feel like you've stolen anything from me & wish you all the best! ;)