nextcloud / nextcloud/spreed

Disable one-to-one conversations

Open
#7,483 7 comments 16 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement feature: api 🛠️ feature: conversations 👥 feature: frontend 🖌️ feature: settings ⚙️
Dominant language
PHP
Stars
2.2k
Forks
587
Avg merge
18h 27m
Merged PRs (30d)
333

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.

Sometimes it might be desired to prevent users from creating one-to-one conversations so all channels are created by a managers/leads/teacher.

We have an option for group/public room creation to limit it to users of a given list of groups.
I guess for one-to-one a bool config is more suitable because otherwise the conditioning whether to show the profile/contacts option etc will require loading too many details from the database?

Also it comes with more workload along the way:

  • Adjust profile actions
  • Adjust contacts menu action
  • Reply privately option needs to be removed
  • Toggling the setting does not delete existing conversations
  • Clients need to understand this setting too, partially automatic by the profile field restriction, but reply-privately is necessary?

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 reviewing the existing restrictions for group and public room creation, then trace the profile actions, contacts menu action, and private-reply option mentioned in the checklist. Done means a setting prevents new one-to-one conversations, leaves existing conversations intact, and is understood by clients.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
full-stack
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.