privatize VS Perlite

I partially encrypt/decrypt a file based on the presence of special HEREDOCs (ie <The tool is still a WIP as it isn't portable between machines -- https://github.com/higgins/privatize

more on it here: https://encapsulate.me/writing/Privatize.html

Yes!

I keep a daily log tracked in git. All of it public although some information is encrypted with my privatization tool (https://github.com/higgins/privatize).

The log itself is a simple org file but I parse and render it in html here so that I can share important event dates (eg: my wedding) with my family and friends.

Here is what I did yesterday:

ooo, good call out. thanks!

currently i only have one warning in place if I forget to close there heredoc: https://github.com/higgins/privatize/blob/main/index.js#L168

but could add some more error checking. added to TODOs: https://github.com/higgins/privatize/commit/9696f30576897898...

https://github.com/higgins/privatize

When added to a git repo, it will automatically transparently encrypt/decrypt files you want privatized.

For example if you configured your repo to privatize the file `example.txt`, you could write:

```

there is a self hosted version here https://github.com/secure-77/Perlite

yes, there is a self-hosting option called perlite. Here is a link: Perlite on GitHub

I share a folder between my Obsidian vault and the folder PineDocs uses with Syncthing (because the machine that runs PineDocs is not my laptop), so as soon as I save my files the site is immediately updated, but PineDocs was not designed with Obsidian in mind, the links work but not the advanced features Obsidian offers.

On the other hand, Perlite [1] is (I never really tested it but it looks cool) designed with Obsidian in mind so maybe it supports more features.

[1] https://github.com/secure-77/Perlite