RocketChat / RocketChat/Rocket.Chat
Gravatar requests still sent after disabling default avatar
Open
Nobody has claimed this yet.
planned
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
Description:
Rocket.Chat still attempts to connect to s.gravatar.com even after disabling Gravatar in Account Settings → Set Default Avatar → Disabled.
The endpoint /api/v1/users.getAvatarSuggestion is still being called, which triggers the connection to s.gravatar.com.
Steps to reproduce:
- Account Settings → Set Default Avatar → Disabled.
Expected behavior:
No connections to s.gravatar.com
Actual behavior:
Connection to s.gravatar.com
Server Setup Information:
- Version of Rocket.Chat Server: 7.9.0
- License Type: Starter
- Number of Users: 35
- Operating System: Linux Debian 12
- Deployment Method: docker
- Number of Running Instances:
- DB Replicaset Oplog:
- NodeJS Version:
- MongoDB Version: 6
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
Start by tracing the /api/v1/users.getAvatarSuggestion endpoint and how it reads the Account Settings → Set Default Avatar value. Reproduce the disabled setting, then verify that the endpoint no longer triggers connections to s.gravatar.com when the default avatar is disabled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100