Live data from Hacker News

Web Domain White Elephant Exchange

docs.google.com

41–50 of 103 posts

Re: Web Domain White Elephant Exchange

#41
post #22

this is great. i have a strange compulsion to buy awful domain names, regardless of their usefulness. is there any rule against multiple entries (aside from the possibility of exchanging with yourself?)

Nope! Right now I'm allowing multiple domains, up to a point. (Maximum is 3) Enjoy!

Cool, added two more.

Re: Web Domain White Elephant Exchange

#42
post #39

Earlier quoted context omitted.

I fully expect something to go very wrong with this, so I'm just preparing to not care when it does. :)

The funny thing is someone didn't know the above was sarcasm based on your previous response. I like the idea and I think it'll turn out fine.

People will always try to put us down.:)

Re: Web Domain White Elephant Exchange

#43
post #34

Earlier quoted context omitted.

You can usually transfer it to another user on the same registrar. They just don't want to lose it to another company. (At least, that's my super rough understanding of it.)

You should match people that have submitted domains from the same registrar so fees are avoided in most cases.

That sounds like a wonderful idea... but far too much work for it to be worth it. Maybe next year...

Re: Web Domain White Elephant Exchange

#44
post #24

Aw, I let a lot of my unwanted domains expire this year instead of hoarding them. But given that they were all rubbish, it does mean that heapt.com (you know, like 'heaped', piles of things!) and f6ing.com (a gaming thing...) are free and unencumbered.

If you had them for a while, not necessarily likely... the squatting companies tend to do a grab of recently expired domains... most that I've let go over the years (tend to get 2-3 new ones, and let 2-3 go a year) are in that group.

Re: Web Domain White Elephant Exchange

#50
post #47

Bummer. I have a .de domain that I really don't want/need. The web form won't accept it.

Try again... I disabled the URL validation on that field. However, the validation required http:// in front, so that may have been the issue.

Probably was the missing http:// It works now. This should be fun.
Post reply on HN