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.

Definitely!

Exactly for the reason you said. They don’t care about your privacy they want your verified email address to sell to the higher bidder.

Burning the midnight oil on my self hosted journal app: https://github.com/journiv/journiv-app

Import/Export are coming very soon! Here is sneak peek https://github.com/journiv/journiv-app/issues/92#issuecomment-3535960988 Built in a way that we can easily make and keep backup without fiddling with docker.

I am happy to hear that :)

Thanks! My main focus right now is simply building the product, the license doesn’t matter much if the product itself isn’t good yet. It’s always easier to move to a less restrictive license later than to go the other way, so this is the approach I’m starting with.

non-docker ways will come later. Stay tuned!

Thank you for adopting Journiv! Yes the export will be added. I do agree with you that a human accessible export is very important. I am a software engineer who knows how to make docker backups etc etc but I never do it :) I know I can set it be automated but the friction is too high to do it.

Journiv is being built for out of need and to be the solution of owning memory so it long term strategy is at it’s core. I am personally using it for all my memories with my young family so it will be devastating to lose it because of backup friction.

My plan for Journiv is:

1. 1 Click export which periodically created a static HTML site with all the entries and media. Zips it and put in local location configured by user. Since journiv run in a docker container the first phase will be putting it but not tied to docker container lifecycle. Second phase will be integration with a network file share where Journiv can automatically dump the export. Once I configure it I want it to just work not fiddle or worry about making backup. If backup fails I get some discord/telegram notification or within Journiv app.
2. Flat JSON export with media. HTML static site will allow user to see entries but JSON export is critical so that the entries can also be exported some where else if the need be.

Thank you.

You can if you can run docker on it. As of now that is the documented path. It is possible to run it without docker but that need some documentation.

Yes, mobile clients are coming. I want to have adoption and sustainability before investing time and resources in launching mobile clients. That is the reason why they will come little after. There has been lot of interest and appreciation for the app as you can see in github issues so stay tuned.

Hello, Thanks for your interest. It is possible but a little work as it will require one to have Python interpreter installed and do few things to run it. Yes, thise instructions are not there. I will add them. Do you have Python installed?

Thank you.