Changes to name filter about namecoin-legacy HOT 5 CLOSED

Note that you can also use "name_scan" for bulk retrieval, which is what I use. I think it is simpler, since you don't have to pass a "fake" regexp. But that's probably a matter of taste. Also, the information that name_scan returns is not the full name_show, either.

I think your requests are reasonable, this should be fixed (with low priority, although I may give it a try soon as it is probably very easy).

from namecoin-legacy.

Does name_scan give you the ability to restrict results to current, registered domains?

from namecoin-legacy.

Dates are really hard to pin down in general. It's outside the scope of this ticket, but I posted some discussion on the forum to setting a more sensible renewal time period (closer to a year) and setting up a soft "expired" date for applications trying to figure out if it should resolve a given address.

Anyway, what about returning the best-guess expire date? Right now, I'm basically dividing the expires_in value by 6 and adding that number of hours to a date object. Not sure if its worth the effort of putting in here or not.... : /

from namecoin-legacy.

The date would always be wrong. IMHO it is a bad idea to display a date estimate, especially since it is so easy to calculate. What would be of interest is information on whether all blocks have been downloaded at all.

from namecoin-legacy.

I suggest for this discussion to be moved to the forum.

from namecoin-legacy.