makiolaj
1a0041f8fa
Every client here is built with followRedirects(false), because DavResource requires it — so the DAV calls follow by hand and the two OCS/JSON ones followed not at all. A Nextcloud that canonicalises host or path with a 301 (apex to www, a trailing slash, a proxy) therefore turned the login flow's start into a bare failure, its poll into an unexplained SERVER_ERROR *after* the password was minted and the flow row deleted, and the app-password revocation into the "attempted, and did nothing" outcome its own KDoc exists to prevent. All three go through one follower now, which re-issues the method and body — both routes answer 405 to a GET — bounds the hops, and applies the same downgrade rule DavResource does. The home set was resolved against the URL the principal PROPFIND was aimed at rather than where it landed, though followRedirects rewrites that location in place and probe() twenty lines above reads it back for exactly this reason. A permanently moved principal answers a relative href, which resolved against the old base names a path that 404s — and a perfectly good account reports that it holds no calendars. And a failing multiget batch discarded every batch before it: the runCatching wrapped the whole loop rather than one request, so a 500 on batch seven of ten threw away two hundred parsed resources and answered Result.failure, and the collection re-downloaded everything next run. It now keeps what it has and lets the unasked hrefs fall out as missing, which the engine already counts rather than acting on. A run that got nothing at all still fails.
Agendula
A modern Material 3 Expressive task app for Android.
Keeps your tasks on your device, or on top of a tasks provider you already use.
Open standards, no account required.
Agendula is the task-list sibling to Calendula.
Where Calendula is a pure front-end over Android's CalendarContract, Agendula
keeps its own store, designed around RFC 5545's VTODO — the same tasks DAVx5
(and SmoothSync, DecSync, …) sync out of your CalDAV server. It can also read and
write a tasks provider you already have, for anyone already syncing that way.
The name rhymes with its sibling on purpose: Agendula is agenda — Latin for
“things to be done” — given Calendula's -ula ending. Calendula keeps your days;
Agendula keeps your to-dos. (A Calendula flower head is botanically a cluster of
many small florets — so the two apps are florets of one bloom.)
Where your tasks live — your choice
| Where | Sync | Needs | |
|---|---|---|---|
| On your device (default) | Agendula's own database | none yet — CalDAV sync of our own is planned | nothing. No account, no permissions, no other app |
| In a provider you already use | OpenTasks or tasks.org | whatever syncs it for you — DAVx5 and friends | that app installed, and its read/write permission |
Agendula's own store is an ordinary app database — nothing is published to other apps, so there is no authority to clash over and no permission to grant. It coexists with OpenTasks rather than replacing it: installing one never breaks the other, and if you already sync through a provider, that keeps working exactly as it did.
Recurring tasks are expanded per RFC 5545, and everything the schema does not model is round-tripped verbatim rather than dropped — so passing your tasks through Agendula does not quietly lose fields a server sent.
Your tasks are exportable as standard iCalendar .ics files at any time, because
data you can't take with you isn't really yours.
Status: backend complete, UI catching up. Storage, reads and writes, smart-list filtering, a self-scheduled reminder engine, and export are built and unit-tested. The Material 3 Expressive screens are being built on top, one at a time — the storage-mode picker and export screen are not there yet. See
docs/ROADMAP.mdfor status,docs/ARCHITECTURE.mdfor how it's built, anddocs/STORAGE-AND-SYNC.mdfor why storage works the way it does.
Sync sources (by design)
In external-provider mode Agendula works with anything that writes to that provider — DAVx5 (CalDAV), SmoothSync, CalDAV-Sync, DecSync CC, or any Android sync adapter — because it builds on the provider, not on any one sync app. Google Tasks / Microsoft To Do are out of scope by design (proprietary; they would mean owning a sync stack). Open standards — CalDAV / iCalendar / DecSync — are the lane.
Translations
Agendula ships in English so far, and would like not to. Translations are managed on a self-hosted Weblate, and partial ones are fine — an untranslated string simply falls back to English.
No coding needed: register on the Weblate server, pick (or request) a language, and translate the strings in your browser. You can also reach this link in the app from the top of Settings → App language.
License
MIT — see LICENSE.