Just informally. The main goal I had was to try to get a rough understanding of what kinds of websites people are running on Namecoin. E.g. one of the categories I assigned was "programming blog" (which seems to be a rather popular thing people are using Namecoin for). It's definitely not any kind of rigorous categorization scheme, and the choices I made are certainly debatable.
(I haven't yet gotten a chance to post the spreadsheet, I'll do so when I have a few minutes.)
Jeremy Rand, Lead Namecoin Application Engineer
NameID: id/jeremy DyName: Dynamic DNS update client for .bit domains.
I had idea of categories but unfortunately it can't be done automatically.
bitname.ru:
- whois service for .bit: whois.bitname.ru or whois.bitname.bit
- dns servers for .bit: dns1.bitname.ru dns2.bitname.ru or dns1.bitname.bit dns2.bitname.bit
- bit domains statistics github
From now bitname.ru support english language also and not only russian.
bitname.ru:
- whois service for .bit: whois.bitname.ru or whois.bitname.bit
- dns servers for .bit: dns1.bitname.ru dns2.bitname.ru or dns1.bitname.bit dns2.bitname.bit
- bit domains statistics github
From now bitname.ru support english language also and not only russian.
Great news. Makes it easier for most visitors of your site, I guess.
Just noticed a small inconsistency on the Namecoin Network Stats page: "Complexity" should be "Difficulty".
Furthermore, it would be quite convenient if you display the Difficulty increase also as a percentage value, e.g.
bitname.ru:
- whois service for .bit: whois.bitname.ru or whois.bitname.bit
- dns servers for .bit: dns1.bitname.ru dns2.bitname.ru or dns1.bitname.bit dns2.bitname.bit
- bit domains statistics github
It looks like the https://bitname.ru/ server isn't including the Let's Encrypt intermediate CA in the cert chain that it provides to the browser. (At least, I think that's what's happening.) This causes the following error to show up in Tor Browser:
bitname.ru uses an invalid security certificate.
The certificate is not trusted because the issuer certificate is unknown.
The server might not be sending the appropriate intermediate certificates.
An additional root certificate may need to be imported.
Error code: SEC_ERROR_UNKNOWN_ISSUER
Any chance that could be fixed?
Jeremy Rand, Lead Namecoin Application Engineer
NameID: id/jeremy DyName: Dynamic DNS update client for .bit domains.
P.S. Don`t understand how I can forgot to put ca cert in chain... Maybe someone distracted me at time when I was changing cert.
bitname.ru:
- whois service for .bit: whois.bitname.ru or whois.bitname.bit
- dns servers for .bit: dns1.bitname.ru dns2.bitname.ru or dns1.bitname.bit dns2.bitname.bit
- bit domains statistics github