Yes, it is fixed in 1.3.4-develop now.
georgehrke from nextcloud asked how to add the server default option. Can you please answer him? I couldn’t find an anwser online but i guess the server should set it itself if no privacy class is set, correct?
@jgold “server default” is
ACCESS_DEFAULT (https://developer.android.com/reference/android/provider/CalendarContract.EventsColumns.html#ACCESS_DEFAULT). It only exists on the client and thus can’t be defined on the server. Currently, DAVdroid interprets “server default” as "don’t send any
CLASSIFICATION", which is the same as
CLASSIFICATION:PUBLIC because it’s the default value [https://tools.ietf.org/html/rfc5545#section-184.108.40.206].
I think it would be a good idea to make this setting adjustable on the configuration view:
It would also indirectly enable users to choose between public, confidential and private.
What do you think about that?
@jgold Which setting do you mean?
@rfc2822 the ACCESS_DEFAULT setting
@jgold I still do not understand what you mean …
Do you mean that a user should be able to set a calendar to “ACCESS_CONFIDENTIAL” or so inside the DAVdroid account?
I thought that the user should be able to choose in the settings what Davdroid should do if an event has the privacy set to ACCESS_DEFAULT - like a dropdown menu where i can set what default should mean (public, private, confidential). At the moment, default is basically the same as public, right? But if you could map default to private or confidential, then every event send to the server would have class: private or confidential.
After a nice cooperation with TapirApps they can now offer support for
CONFIDENTIAL in their aCalendar+ Android app.
@jgold Does it work for you as expected?