New Privacy and Security Documentation

I discovered recently that there are no useful results when searching tiddlywiki.com for “privacy” or “security”. Given the importance of these topics I am preparing a Pull Request that adds a new section giving basic information about privacy and security when using TiddlyWiki. There is also a new badge for the home page to advertise it:

The goal is to give users good quality pointers to trusted sources of information, and suggest strategies for using TiddlyWiki with minimal trust in external entities.

The pull request is #8746, and there is a preview at https://deploy-preview-8746–tiddlywiki-previews.netlify.app

Suggestions and thoughts are welcome.

11 Likes

This is a great idea. Some feedback:

  1. There’s a small typo: s/stoerd/stored/

  2. Unless the goal is to exclusively offer a general, ten thousand feet altitude perspective, might be worth explicitly linking related topics, to give a first time reader pointers for further research of practical solutions that the TiddlyWiki ecosystem can offer. I’m thinking about:

Thank you @vuk I’ve implemented your suggestions in this commit. The preview will be updated in a few minutes.

1 Like

7 posts were split to a new topic: Enable AES-256 Encryption for TW

Thank you to all those who helped with feedback (including over at GitHub). I’ve now merged these changes to tiddlywiki.com. Further improvements are welcome.

Great start. Here is some feedback as requested:

The article assumes some amount of TiddlyWiki knowledge, but at least on my monitor, it appears above the fold :information_source:. This means a privacy-conscious visitor may visit it first, without the requisite background. The main issue is that it doesn’t introduce the two types of configurations it discusses (single file v. node)

This line upfront is also misleading.

The key is that TiddlyWiki is just a file, and so everything that users may have already learned about how to keep documents and images private can be applied to TiddlyWiki.

You can keep most of it, but it would be more accurate to reframe the opening to

‘As standard, TiddlyWiki is a single file’

To address this issue without rewriting the whole text:

  • The introductory paragraph must distinguish between the single file and node setups
  • Add some [[internal]] links when these concepts are introduced.
  • Put the two headings of ‘Single file configuration’ and 'Node.js configuration in a two-column layout within the tiddler.

This would give something like

Single file configuration                         Node.js configuration
Lorem ipsum...                                    Dolor amit...

But I appreciate this may not be straightforward!

Finally,

  • I recommend making the external link to the EFF’s website inline, within the text.

Thank you @yan. I’ve made a few changes here to try to address your points: