I love the concept of apple’s in house journal app which allows you to create dated posts that include text, videos, and photos. I hate the idea of writing anything private in a journal hosted by apple as well as the fact that apple could discontinue at any time. Any ideas on a way to achieve something similar in a clean interface (a long word document wouldn’t cut it) without the middle man? A dedicated un-networked device even?
Could just skip the hosting step and use Joplin. Has a lot of backends built-in, and encryption support at the app so the contents are encrypted before they leave the device.
Great suggestion in !selfhosted@lemmy.world…
You can easily use it with Nextcloud, to name one example. So yeah, it’s a good suggestion.
I was referring to the “just skip the hosting step” part. You may be right about Joplin but you’re wrong about the suggestion.
Logseq! Right now, you can only self host the database and sync it with Syncthing for example, but the dedicated sync feature is currently in beta and will be self hostable afaik.
This is where I’ve landed too.
- self hosting is dead simple.
- so no syncing to be done across devices.
- posts are saved as plain text files (in markdown).
- so you can do what you need with them.
- supports multi users, SSO, cloudflare R2 for storage if you need those things.
As a Logseq user, that looks pretty much like what I wanted it to be. Lean, self hostable, no weird feature bloat. I’ll take a closer look!
I am also on the hunt for a good self hosted journal for life journaling (not note taking like some other links in other comments). Here’s what I am trying to replace:
I’ve been using DayOne without subscribing. I’ve had a lot of ups and downs with DayOne over the years, but I’ve finally found a way to use it with the free plan that I’m happy with, that kind of fits into a self hosted setup. I journal on my phone, and also in my laptop. I love that it captures location, weather, music, step count, and activity. After a month or so, I export the journal entries as json, and put them into a private hosted view and search interface that I’m in the process of writing in Python.
The DayOne journal data does not need to be synchronized to the cloud, and can even be encrypted by you, but who knows how much of your metadata is sent to them.
This setup is far from ideal because it’s not entirely private (metadata is probably leaking to the company), but it does have solid data liberation, is free (as in beer), can be encrypted, and the format is just json so it’s easily inspectable and transformable. It’s been working fine for me for several years (I actually have over a decade of DayOne journal history). It’s kludgy and not turnkey, so definitely not for everybody.
Side note for anybody who is using DayOne: I highly recommend making sure your backups are working, and saving a copy of the backup periodically. I store my exported entries in git and over the years have observed lots of instances of corrupt data due to sync problems with their sync server, which is another reason I want to move to self hosted.
