this post was submitted on 13 Nov 2024
48 points (96.2% liked)
Open Source
31354 readers
472 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
- !libre_culture@lemmy.ml
- !libre_software@lemmy.ml
- !libre_hardware@lemmy.ml
- !linux@lemmy.ml
- !technology@lemmy.ml
Community icon from opensource.org, but we are not affiliated with them.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.
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%
True!