> Private by default > Your wiki and archive live on your machine. Nothing is stored remotely.

Sure, the wiki is private. However, in the process your data is being uploaded straight to an AI company. Of course local LLMs exist but that’s seemingly not supported here and I think the statement on privacy could be clearer.

fair point, I've added a disclaimer to the landing page + docs to make this clearer

you can also use opencode with local models for a fully offline setup

@dang, I think it’s fair to say this is a scam post.

Looks really well done, nice!

I also had similar concerns. Their voyager keyboard should solve that concern and I’m strongly considering using it. I’ve had their Planck EZ for maybe 2 years now (on Dvorak) and later got their Moonlander but I think it was too much for me and went back to the Planck shortly after.

Ben Vallack has a good video on the voyager[^0] and many other setups and workflows

[0]: https://youtu.be/dg2TT1OJlQs?si=vNM6fOK7ua9KCIky

Have you tried doing `find . -name '*.cstemp' -exec rm {} +`? This provides as many arguments (filenames) as possible to the executed command (rm) rather than the `\;` which executes the command per file. This provides a massive speed improvement.

I’m also interested in your usage/workflow.

I have a simple workflow I use for ENV vars. Another comment noted a script written which likely does more but I haven’t fully read the code. Here’s my simple workflow in case someone is interested.

Create a DB in MacOS keychain called envs:

  security create-keychain -P envs

Then use these shell functions:

  which get-env
  get-env () {
     security find-generic-password -s "$1" -w envs
   }

  which add-env
  add-env () {
      security add-generic-password -a "$USER" -s "$1" -w "$2" envs
   }

Then add one via:

  add-env ENVNAME SECRET

Example using it:

  ENVVAR=“$(get-env ENVNAME)” ./script.sh

this is gold, thank you

Happy it was helpful! Neglected to mention that your entry with the password will be stored in the shell history. You can prefix a space and have those commands (prefixed with a space) to be ignored in shell history. Alternative is to use `read` to pass the password in and hide the input. I can rewrite it for you if that’ll help.

There is [vulnhub](https://www.vulnhub.com/). There was another one that started with an “e” (it had Linux and code challenges too (e.g. here is the C code, exploit privilege escalation)). I remember a few years ago the site went down and a mirror was stood up under a different domain. Don’t have those links unfortunately.

Edit. Found it:

- What it used to be: https://web.archive.org/web/20180202211058/https://exploit-e...

- Mirror: https://exploit.education/

- Also can be downloaded at vulnhub: https://www.vulnhub.com/series/exploit-exercises,11/

This looks interesting. Thanks for posting!

Trilium Notes can do those very well. The first one being done with the web clipper extension.

https://github.com/zadam/trilium

Looks interesting. I'll check it out. Thanks!