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

[BUG] Conversation Management #3207

Open
ChuanqiBai opened this issue Mar 8, 2025 · 2 comments
Open

[BUG] Conversation Management #3207

ChuanqiBai opened this issue Mar 8, 2025 · 2 comments
Labels
bug Categorizes issue or PR as related to a bug.

Comments

@ChuanqiBai
Copy link

OpenIM Server Version

3.8.0

Operating System and CPU Architecture

Linux (AMD)

Deployment Method

Docker Deployment

Bug Description and Steps to Reproduce

Currently, the client uses the getConversationList interface to retrieve conversation information and fetch data. This leads to an issue where conversations are not deleted after user exits a group (there is no interface to delete user conversation),resulting in unwanted conversation information being fetched.If we modify this interface to filter conversations based on user group, could it cause any problems?

The second issue is that a new conversation is created every time a private chat occurs.When the client receives a large number of private chats, fetching a large amount of data upon login causes noticeable lag on the client side and also impact s the server.

Screenshots Link

No response

@ChuanqiBai ChuanqiBai added the bug Categorizes issue or PR as related to a bug. label Mar 8, 2025
@OpenIM-Robot
Copy link

Hello! Thank you for filing an issue.

If this is a bug report, please include relevant logs to help us debug the problem.

Join slack 🤖 to connect and communicate with our developers.

@FGadvancer
Copy link
Member

Hello,

The issue you described regarding conversation recycling is indeed a potential problem. Your direct filtering approach is also a viable solution.

We are currently considering deleting related conversations when a user leaves a group or when a group is disbanded. For one-on-one chat scenarios, if the system requires a friendship to initiate a conversation, we can create or delete conversations when a friendship is established or removed.

However, for stranger chat scenarios, due to local cache data storage, if a user deletes a conversation and then starts chatting again after a certain period (which is uncertain), the timing of when the server should recreate the conversation remains an issue. In the future, we may adopt different strategies for conversation recycling and creation between friends and non-friends.

Additionally, you mentioned that a large number of private chats lead to noticeable synchronization delays on the client side. Could you provide some details on the scale of private chat activities for the mentioned user? Also, is your scenario based on non-friend chatting, or is chatting only allowed between friends?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

3 participants