HelloZeroNet / HelloZeroNet/ZeroNet
The domain naming scheme proposal
- 主要言語
- JavaScript
- スター
- 18.8k
- フォーク
- 2.3k
- PR マージ指標
- 30日以内にマージされた PR はありません
説明
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://
* 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/` - the classic way.
* `http://127.0.0.1:43110/.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
コントリビューションガイド
このリポジトリのコントリビューションガイドは索引されていません
調査の方向性
No implementation files, tests, or entry points are named. Read the linked discussions and related issues first, then inspect the existing proxy, core, and plugin handling; done would mean the proposed naming scheme is agreed and implemented consistently for proxied and non-proxied addresses.
索引モデルが issue の本文から書いたものです。
評価
- 領域
- networking
- issue の種類
- 機能追加
- 難易度
- 5/5
- 見積もり時間
- 1週間以上
- 活発さ
- 停滞
- 明瞭さ
- おおむね明確
- 初心者へのやさしさ
- 25/100