HelloZeroNet / HelloZeroNet/ZeroNet

Ideas on How Zeronet Could Improve

Ouverte
#1,423 5 commentaires 4 réactions 0 personnes assignées Voir sur GitHub
Langage dominant
JavaScript
Étoiles
18.8k
Forks
2.3k
Métriques de merge des PR
Aucune PR mergée en 30 j

Description

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

Guide de contribution

Aucun guide de contribution indexé pour ce dépôt

Piste de recherche

Aucun fichier, test ou point d’entrée n’est indiqué. Séparez d’abord les suggestions concernant les performances, les sauvegardes, l’identité, la documentation et Android, puis localisez les zones pertinentes et déterminez quelle proposition unique a un périmètre convenu ; la réalisation doit être définie par des critères d’acceptation concrets pour cette proposition sélectionnée.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Évaluation

Domaine
documentation, mobile, performance
Type d'issue
Fonctionnalité
Difficulté
5/5
Temps estimé
Plus d'une semaine
Activité
À l'abandon
Clarté
À clarifier
Accessibilité débutants
15/100

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.