".i2p" make it flexible about i2p.i2p

[eyedeekay]

Possible eventually yes, but is it reasonable right now? Probably not. There's a lot that goes into this, and maybe flexibility in our top-level namespace is a reasonable way to start, but meeting all the necessary conditions for such a thing to work is probably hard.

For one thing, just letting people set their own top-level namespaces would introduce a footgun, wherein the user would be able to replace/intercept an existing top-level namespace and MITM themselves. So it would need a way to prevent such a thing from happening.

For another, we might actually have a good reason to change namespaces in the future because real TLD's aren't supposed to contain digits, which besides... some other stuff... is a reason we can't have real TLS certificates like .onion names can. .garlic might be the obvious choice, but that doesn't satisfy "flexibility." In fact, this necessitates narrowing the flexibility of the namespace.

However, human-readable naming is really just an application extension primarily used by the HTTP proxy. If somebody wanted, they could implement their own HTTP proxy with their own ways of mapping keys to values. I've done this, so that applications can maintain their own address books. That might be the quickest way to get what you want, doing it in the core will take a lot of deliberation.