nextcloud / nextcloud/server

Disappearing users in system address book for federation

Open
#38,042 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage enhancement feature: carddav feature: federation
Dominant language
PHP
Stars
36.9k
Forks
5.2k
Avg merge
2d 3h
Merged PRs (30d)
713

Description

Follow up to https://github.com/nextcloud/server/issues/38021

With the new address book exposure, a user can remove themselves from a federated the system address book by setting their VCARD data to a local scope on the required VCARD properties (FN (v3, v4), N(v2, v3)).

This is GDPR compliant, but might cause confusion if admins are federating with another instance and users are missing.

Option 1: allow admins force overrride
Option 2: document and leave as is

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the linked issue 38021 and the behavior described for FN and N vCard properties with local scope. Determine whether the agreed outcome is an administrator override or documentation explaining why federated users may be absent; done means that decision is recorded and the chosen work is complete.

Written by the indexing model from the issue text.

Assessment

Domain
distributed-systems, documentation
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.