nextcloud / nextcloud/spreed

remember notification settings on open conversations between leave/join

Open
#12,775 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement feature: api 🛠️ feature: conversations 👥
Dominant language
PHP
Stars
2.2k
Forks
587
Avg merge
17h 55m
Merged PRs (30d)
350

Description

How to use GitHub
  • Please use the 👍 reaction to show that you are interested into the same feature.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

Feature request

Which Nextcloud Version are you currently using: (see administration page)
latest stable - 28.x

Is your feature request related to a problem? Please describe.
There's a bunch of open chats on our server. I join and leave regularly. But some are team chats that have regular calls, so I have to disable the notification for calls, otherwise I go crazy. But after I leave a room and re-join, I have to disable this notification again... it doesn't store it.

Describe the solution you'd like
Talk should remember my settings per room, even when I exit the room and join again.

Describe alternatives you've considered
A global default would be nice, but it doesn't fully replace this.

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 tracing Nextcloud Talk's per-room notification settings flow and how a user's room membership is handled when they leave and rejoin. The feature is done when call-notification preferences are retained for each room across that membership cycle, while a global default remains only an alternative.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
full-stack
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.