Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reduce call-related messages verbosity in 1-to-1 conversations #14056

Open
pmarini-nc opened this issue Dec 28, 2024 · 1 comment
Open

Reduce call-related messages verbosity in 1-to-1 conversations #14056

pmarini-nc opened this issue Dec 28, 2024 · 1 comment
Labels
1. to develop enhancement feature: api 🛠️ OCS API for conversations, chats and participants feature: call 📹 Voice and video calls feature: chat 💬 Chat and system messages

Comments

@pmarini-nc
Copy link

pmarini-nc commented Dec 28, 2024

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: 30.0.4

Is your feature request related to a problem? Please describe.

I think that in 1-to-1 conversations there are too many call-related messages.

Consider for example the following situation:

Image

So, here two users have tried to call each other 4 times in a short time span. This could be seen as a special case, but it isn't. Especially when you are on the go and calling from a mobile device there maybe a "call me in 5 minutes.." proposal from on of the participants, connection issues due to poor networks, "I joined with video and you didn't.."...

However as we are in a 1-to-1 conversation I think that:

  • there is no need to specify who started the call, or at least not in a standalone message. The call is either incoming or outgoing.
  • there is no need to specify who ended the call, as the call ends for both participants.
  • there is no need to specify participant names, as they are defined by the context. In a 1-to-1 there cannot be a 3rd participant.

So these messages output could be basically reduced to 4, similar to the following (just for the sake of the example):

Attempted outgoing call
Outgoing call, duration 3:01
Incoming Call, duration 0:11
Incoming Call, duration 5:41

@ShGKme
Copy link
Contributor

ShGKme commented Dec 28, 2024

Makes sense

@nickvergessen nickvergessen added 1. to develop feature: chat 💬 Chat and system messages feature: api 🛠️ OCS API for conversations, chats and participants feature: call 📹 Voice and video calls and removed 0. Needs triage labels Jan 2, 2025
@nickvergessen nickvergessen added this to the 🖤 Next Major (31) milestone Jan 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1. to develop enhancement feature: api 🛠️ OCS API for conversations, chats and participants feature: call 📹 Voice and video calls feature: chat 💬 Chat and system messages
Projects
None yet
Development

No branches or pull requests

3 participants