Anything which is metadata to a media is too limiting. I don’t see journaling to be something as a metadata to a media but journal entry where media are linked as a reference.

To keep them coupled you have two option in Journiv: Link mode where coupling is lose if you lose the media in Immich you lose it in Journiv. Copy mode: Coupling with redundancy as Journiv makes a copy.

Journiv is not a journaling tool for Immich but a standalone journaling solution with many features and has a integration with Immich for convenience to user.

My thought is that in 20 years time, what software and data standards are going to be around? Archival tends to work best when its simple and resilient.

I have similar thoughts as well that is why Journiv exists so I own the data and can do whatever I want on my terms. Some background:

• https://www.journiv.com/blog/the-story-behind-journiv
• https://www.journiv.com/blog/why-journiv-doesnt-use-caldav
• https://www.journiv.com/docs/guides/journiv-viewer

Thanks

Thank you. As an Immich lover it is an honor for Journiv to be considered similar to it :)

I have similar kinda story and thats how Journiv was born: https://www.journiv.com/blog/the-story-behind-journiv

I wanted to capture all the stories/thoughts behind the pictures to some day maybe pass it down to my kids but I didn’t want to put all this info on some third party server. I looked a lot for self hosted journal kind of solution but didn’t find anything beside note taking apps (plenty of them). So finally decided to take matters in my hand. Immich integration was a primary use case for me so everyday/week I can add snippets notes to pics to keep memory of those pics and what I was thinking, what was happening, what did the kid said/do etc etc.

Hello, no not as of now. Immich integration was done because I am a huge immich fan and user and I wanted to journal around my immich library media. A lot of immich community member also wanted it. I have never used Photoprism so I am not sure what it is and how it works. But if there is enough demand for it then it can be added. When I built immich integration I made it modular so I can plugin other media provider in future as needed.

Daylio import will come. The blogpost above has done a lot of hard work of decrypting their obscurely secure export :) The larger lift for Journiv is building a native activity tracking system this needs db schema design update and changes. This is what I will be working on very soon once that is done export from Daylio will follow.

Hello, yes it is.

Hello, Encryption at rest is on roadmap. End to end encryption is very time intensive to build correctly and would be an overkill for a large percentage of users who are self hosting Journiv so as of now there are no plans for e2e.

Thank you. Please let me know your feedback. I am not sure what IBAN is but yes I do have support page: https://www.journiv.com/support and github sponsors: https://github.com/sponsors/swalabtech

Thank you :)

Thank you.

Nice. You can just follow this doc and it will be smoother. https://www.journiv.com/docs/installation/docker Celery beat is still missing from the compose. Journiv uses that for scheduled tasks. Also if you like Journiv and plan to use it I will recommend moving to Postgres because that is preferred DB and many upcoming features will utilize pg vector etc.

Thanks. Yes, I am hoping the support grows and the project becomes sustainable to grow. Sure, anywhere is fine.

No that is not supported. Journiv is not a note taking app and a journal app and the focus is to build it as a journal app even if it limits its target audience. There are many note taking apps out there and many in self hosted world. My personal favorite is Obsidian which I am happy with.

Daylio has been requested before (and I just saw it has 4 upvote, so I am guessing its pretty popular ?) https://github.com/journiv/journiv-app/issues/58

Daylio kind of mood tracking i.e. extensive with custom mood and with activities will come soon.

Import from Daylio is possible although I am not sure how much the demand is. The github repo has lot of import from request from different apps and import does take a lot of time to build as most apps have obscure formats and nuances to deal with or on purpose don’t support simple portable formats to lock down user data. For example see the circus one has to go through to get meaning from Daylio export: https://www.joelotter.com/posts/2022/01/daylio/

Congrats on liberating your memories and thoughts. I look forward to your feedback.

Can you clarify the export issue you are seeing or please report it on github? The export/import has been working well. I am guessing you might have tried it out with quickstart docker compose or Synology NAS guide from mariaus hosting which does not have complete docker compose i.e. it is missing celery-workers container which are needed to create import/export jobs and run them async. Couple of users tripped on this so I will be improving the error message to specifically say they need to run complete stack right not the error message is very cryptic low level detail which is hard for anyone to understand what went wrong.

That sounds like a fun project. I did initially do some research in VJOURNAL but found it rather limiting for all the stuff I want to build in Journiv. I wrote a blogpost about it earlier: https://www.journiv.com/blog/why-journiv-doesnt-use-caldav The application is cross platform so it work as PWA and you can use it as mobile devices as PWA without any issues. Many Journiv users are already doing so. Native mobile apps are ready and will be coming soon once the project becomes sustainable to cover the development cost and expenses around it: https://github.com/orgs/journiv/discussions/184#discussioncomment-15180557

Hello, Sorry for the late reply. I do not use lemmy that often and only saw this now when I came here to post about new release. You’re right to call that out. I made an oversimplified claim. Let me clarify, XML vs JSON performance is nuanced:

1. Parsing speed: JSON is generally faster to parse than XML because:

• Simpler syntax (no opening/closing tags, no attributes vs elements decisions)
• Less data structure overhead
• More direct mapping to native data structures in most languages

2. Payload size: XML is typically more verbose due to:

• Opening and closing tags
• Namespace declarations
• Attribute syntax
• This means larger network transfers

However:

• Well-optimized XML parsers can be very fast
• The difference matters more for high-volume APIs than occasional journal syncs
• For large text content (like journal entries), the actual content dwarfs the format overhead

In CalDAV specification journal is supported by VJOURNAL which is not specifically CALDAV.

My understanding so far is that no one specifically uses VJOURNAL due to lack of its adoption and features but have a feeling it is a standard which should be followed based on the fact how dominant CALDAV is but VJOURNAL is not CALDAV and is not same. The post goes in details about limitation and issues with VJOURNAL.

Thank you. I will incorporate this.