• 1 Post
  • 17 Comments
Joined 3 years ago
cake
Cake day: June 6th, 2023

help-circle
  • I’ve not heard of those, but to me this is a competitor to the much more ubiquitous Obsidian. Which works great, and has a whole community of support, but is not open source.

    Personally, I don’t need my notes app not be responsible for syncing across devices either. I already have that for other file types (photos, media, etc).

    I’m not against these features being added, but this app is young, afaik it’s one person writing it, so I’d rather see their time be spent making the note taking experience as good as it can be.

    I also generally wouldn’t trust one person to properly audit the security of the networking and encryption features. If I wanted those features, I’d still give the community time to peruse the codebase.


  • I think it makes sense to handle this at a lower level. After using other notes apps, the thing I want is for it to not have some arbitrary opaque file hierarchy that locks me into it. I want a plain dir of .md files, some resources they link to, and that’s it. If I want disk encryption, there are solutions for that. I can use something like LUKs to encrypt my whole drive, or even just the notes directory.

    For android, afaik everything uses disk encryption by default.

    The unix philosophy is do one thing really well. We don’t need a note taking app that also handles encryption.






  • I have an edge router and switch, and two unifi APs. All accounts running locally. Works fine for my uses, though I think if I had it to do over again I’d investigate pfsense or opnsense. Not sure about hardware tho.

    since it uses ZFS I don’t know it would be good for home use

    TrueNAS is all I’ve used for my home for the better part of a decade. It’s been fine, what is your concern?


  • I feel like if that’s something you’re doing, you’re using containers wrong. At least docker ones. I expect a container to have no state from run to run except what is written to mounted volumes. I should always be able to blow away my containers and images, and rebuild them from scratch. Afaik docker compose always implicitly runs with --rm for this reason.




  • Step 1 is to do everything inside your network with data you don’t care about. Get comfortable starting services, visiting them locally, and playing around with them. See what you like and don’t like. Feel free to completely nuke everything and start from scratch a few times. (Containers like Docker make this super easy).

    Step 2 is to start relying on it for things inside your network. Have a NAS, maybe home assistant, or some other services like Immich or Navidrome. Figure out how to give services access to your data without relying on them to not harm it (use read only mounts, permissions, snapshots, etc.)

    Step 3 is to figure out how to make services more accessible away from home. Whether that is via a VPN, or something like tailscale, or just carefully opening specific ports to specific secure and up-to-date services. This is the part you’re feeling anxious about, and I think you’ll feel less anxious if you do steps 1 and 2 first and not even think about 3 yet. Consider it its own challenge, and just do one challenge at a time.