Namecoin Forum

You clearly don't understand how Namecoin is designed. Namespace validation is supposed to be done at the nmcontrol level, not the namecoind level. It's not the Namecoin developers' role to tell people what data formats they can and can't store in the blockchain. I understand it in different way, t...

wow, looks really good

I've had this idea for a while making PowerDNS backend as it's awesome DNS server, only haven't had time to work on it.

Sadly I don't like Haskell at all... I would actually make it in D language.

actually, what about complete remake of namecoin on top of Bitcoin Core v.0.9.0? Not try to rebase current namecoin source code, but just reimplement. It would basically like how it is now with QT just with all new bitcoin features. To do this would need to know what is namecoin specific, different ...

There's just no place for messaging in namecoin, but it would be suitable for BitMessage. From namecoin everyone expects mostly name/domain database and it shouldn't include unrelated things. If I want to host namecoin node/DNS, why should I host some tweets as that's completely unrelated. Those twe...

Seems that the most cheapest are from https://cheapsslsecurity.com/comodo/positivessl.html ($5/year and $4 if you buy for 5 years). Wildcard cert would be nice, but they're fucking expensive, so it seems it's actually cheaper to buy multiple ones. Will need for namecoin.info, forum.namecoin.info, wi...

Twitter in Namecoin is stupid idea, DNS servers (and Namecoin nodes) don't care about your tweets and they won't want to store them as that's not related to main purpose of Namecoin, which is to store names, but not some other random data itself.

There's no guidelines for what other namespaces could be used for and there aren't any restrictions either, so yes, your program can use them in any way they want. Someone can create namecoin DNS server which will use "lite/" (or "u/") namespace for .bit domains (or for any other) and not "d/". Now ...

I recommend to check out my suggestion which I wrote in Dev section of this forum. Because I think it's unavoidable that people will start to use namespaces for all kinds different reasons and because there's no way to determine which is correct usage there will be problems when multiple apps will u...

Namespaces (such as "d", "id" and others) are not owned by anyone and not even enforced what they represent as all those "specifications" are just guidance and they aren't really validated. For example anyone can register a domain with {"ip":"fake"}. In reality this isn't a big issue, but it means a...