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

Drafts are not private

Aperta
  • Qualcosa non va?
#64 2 commenti 0 reazioni 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
node.js, typescript
Ambito
backend, security

Direzione di ricerca

Start by mapping how MWS writes draft tiddlers and how recipes and bags determine visibility, comparing this with vanilla TiddlyWiki on Node.js. Evaluate the proposed private user bag and the [is[draft]] filter semantics before choosing an approach. Done means drafts are private to their author for each wiki and are not synced to other users before publication.

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

Descrizione

discussion enhancement

Both in MWS and vanilla TiddlyWiki on Node.js, draft tiddlers created by one user are visible to other users. This does not match user expectations for other applications, where drafts are private until published.

There is a significant privacy impact. An illustrative scenario is that I want to copy a redacted version of a private email into a tiddler. I copy the entire text of the email and enter it into a new tiddler. Then I go through it, replacing the private information with [...], and finally click "save" when I am done. The problem is that the entire text of the email will have been synced to the server before I have had a chance to make my redactions.

We did not address this problem in TiddlyWiki on Node.js because there isn't an obvious way to resolve it, and there was little impact given the single user design.

I do think this is a problem we need to resolve for MWS. One possible approach is for users to have their own private bag in which their drafts are stored. This private user bag would be an implicit even-more-topmost bag in every recipe. The semantics of writing a tiddler would become more complex: tiddlers that are caught by a specified filter (such as [is[draft]]) would be stored in the private bag, and all other tiddler writes would be pushed down to the topmost bag. A further subtlety is that users would actually need a private bag for each wiki that they edit.

Lingua principale
TypeScript
Stelle
60
Fork
17
Merge medio
4m
PR unite (30g)
1

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 TiddlyWiki/MultiWikiServer

Tutte le issue di TiddlyWiki/MultiWikiServer

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.