search

namecoin / namecoin-legacy

Legacy client. New version here: https://github.com/namecoin/namecoin-core Note the release branch! - Official website:
https://namecoin.org
MIT License
448 stars 177 forks source link

size limit for entries json string #216

Open ulrichard opened 9 years ago

ulrichard commented 9 years ago

There seems to be a 512 char limit on the json string. Is there any possibility I could use more chars for my id entry?

JeremyRand commented 9 years ago

Hi,

The limit is actually 520 bytes. However, you can get more by using the "import" field. This is not particularly well documented at the moment, though.

ulrichard commented 9 years ago

I couldn't find any documentation, and what I tried doesn't seem to work :

d/ulrichard stopped resolving on opennic dns servers after I introduced the include.

id/ulrichard doesn't retrieve the address in PyBitmessage, I have to use idd/ulrichard_bitmessage explicitly.

Are the includes resolved by the namecoin daemon or the querying application such as nmcontrol, bitmessage ...?

JeremyRand commented 9 years ago

@ulrichard It's handled by NMControl. I'm actually not sure if we currently implement multiple imports in a single name (I see you're using a list). The import code is going to be refactored, so we'll make sure lists work properly when we do that.

ulrichard commented 9 years ago

Wouldn't it be better if it was expanded by namecoind? That way it would directly work for other applications as well. For example BitMessage.

JeremyRand commented 9 years ago

@ulrichard The intention is for applications such as Bitmessage to read the blockchain using NMControl rather than directly querying namecoind. I believe Bitmessage supports reading from NMControl, no?