Why Journiv Doesn't Use CalDAV (And Why That Makes It More Open)
from rockstar1215@lemmy.world to selfhosted@lemmy.world on 19 Dec 14:03
https://lemmy.world/post/40440976

Hello all!

Thanks for all the interest and support you have shown for Journiv so far. If you don’t already know about Journiv:

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.

CalDAV and VJOURNAL are pretty popular in self hosted world and it has been asked few times why Journiv does not use VJOURNAL. So I wrote a blogpost about it to share my research and learning from initial days of Journiv.

If you find anything technically incorrect or have any feedback/suggestion around this I will love to hear it! I think there are lot of experts/users of CalDAV and VJOURNAL here from whom I can learn more.

Thank you.

Journiv self hosted journal

#selfhosted

threaded - newest

l3db3tt3r@piefed.social on 19 Dec 14:26 next collapse

@rockstar1215@lemmy.world OP,
Suggestions:
1) Provide a couple real use case examples for why people may be asking for these PRs.
- Probably revolve around user familiarity with their current use cases using CalDAV and friends.
2) Build an import/export adapter.

  • Link to relevant examples, resources, and/or documentation. It’s a call to action, so give readers a direction.
rockstar1215@lemmy.world on 19 Dec 14:37 next collapse

Thank you. I will incorporate this.

mhzawadi@lemmy.horwood.cloud on 20 Dec 01:15 collapse

Maybe also talk to nextcloud and see if the vjournel could be improved?

non_burglar@lemmy.world on 19 Dec 15:22 next collapse

I read the entire article,and you seem a bit prickly about caldav, but that is of course your prerogative.

I do wonder if your users are asking for caldav because their use-case make caldav a valuable translation for the rest of their digital lives… Maybe it would be helpful to understand what parts of caldav are interesting to users and what they might actually be asking for.

rockstar1215@lemmy.world on 19 Dec 15:43 collapse

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.

thelocalhostinger@lemmy.world on 20 Dec 02:20 collapse

Good blog post, thanks for sharing.

I fully agree with your points about real openness, I think this “file over app philosophy” is the way to go for every self hosted app – make it possible get the data out of there.

What I did not quite understand is why using XML is slower? Why is that – are parsers just slower in general? I do not have a lot of experience with XML, but I always thought it pretty much doesn’t matter whether you send your data via JSON or XML. And how does your JSON structure solve the problem of “content heavyness”?