HelloZeroNet / HelloZeroNet/ZeroNet
Use BitTorrent for file sharing
- Lenguaje dominante
- JavaScript
- Estrellas
- 18.8k
- Forks
- 2.3k
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Descripción
I think ZeroNet should transition over to using BitTorrent directly instead of trying to imitate it.
BitTorrent is a much more robust and well-developed protocol. I mean no disrespect to ZeroNet, but projects like [libtorrent](https://github.com/arvidn/libtorrent) have very large budgets devoted to them, probably greater than all of ZeroNet, and it's just for transferring data and nothing else. BitTorrent can also handle larger files, as well as other things.
BitTorrent is an open standard. If ZeroNet started to use it, it'd be possible to interact with other BitTorrent-based projects. This is useful. For example, you could embed videos from BitTorrent directly into zites, and people could download zites in their BitTorrent clients.
If ZeroNet started using BitTorrent for new sites, it could focus on the core functionality, like building decentralized interactive websites, like using Tor instead of trying to re-invent the wheel. With that, making new implementations would also become much easier, because you could use a ready-made BitTorrent library instead of having to re-write the entire file sharing module.
Two semi-recent developments on BitTorrent have made this situation more interesting, and cleared away the last blockers:
* [BEP 52](https://www.bittorrent.org/beps/bep_0052.html) switches the hash algorithm from SHA-1 to SHA-256, changes hashing to the level of individual files, and implements something similar to [TTH](https://en.wikipedia.org/wiki/Merkle_tree#Tiger_tree_hash) to get smaller torrents while keeping piece sizes at 16 KiB
* [BEP 46](https://www.bittorrent.org/beps/bep_0046.html) (or possibly [BEP 50](https://www.bittorrent.org/beps/bep_0050.html), or a custom solution as an extension) allows to dynamically update content
BEP 50 is a good example of this: ZeroNet handles updates (correct me if I'm wrong here) by naively gossiping them, whereas BEP 50 has a very clever structure for making sure updates are propagated in an efficient manner, basically creating an overlay network. Using BitTorrent allows ZeroNet to make use of all of these improvements, while still giving it the freedom to create extensions as needed. If useful, these extensions could be made into a BEP and pawned off onto upstream maintainers.
To be clear here, I'm not proposing that anything be explosively decommissioned, like Tor or Python v2. There's no urgent security flaw that mandates it.
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
Línea de trabajo
Start by reviewing ZeroNet’s existing file-sharing module and the BitTorrent BEP 46, BEP 50, and BEP 52 proposals linked in the issue. Determine whether a migration path can preserve current site updates and compatibility. Done would require an agreed design and implementation plan, not a single localized change.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Área
- distributed-systems, networking
- Tipo de issue
- Nueva funcionalidad
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Estado de actividad
- Estancado
- Claridad
- Necesita aclaración
- Aptitud para principiantes
- 15/100