Jeremy Rand

AFAICT the "Lite and Web Clients" section of `dot-bit/security-model/index.md` is basically just talking about stuff that applies equally well to Bitcoin. I tend to think the Namecoin website shouldn't be...

The 51% Attack section in `dot-bit/security-model/index.md` should be merged into the 51% Attack section of the FAQ, with cleanups if necessary.

AFAIK Namecoin hasn't actually supported I2P naming since Convergence for Namecoin stopped working. We should probably remove mentions of I2P from the documentation, e.g. in `dot-bit/index.md`.

`dot-bit/index.md` states: > Dot-Bit's phonebook updates within 40 minutes on average with default settings. AFAICT this is based on the 10-minute target block time, plus NMControl's 30-minute cache, right? ncdns's...

`dot-bit/index.md` states: > Dot-Bit's digital phonebook doesn't generate any network traffic when you lookup a website address, which improves your privacy. NS/CNAME/DNAME records will produce network traffic, as will any...

`dot-bit/index.md` states: > If a single CA (there are thousands) gets broken into by criminals Do we have a citation for there being thousands of public CA's? Presumably the certificate...

`dot-bit/index.md` states: > So-called experts claim that HTTPS (the "secure" website protocol) prevents this kind of hijacking, but it doesn't. Dot-Bit prevents hijacking __for real__. It would be nice to...

`dot-bit/index.md` states: > instead of the phone book being a corporation or government, the digital phonebook is on __your own computer__. Bitcoin technology ensures that every user in the world...

` dot-bit/index.md` states: > Dot-Bit-enabled websites are immune to these problems This wording feels a bit strong to me. For example, if you delegate a Namecoin domain name to DNS...

`dot-bit/index.md` states: > The problem is that these DNS servers are controlled by governments and large corporations, and could abuse their power to censor, hijack, or spy on your Internet...