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.
Guess I was always using the right combination of apps. Never had any problems with CalDAV and CardDAV. Except for frustration at outright missing support.
Nextcloud as the server and DAVx⁵ with Fossify Calendar as the client on my phone. On my laptop Kontact, but I haven't looked at that in ages, so it could be in shambles for all I know. I think I've also used Thunderbird with some plugin.
And my Fritzbox router uses CardDAV to populate the phonebook of all connected phones.
Those two are reliable as can be. BusyCal is a great app with a responsive developer and can connect to virtually anything.
As to the topic of this post, despite the above, I’m trying to move away from CalDAV and CardDAV, the latter has poor support on most mobile platforms in the way I want to use it. I also am trying to reduce self hosted platforms I maintain, which is currently a high number.
You are probably the exception rather than the rule. Nextcloud, in my experience, is the only one that seems to work fairly well. Just look at the Issues on Github for apps that try to use CalDAV.
You should look at JTX Board. It's associated with DAVx5 and they do the vjournal and vtodo standards. They have a list of services that support it.
https://jtx.techbee.at/sync-with-davx5
zero-hassle setup in Thunderbird for both of those things
DAVx on Android works seamlessly for calendar and contacts Sync
Fossify calendar to view, edit calendar
default contact app for contacts
Infcloud as a web frontend for Radicale. Not pretty, but absolutely functional (and I hardly ever need it thanks to Android calendar app / Thunderbird)
Haven't tried todo lists yet, but I would imagine they are similarly hassle-free.
The only annoyance I have is that DAVx is required at all, but I'd suspect that's an Android/Google issue? IDK.
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.
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
Never had an issue with caldav and cardav. Maybe you are using broken servers or clients?
Even notes can be done efficiently on those standards...
But, hey, I am using only FOSS server and clients, maybe you referring to proprietary ones? You know, those who are mare by vendors who have no interest in interoperability?
I have to join the choir, what do you mean dying and doesn't work? If proprietary apps don't support it, it's just because it's one of the best ways to lock people in.
Google etesync. It has everything you need and light weight and written in modern languages, python. It even supports e2e encryption and open source hosting option. You are welcome.
zero-hassle setup in Thunderbird for both of those things
DAVx on Android works seamlessly for calendar and contacts Sync
Fossify calendar to view, edit calendar
default contact app for contacts
Infcloud as a web frontend for Radicale. Not pretty, but absolutely functional (and I hardly ever need it thanks to Android calendar app / Thunderbird)
Haven't tried todo lists yet, but I would imagine they are similarly hassle-free.
The only annoyance I have is that DAVx is required at all, but I'd suspect that's an Android/Google issue? IDK.
Probably because there is no interest in open standards. I find ical is more a file format than a transport format, an actual standard protocol around it would be great. Although I suspect that the "transport" was always supposed to be email.