Hi Reet,

I've been using TW encryption for years and it's been very reliable. I use 
a single-file TW for everything (currently 5.2 MB) with approx. 2k 
tiddlers. I'm not sure how encryption works when you use one of the other 
access methods (bob/node.js etc.)

I reckon it will add some overhead on startup: once you've provided your 
password and hit enter you'll wait longer until your TW is decrypted and 
loaded the larger it is and the slower your device. But for me encryption 
has been a critical feature since I use the single file for everything and 
this additional wait time is well worth it.

You may read about the encryption 
<https://tiddlywiki.com/static/Encryption.html> standard used by TiddlyWiki 
in the documentation. The library used by the core is called Stanford 
JavaScript Crypto Library 
<https://tiddlywiki.com/static/Stanford%2520JavaScript%2520Crypto%2520Library.html>
.

You might also be interested in this discussion on this group:
https://groups.google.com/forum/#!topic/tiddlywiki/VRGzXzxSYEA

If you're concerned about data corruption, probably the single best measure 
against data loss is to make frequent backups. But again, I would never 
expect it to happen because of encryption.

BTW, there's also a plugin allowing you to encrypt single tiddlers only, 
though I don't personally use that.

I hope this helps.

Enjoy!
Hubert

 

On Monday, 18 May 2020 03:09:26 UTC+1, Reet Pandher wrote:
>
> Have you tried the encryption feature of the tiddlywiki?
> If yes then has it been reliable for you? Reliable as in Has it caused any 
> sort of corruption or loss of data even when you know your password? Does 
> it work properly even when you have large amounts of data stored in it? 
>
> Thanks!
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/d1e04dd1-f59a-480c-a857-8e20e1b08bae%40googlegroups.com.

Reply via email to