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.

Thank you. I am glad to hear.

Thank you. Please provide feedback on github issues.

Thank you. Please provide feedback on github issues.

Thank you. You are right. Journiv Ahead sounds way better :)

Thank you. I am glad you like it.

I can very much relate to the parent part. That is how Journiv was born actually :)

https://journiv.com/blog/the-story-behind-journiv

https://journiv.com/blog/journiv-immich-integration

Thank you. Journiv can be used by multiple user on same instance. Journiv has been built with industry grade security practices (https://journiv.com/docs/configuration/security) and support user management (https://journiv.com/docs/configuration/user-management) with role based access control. If you are using with multiple user it is recommended to use postgres as the db over sqlite: https://journiv.com/docs/configuration/database

Journiv currently does not support shared journal where you can share your journal with other users in your instance. It is a requested feature so will be added https://github.com/journiv/journiv-app/issues/62

Thank you. Please report any issues or feedback on github. This post has details on current status of immich integration https://www.reddit.com/r/immich/comments/1p7g4t7/journiv_v010beta8_this_thanksgiving_give_your/ It will be coming soon. Stay tuned!

Shared journals is a requested features: https://github.com/journiv/journiv-app/issues/62 Please upvote the issue so it can be prioritized better.

Thank you using Journiv. Please report and feature request or bugs on Github. Regarding how long term:

• It is very dependent on the support and sustainability the project gets from the community. So if you feel the project makes your life better and is valuable to you then definitely consider contributing and supporting it https://journiv.com/sponsors
• Journiv, core mission is to let users completely control their data and enable freedom to do whatever they wan’t with it. So open data formats and robust export is being built from day one. Journiv-viewer (coming soon https://journiv.com/docs/guides/journiv-viewer#exporting-to-markdown) allow users to access their journiv export as HTML webpages completely client side and standalone HTML pages. So even if you don’t have journiv instance running years down the line you have easy access to your journals. This viewer can also generate markdown export zips with frontmatter which can then be imported to any markdown viewer or note app which support markdown without any metadata loss.

The article and discussion here is about open source software which is not free software. Thats where the problem lies it is assumed that open source software has be free.

Freedom in software does not mean free software.

It’s funny how common this mindset is in the self-hosting community: “If I’m running it on my own hardware, the software should basically be free… maybe I’ll toss a tiny ‘tip’ if I feel generous.”

The logic seems to be that since there’s no ongoing server cost, the developer’s time, skill, and effort must somehow be worth nothing and that we should magically fund the entire project through some hypothetical cloud version that they themselves will never use.

It’s like showing up to a brewery with your own growler and expecting the beer to be free because you didn’t use their glass.