The domain naming scheme proposal

[wandrien]

Some related comments and discussions:

• https://github.com/HelloZeroNet/ZeroNet/issues/83#issuecomment-94332474
• https://github.com/HelloZeroNet/ZeroNet/issues/83#issuecomment-489451550
• https://github.com/HelloZeroNet/ZeroNet/issues/1696
• https://github.com/HelloZeroNet/ZeroNet/issues/104
• https://github.com/HelloZeroNet/ZeroNet/issues/2049

The idea:

• ZeroNet site should be accessible with both http://127.0.0.1:43110/... and http://.../ via a proxy.

• When accessing zites with a proxy, the pseudo-TLD .zeronet is used: http://<address>.zeronet/

• When accessing zites with http://127.0.0.1:43110/, the .zeronet part can be ommitted and is ignored by the core if present. These point to the same site:

  • http://127.0.0.1:43110/<address> - the classic way.
  • http://127.0.0.1:43110/<address>.zeronet - for similar look&feel to the proxied addresses.

• The second-level domains are handled by plugins.

• • *

The proposed second-level domain schemes:

• Namecoin domains: .bit.zeronet

  • Proxied: http://Talk.ZeroNetwork.bit.zeronet
  • Non-proxied: http://127.0.0.1:43110/Talk.ZeroNetwork.bit

• Cert-based, as proposed in https://github.com/HelloZeroNet/ZeroNet/issues/1696: .user.zeronet

  • Proxied: http://geekless.zeroid.user.zeronet, http://geekless.kxoid.user.zeronet
  • Non-proxied: http://127.0.0.1:43110/geekless.zeroid.user, http://127.0.0.1:43110/geekless.kxoid.user

• Opennic-based (https://github.com/HelloZeroNet/ZeroNet/issues/104): .opennic.zeronet

  • Proxied: http://example.libre.opennic.zeronet
  • Non-proxied: http://127.0.0.1:43110/example.libre.opennic

• Onion-based (the protocol proposal hasn't been published yet): .onion.zeronet

  • Proxied: http://nd6bvylhggfd41g.onion.zeronet
  • Non-proxied: http://127.0.0.1:43110/nd6bvylhggfd41g.onion

[filips123]

Mentioned sprite add-on tries to support all but that can cause more problems then it solves.

Why do you think so?

Because there is currently no standard, all options should be possible. When standard will be created, only is should be enabled.

[sprite-1]

As far as I know, the only thing my extension potentially screws up are *.bit domains on regular browsers but that's pretty much it

[filips123]

@sprite-1 Can you add configuration page to let users manage which keywords, addresses and TLDs should be rewritten? This would be useful if the user does not need all possibilities or you forgot some of them. It should have the following option:

• Keywords: [keyword] [address] (user chooses [keyword]) -> http://127.0.0.1:43110/[address] (example zn 1Name2NXVi1RDPDgf5617UoW7xA6YrhM9F)

• Keywords: [host]/[address] (user chooses [host]) -> http://127.0.0.1:43110/[address] (example http://zero/1Name2NXVi1RDPDgf5617UoW7xA6YrhM9F)

• Domain without stripped TLD: *.bit, *.yo, *.yu...

• Domain with stripped TLD: *.zero, *.zeronet...

[krzysztof113]

@filips123 Scenario: someone pastes link in reddit etc with http://mydomain.zeronetrocks but you don't have that particular plug-in that will redirect properly and you have to manually extract "mydomain".

[filips123]

@krzysztof113 This is not what that plugin is meant for. And how would you actually do this with a plugin?

This needs to be done with ZeroNet changes. Public ZeroNet instance should accept URL like talk.zeronetwork.bit.example.com where talk.zeronetwork.bit is ZeroNet domain and example.com is proxy URL. The instance should then extract ZeroNet domain, lookup site and serve it. This can't be done with plugin.

For local ZeroNet instances, talk.zeronetwork.bit.zeronet is enought. It should be handled by local ZeroNet instance and can be done with proxy PAC file, custom DNS or DoH server, system program or browser plugin. However, all cases would require ZeroNet changes to handle server on custom URLs.

See this issue, issues linked from this issue and issues that link this issue for details.

[sprite-1]

Can you add configuration page to let users manage which keywords, addresses and TLDs should be rewritten?

I've been meaning to do this but just haven't had the time yet lately so it's definitely something I want in there

[filips123]

I created a comment about different ways of accessing ZeroNet and ways of implementing that in https://github.com/HelloZeroNet/ZeroNet/issues/2100#issuecomment-544664709.