"only show your own" has no effect at all (at least when using a Nextcloud account)

[DJCrashdummy]

Problem scope

• I'm sure that this is a DAVx⁵ problem.

App version

• I'm using the latest available DAVx⁵ version.

Android version and device/firmware type

Android 15 (LineageOS 22.1)

Steps to reproduce

1. have some shared calendars in your Nextcloud account
2. setup this Nextcloud account in DAVx5
3. see all calendars in DAVx5 (even the shared ones with the owners username in () beside the calendar name)
4. activate the "only show your own" (that's my translation) in the 3-dot-menu
5. even after manually refreshing the list and syncing, nothing changes.
6. in the details view of every calendar the owner is stated correctly, no matter if it is me or someone else.

Actual result

unfortunately nothing changes.

Expected result

the calendars owned and shared by an other user should not be shown in the list.

Further info

it seems that the same is true for address books... since i don't have shared address books i can't 100% confirm, but Nextclouds system address book "Accounts" also stays visible although the owner is correctly shown as "system" in contrast to my username at the other ones.

[rfc2822]

There are unfortunately multiple methods to detect "personal" collections. To support specific services, DAVx5 currently doesn't user the DAV:owner field, but considers collections which are in a homeset of the user as "personal". Other resources that are found by service detection, for instance in a homeset of a group that the user belongs to, are not considered personal.

The UI switch toggles the personal flag, as explained above.

I agree that this is somehow confusing. We could in theory check whether this method is still needed for these specific other services or we could replace it completely by DAV:owner-based logic. But I'm afraid that at the moment there are too much other things.

[DJCrashdummy]

this is indeed really confusing! ...else i wouldn't have classified it as bug.
i would suggest to either use the DAV:owner field, or if the current method is still necessary, both. ...as most normal users have no idea about a homeset and don't care why something is considered to be theirs, when it isn't. another idea would be to use 2 different items for this 2 methods, but IMHO this would only be marginally less confusing.
over all: for sure there might be more important things to do. ...so this in not a big deal since it doesn't actually break anything.

[rfc2822]

See also #1372

[dilyanpalauzov]

The “bootstrap” (discovery) process starts by querying a well-known URL, from it obtaining the principal-own URL, and from there the calendar-home-sets (plural) and addressbook-home-sets (again plural) for that user (principal).

Currently DAVx⁵ classifies collections, when these are not found via the principal URL (current-user-principal).

Okay, how are then non-personal collections discovered at all? This is not clear from https://manual.davx5.com/accounts_collections.html#personal-collections .