Hello, yes it is.

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.

And I meant that what you to say is valuable enough to write :)

Seems pretty valuable to me. If you do write this for a month or year with Journiv’s analytics you can find out

• How much gas you can save overtime
• All the names you call yourself
• What do you forget most :D

I am glad it is serving it’s purpose. Notification/reminders will come soon to Journiv which will help with forgetting to write :)

Thank you. Please provide any feedback on github issues.

Yes location, weather will be coming soon. There is existing feature request opened by the community for this. I am not sure what do you mean by routes. Can you provide more details as what such a feature will look like?

They don’t have to. As long as Obsidian or any tool is working for someone then that is what they should use.

But for many including me Obsidian is not a solution for journaling although I extensively use Obsidian for note taking. You can read why here

• https://www.reddit.com/r/immich/comments/1onj6ay/journiv_011beta_is_out_a_selfhosted_privacyfirst
• https://journiv.com/blog/the-story-behind-journiv

Thank you. Looking forward to your feedback.