It's clear that CalDAV doesn't function consistently across devices (and does seem to be dying as a standard). If you work across different devices/OS it's virtually impossible to get things set up seamlessly. Companies and developers of task apps seem happy to create silos and not look at interoperability.

If you want to self-host, it's too hard to do this and you really are limited to a tiny number of options.

you are viewing a single comment's thread
view the rest of the comments

[–] ComradeMiao@lemmy.world 1 points 1 week ago (1 children)

Which didn’t it work on? I got Baikal to work on all but I needed to edit dns for it specifically. Nextcloud caldav doesn’t work with iOS to my knowledge.

[–] tenebrisnox 1 points 1 week ago (2 children)

I have Nextcloud CalDAV working on iOS (the trick is to set up calendar and tasks separately). I can’t get Baikal Calendar to sync on ios.

This is what I was trying to get at: setting up calendar and task SHOULD be straightfoward and work across devices and OSes. It’s not.

[–] fry@lemmy.sdf.org 2 points 1 week ago* (last edited 1 week ago) (1 children)

iOS used to be an absolute pain in the ass. Had to scratch my head for several days a few years ago. I believe it was iOS 15. Forcing SSL and self-signed certs with some odd flags finally did it but it was not straightforward. Good luck reading logs on an iPad. Unfortunately I don't remember any specifics.

Other than that I've had zero issues with Baikal for the last couple of years. Roughly 15 devices (iOS, Android, Windows, Linux), and 5 users each with multiple calendars, tasks, contacts, notes etc. and everything just works. DAVx is excellent if you use Android as CalDAV isn't natively supported for some reason.

But I get your point. CalDAV as a standard has always felt a bit... Janky? It never left the early 2000s. So setting up a CalDAV server in 2024 isn't particularly difficult but everyone wants their own implementation. And your server/client combo probably require you to find some obscure forum post from 2009 and reading the man pages several times before you find that one specific fucking legacy parameter in some config file that has to be set.

You could always set up your own Exchange server though if you're a true masochist.

[–] tenebrisnox 1 points 1 week ago

And your server/client combo probably require you to find some obscure forum post from 2009 and reading the man pages several times before you find that one specific fucking legacy parameter in some config file that has to be set.

100%

[–] ComradeMiao@lemmy.world 1 points 1 week ago

True!