Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Optional end-to-end encrypted sync

Aperta
  • Qualcosa non va?
#55 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

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
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
csharp, sqlite
Ambito
database, desktop, security

Direzione di ricerca

Read ROADMAP.md and AGENTS.md first to confirm the product constraints, then review the existing .zip export and v1.4 mirror behavior. Settle transport, merge rules, key handling, local-only data, and 1.0 schema compatibility; done means recording dated decisions in ROADMAP.md and adding a milestone with its own checklist.

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

Descrizione

enhancement later

Keep one library on several computers, with nothing readable leaving the machine.

ROADMAP.md rules out any sync that isn't optional and end-to-end encrypted, and it rules out accounts. Today prompts move between machines as .zip exports, and v1.4's mirror will give a one-way copy in plain files.

What has to be settled before this gets a milestone

  • Transport. The only network code allowed today is the Velopack update check (AGENTS.md). The approach that keeps that rule writes encrypted changes into a folder the user already syncs (Syncthing, Dropbox, OneDrive, iCloud Drive), so Prompuff opens no connection of its own. A Prompuff server would mean accounts, which are not planned.
  • Merging. Two machines can edit the same prompt while apart. Versions make this easier: both edits can become versions, with the newer one current. What happens to metadata (favorite, rating, tags, collection) and to deletes needs a rule too.
  • Keys. Where the key lives, how a second machine gets it, and what happens when it's lost. Without the key the synced copy is unreadable, and the local library stays safe.
  • What stays local. Remembered values are never exported, so by default they don't sync either. Settings could go either way.
  • The 1.0 promise. A synced library is still a library that every later version opens. Sync can't change the schema in a way 1.0 can't read.

Done when

  • The settled answers are a dated decision in ROADMAP.md, and this issue gets a milestone with its own checklist.
Lingua principale
C#
Stelle
0
Fork
1
Merge medio
1h 51m
PR unite (30g)
13

Preparare l'ambiente

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 hazeliscoding/prompuff

Tutte le issue di hazeliscoding/prompuff

Issue simili

Altre issue su C#

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.