Drafts are not private

Abierto
  • ¿Algo no está bien?
#64 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Estancado
Stack tecnológico
node.js, typescript
Área
backend, security

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
TypeScript
Estrellas
60
Forks
17
Merge medio
4 min
PR fusionados (30 d)
1

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de TiddlyWiki/MultiWikiServer

Todos los issues de TiddlyWiki/MultiWikiServer

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.