Does anyone know why there’s no desire to see a working standard (protocol) for calendar/tasks?
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.
Huh?
I’ve been running radicle for a while to sync my desktop and mobile calenders without any hiccups ever.
I also don’t get this. I run baikal and sync my server, Linux PCs, and iPhone. Calendar, tasks, and contacts
I have tried hard to get Baikal to work across devices and had to admit defeat (works on some, not on others). I am running CalDAV most successfully using Nextcloud.
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.
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.
True!
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.
100%
Another one selfhosting contacts, calendar, notes and so on with that non-interoperable protocol.
And for the shake of honesty I need to say that while doable it is true that the situation could be highly improved with a lot of non standard stuff that private apps are implementing outside of the standard compliance
What’s your set up with CalDav? What devices do you run it on?
I use the tchapi docker image for the caldav server (die to the LDAP support for the user Auth) and davx5 for the android integration.
In Desktop thunderbird already have a native integration and with iPhone is also working fine.
No problems so far in almost a year, they work reliable and smooth. The only point I somehow miss is the lack of push notifications from the server to the devices, but it is not a deal breaker from me