Quote from: kiba on April 21, 2011, 06:03:31 AM

It seems that bitcoind is instead reading the configuration file in .namecoin rather than .bitcoin?

That is kinda odd, I'd get it if it was the other way around. Are you sure they aren't hard linked or anything? I'm running both by the way, with RPC servers on. I suggest you run namecoind as a different user, just in case.

Quote from: ryepdx on April 21, 2011, 03:34:06 AM

Quote from: dmp1ce on April 21, 2011, 02:53:40 AM

About the design questions, I have not a clue. I think 3 months is reasonable, especially if it auto renews. Why do we have to decide on the TLD? Is it possible that Namecoin names could specify the TLD to use as well?

I second the question.

Yes I also think 3 is OK, but 6 would be much better. Can we meet third way and make it 4? Cheesy

Regarding TLD: There is also the question about TLD's other than .bit (or whatever is accepted as the default). However I think putting TLD in the name is kinda against the established architecture. I think it needs to be part of the name specification, not the name itself.