HelloZeroNet / HelloZeroNet/ZeroNet

Ideas on How Zeronet Could Improve

オープン
#1,423 コメント 5 件 リアクション 4 件 担当者 0 名 GitHub で見る
主要言語
JavaScript
スター
18.8k
フォーク
2.3k
PR マージ指標
30日以内にマージされた PR はありません

説明

Note: Many of these have been mentioned by other people.

* Performance
- Starting up ZeroNet after being off of it for months is very painful! Not only does it take a long time to download stuff (which may not be able to be improved, not sure on that), but you can't visit any zite that accesses a database because the loading of all the other databases blocks it.
- ZeroNet needs multi-threading and parallelization
- ZeroNet needs to prioritize the downloading of files of the zite you are *currently looking at*, not sure how possible this is.
- Ability for dev to set the files that should be prioritized to download as early as possible before other files. I would like the index html file and the main js file to be downloaded before images, etc. - not sure how possible or realistic this is.
* Backing up the files you're seeding and your zites easily.
- The Download Zite as Zip File feature helps quite a bit with this, but it still needs to be improved
- A zite where you can select all of the zites you want to download zips of that way you don't have to manually go to each and every zite
- Move user's files (aside from data files) to one location so that you can actually use them outside of ZeroNet, reduce duplications, etc.
* ID's
- It might be good to provide a way to backup or somehow sync your users.json file between multiple clients. However, not sure how this would be done *securely*
- Allow multiple id's from same provider so that all of them are listed when selecting a user.
* Documentation, Tutorials, Tour of ZeroNet
* Better Android client

コントリビューションガイド

このリポジトリのコントリビューションガイドは索引されていません

調査の方向性

No files, tests, or entry points are named. First separate the performance, backup, identity, documentation, and Android suggestions, then locate the relevant areas and determine which single proposal has an agreed scope; done should be defined by concrete acceptance criteria for that selected proposal.

索引モデルが issue の本文から書いたものです。

評価

領域
documentation, mobile, performance
issue の種類
機能追加
難易度
5/5
見積もり時間
1週間以上
活発さ
停滞
明瞭さ
説明が足りない
初心者へのやさしさ
15/100

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。