Hello everyone!

Journiv is a self-hosted private journaling application that puts you in complete control of your personal reflections. Built with privacy and simplicity at its core, Journiv offers comprehensive journaling capabilities including mood tracking, prompt-based journaling, media uploads, analytics, and advanced search. All while keeping your data on your own infrastructure.

Journiv v0.1.0-beta.11 is out with

  • Day One Import - Own your data forever and import them from Day One
  • Location and Weather - Attach location and weather to your entries
  • Tags Management - Complete Tag management with tag based filtering and tag analytics
  • Auto Save - Never lose your entry in draft mode
  • Media de-duplication: Attach same media to multiple entries/journal without consuming more space.
  • Journiv Plus: Gives supporters additional features as a thank you for supporting the development of Journiv. Thanks to Kavita developer majora2007 for providing some guidance on this.
  • and many more features and bug fixes.

The Journey Ahead

Journiv is in active development, with a fully functional backend, a web frontend, and mobile apps launching soon. It is self-hosted, and designed to be your companion for decades.

Journiv is being built because our memories deserve to be ours, forever.

Learn More

    • rockstar1215@lemmy.worldOPEnglish
      1·
      3 days ago

      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.

      • Rogue1633@discuss.tchncs.deEnglish
        1·
        1 day ago

        ok thanks for the reply. I understand that this would take very much work but I wouldn’t be comfortable hosting something with potentially very sensitive data on a remote server where the admins could see the files. Unfortunately hosting on my Raspberry Pi at home isn’t possible because of this error when starting the docker containers (which seems to be a Raspberry issue).

        What is the difference between your encryption at rest and disk/file system encryption? Would the use case be that someone stealing the server couldn’t access the files?

        • rockstar1215@lemmy.worldOPEnglish
          1·
          1 day ago

          That makes sense. As of now I have not considered the VPS approach you mentioned but only thought of self hosting but I can see how in VPS world it is not safe. Encryption at rest can be obtained by various means

          • Have the disk encrypted like you said.
          • Have the db encrypt by a admin provided secret but in this case all users of instance share that secret and admin can technically decrypt other user data.
          • Have the app do encryption based on user provided password. This gives per user secret and encryption. So encryption at rest will be something among this preferably (3) one.