this post was submitted on 19 Dec 2025
38 points (97.5% liked)

Selfhosted

53833 readers
323 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
38
Why Journiv Doesn't Use CalDAV (And Why That Makes It More Open) (lemmy.world)
submitted 3 days ago by rockstar1215@lemmy.world to c/selfhosted@lemmy.world
6 comments fedilink hide all child comments
 

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.

top 6 comments
sorted by: hot top controversial new old
[–] non_burglar@lemmy.world 19 points 3 days ago (1 children)

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 4 points 3 days ago

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.

[–] l3db3tt3r@piefed.social 10 points 3 days ago (2 children)

@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.
  1. 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 4 points 3 days ago

Thank you. I will incorporate this.

[–] mhzawadi@lemmy.horwood.cloud 1 points 2 days ago

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

[–] thelocalhostinger@lemmy.world 3 points 2 days ago

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"?