Pinning should have a better UX for any time scale it takes to pin, and pinning intentions should be persisted between reboots

Aperta
#2,385 2 commenti 1 reazione 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Da chiarire
Stato di attività
Ferma
Stack tecnologico
javascript
Ambito
desktop

Direzione di ricerca

Inizia tracciando il flusso attuale del pinning in IPFS Desktop e verificando come le richieste di pin sopravvivono ai riavvii dell'applicazione. Definisci gli stati, il comportamento della coda in background e in foreground, la gestione dei retry e le notifiche di completamento descritti qui; il lavoro è completato quando i pin ritardati, di grandi dimensioni e non disponibili rimangono visibili e segnalano infine il completamento senza perdere l'intento dell'utente.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

effort/weeks exp/wizard kind/discussion kind/enhancement need/analysis need/community-input need/maintainers-input P2 topic/design-ux

This is a feature request for IPFS Desktop as I currently see this problem;

Pinning something falls either under three different "time scales".

The first is that the file is already locally downloaded, and pinning is nothing more than verifying that the file exists, this usually takes under a second.

The second is that the file is not completely downloaded, or not downloaded at all, but that it is easily accessible over the network (i.e. DHT announcements are out, content is easily findable, and its relatively small, only a few MB or so), this'd take a few seconds, but nothing more.

The third is that the file is not findable, the file is either not announced, the peers aren't reachable, or otherwise the pinning process takes an extra amount of time to complete, usually for multiple GB of data.

The last two is what IPFS Desktop does not feel ready for, the pinning checkmark feels like it has a roundtrip time of exactly the amount of time it takes to press it, and nothing more.

For pins that take a second more, the pinning state should be communicated clearly to the user, and replaced with a 'pinned' icon when it is done.

For pins that are stalled or take an incredibly long amount of time, the request that the user wants to pin this file should be persisted, so that they can simply tell IPFS "hey, i care about this file, find it, no matter how long it takes", that is what i expect it to do, and i've had multiple times where after a restart, IPFS Desktop forgot i wanted to pin the file, even ones that were actively downloading.


I'm currently using ipfs-cluster, which has this behaviour, where pin add tells it to queue up the pin, and try pinning it later, retrying other pins in a round-robin fashion ad infinitum, until one of them succeeds pinning, leaving others to take the place in the queue.

It has a relative prioritisation system, where a new pin is more eligible for the active-pinning queue than older pins. This is relatively annoying as it takes the timeout phase (24h by default) for the new pin to start getting pinned, so IMO a "background" and "foreground" queue should be created for IPFS Desktop to achieve a better user experience.


Pinning this way (in the background, in a long-form) should also generate notifications when the pin is complete, so the user can be somewhat aware when such a thing is finally done.

Lingua principale
JavaScript
Stelle
6.6k
Fork
908
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di ipfs/ipfs-desktop

Tutte le issue di ipfs/ipfs-desktop

Issue simili

Altre issue su JavaScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.