From 745013b93fa04e5ce45015665e615851105bca7d Mon Sep 17 00:00:00 2001 From: Lennart <18233294+lennart-k@users.noreply.github.com> Date: Sat, 4 Jan 2025 17:34:22 +0100 Subject: [PATCH] Update README.md --- README.md | 30 +----------------------------- 1 file changed, 1 insertion(+), 29 deletions(-) diff --git a/README.md b/README.md index 3ab9f3b..fcfbf17 100644 --- a/README.md +++ b/README.md @@ -46,39 +46,16 @@ These can use the faster `pbkdf2` algorithm. ## Todo -- [ ] CalDAV - - [x] Support for VEVENT, VTODO, VJOURNAL - - [ ] Proper filtering for REPORT method - - [x] comp-filter - - [x] time-range filter - - [x] good enough to use - - [ ] prop-filter - - [x] ICS parsing - - [x] Datetime parsing - - [x] Implement PROPPATCH -- [x] CardDAV - [x] Auth - current state: RustiCal should be safe against unauthenticated request, however many routes are not checked for authorization yet - [x] static authentication - [ ] Access control - [x] preparation for different principal types (groups) - - [x] authentication rewrite? (argon2 is very slow for each request) - - [x] solved through app tokens -- [ ] Web UI -- [x] Trash bin - - [x] Hiding calendars instead of deleting them - - [x] Restore endpoint -- [ ] Packaging - - [x] Ensure cargo install works - - [x] Docker image - - [ ] Releases -- [ ] Testing such that I'm confident enough to use it myself :) - [x] WebDAV sync extension [RFC 6578](https://www.rfc-editor.org/rfc/rfc6578) - [x] implement getctag [see](https://github.com/apple/ccs-calendarserver/blob/master/doc/Extensions/caldav-ctag.txt) - [ ] implement WebDAV If header -- [x] Ensure proper routing - [ ] Onboarding - - [ ] config generation + - [x] config generation - [ ] usable documentation - [ ] usable frontend @@ -93,8 +70,3 @@ These can use the faster `pbkdf2` algorithm. - We need to implement sync-token, etc. - This is important for more efficient synchronisation - iCalendar [RFC 2445](https://datatracker.ietf.org/doc/html/rfc2445#section-3.10) - -## Sync-token - -- a returned version of a resource is marked with a sync token -- the client can send the sync token to find out about changes after this sync token