Federated avatars
Open
Nobody has claimed this yet.
1. to develop
enhancement
feature: federation
needs review
overview
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
There are several things:
- federated avatar is not available on web ui, only "tobias@next…" is shown
- owner-id via propfind shows
- "tobi"/userID if it is the same server
- "tobi@nextcloud.domain.com" if it is a federated share, but no protocol
- clients would have to fetch avatars by themself
- clients cannot really difference between local and federated user:
- tobias@domain.com (internal)
- tobias@nextcloud.domain.com (external)
@rullzer suggested that local server acts as a proxy, so that client/webUI can ask for avatar on their own server
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by tracing the web UI avatar display and PROPFIND owner-id handling, then review the suggested server-side proxy for federated avatar requests. Done criteria need to define local versus federated identities and avatar retrieval.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- api, full-stack
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100