There was an error while loading. Please reload this page.
Calendar: syn-cal, and the three things people will hit A page for the calendar and schedule planner: CalDAV, Google through OAuth, Microsoft 365 through Graph. Weighted towards what will actually stop somebody rather than a tour of the commands. An app password is required wherever the account has two-factor, and the refusal does not always say so. A Google client id has to be created by whoever is using it, and there is deliberately no secret to copy beside it — a desktop application is a public client, so any secret it were issued would ship inside the binary. And repeating events are read from Microsoft but never written back: a recurrence flattened on the way out replaces a series on a work calendar with one occurrence, and neither side reports anything wrong. Also here: where the calendar actually lives on disk and why it is a vdir rather than a database, that accounts.conf holds no password, and what happens when two people edit the same event — both copies are kept, and the losing one is findable by its UID.