Files
verdande/docs/caldav.md
T
Kristian WindandClaude Opus 5 f64b7c1f01 docs: Noter og Kalender havde ingen sider, mens forsiden lovede begge
Landingssiden reklamerer for noter og for en kalender, og dokumentationen havde
hverken en side om den ene eller den anden. Det hul blev skrevet ned i morges og
er det her.

**Noter** siger, hvad der er værd at vide, og hvad der ikke virker: at første linje
*er* titlen og udledes ved hver gemning, at arkivet og papirkurven er to
forskellige ting, at søgningen finder `grøn` når man skriver `gron` og
`keepInventory` når man skriver `inventory` — og at notekroppe ligger i klartekst i
hver sikkerhedskopi, man kan hente. Det sidste hører hjemme dér, hvor nogen står
med en note og overvejer at skrive et kodeord i den.

**Kalender** samler det, der før var spredt: gitteret, ugen som et døgn, træk der
sætter et klokkeslæt, abonnementer på ICS og webcal, og Google-forbindelsen med
det forbehold, den skal have — den er skrevet efter dokumentationen og har aldrig
kørt mod Google. `caldav.md` er nu den anden retning alene: verdandes egne opgaver
læst af noget andet.

En ting, byggeriet lærte: `</>` i inline-kode vælter Pythons html-parser på 3.9
med "we should not get here!". CI kører 3.12 og er ligeglad, men en side, der ikke
kan bygges lokalt, er en side ingen retter. Knappen er beskrevet med ord i stedet.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-20 21:50:27 +02:00

98 lines
3.5 KiB
Markdown

# Calendar and CalDAV
Two ways to get your tasks into a calendar. Getting somebody else's calendar
*into* verdande is the other direction and has its own page — see
[Calendar](calendar.md).
| | [Feed](#subscribing-to-a-feed) | [CalDAV](#connecting-a-caldav-client) | [Calendars in](calendar.md) |
|---|---|---|---|
| Direction | Tasks out, read only | Tasks out, two-way | Events **in**, read only |
| Works with | Anything that subscribes to a URL | Apple Reminders, Thunderbird, DAVx⁵ | A Google account |
| You can tick things off | No | Yes | No — an event is not a task |
| Setup | Paste a URL | Username and token | Connect, then pick calendars |
## Subscribing to a feed
**Settings → Calendar feed** gives you a URL. Paste it into whatever subscribes to
calendars.
=== "Apple Calendar"
**File → New Calendar Subscription**, paste the URL, and set auto-refresh to
every hour.
=== "Google Calendar"
**Other calendars → + → From URL**. Google refetches on its own schedule,
which can be many hours — this is Google's behaviour and nothing here can
change it.
=== "Thunderbird"
**New Calendar → On the Network → iCalendar (ICS)**.
Tasks go out as `VTODO`. Google ignores those entirely, so tasks with a clock time
are *also* sent as events — which is what makes the feed useful in the calendar
most people actually keep.
!!! warning "The URL is the password"
Anybody with the link can read your tasks. Calendar clients cannot log in, so
there is nothing else it could be. If it ends up somewhere it should not,
**Settings → Calendar feed → Rotate** issues a new one and breaks the old
immediately.
## Showing a Google calendar in verdande
Moved. Connecting a Google account, subscribing to an address, and what the grid
does with either now live on their own page — see [Calendar](calendar.md).
This page is the other direction: verdande's own tasks, read by something else.
## Connecting a CalDAV client
This is the one where ticking something off in Apple Reminders ticks it off here.
**First, make a token.** **Settings → API tokens → New token**. Copy it — it is
shown once.
Then:
- **Server**: your verdande address
- **Username**: your email address
- **Password**: the API token, **not your account password**
=== "Apple Reminders (macOS/iOS)"
**Settings → Accounts → Add Other Account → CalDAV account**, choose *Manual*,
and fill in the three fields above.
=== "Thunderbird"
**New Calendar → On the Network**, enter your email as the username and the
address as the location. It will find the collections itself.
=== "DAVx⁵ (Android)"
**Add account → Login with URL and username**. Then pick which projects to
sync.
Each project appears as its own calendar, so you can turn them on and off
individually.
!!! note "Why a token and not your password"
A CalDAV client stores what you give it and sends it on every request. A token
can only read and write tasks — it cannot sign in to the app or change your
password — and you can revoke one without touching anything else.
## What syncs
Task titles, notes, due dates and times, priorities, repetition, and completion —
in both directions.
Not sections, labels, sub-task relationships, comments or attachments. CalDAV's
VTODO has nowhere to put them, and inventing an encoding would produce something no
other client could read.
Completed tasks stay in the collection. A client that stops seeing one treats it as
deleted and drops its own record of having done it.