FAQ about interactive messaging

更新时间:
复制 MD 格式

Answers to commonly asked questions about the new version of interactive messaging.

Does an interactive messaging group that I created become invalid if no one joins the group?

No. After you create a group, the group information is stored in the backend until you delete the group.

How many interactive messaging groups can I create? How many people in a group can be online at the same time?

By default, you can create 5,000 groups for each application, excluding deleted groups.

A group has no limit on the total number of members. If more than 20,000 members need to be online at the same time in a group and this does not cause risks, submit a ticket to request a quota increase. For more information, see Contact us.

Are the new version and the legacy version of interactive messaging compatible?

No. The new version and the legacy version of interactive messaging use different protocols and have different architectures. Messages cannot be exchanged between the new and legacy versions.

Does interactive messaging support uni-app miniapps?

Yes. You can use JavaScript to implement interactive messaging on an HTML5-based uni-app miniapp. For more information, see Client-side integration.

When I query the online members in a group, do the query results include the group creator?

Yes. When you query the online members in a group, all active users in the group are returned. All clients that are logged on and connected to the server are counted. If a client is closed, interrupted, or calls an API operation to leave the group, the corresponding user is removed from the online members list.

What are the differences between the new version and the legacy version of interactive messaging?

The legacy version does not support features such as live room gifts and rewards. Its traditional architecture limits further optimization.

The new version relies on Global Realtime Transport Network (GRTN), offering more reliable message delivery, richer features, and a smaller SDK.

Does interactive messaging support content moderation of messages that are sent?

Yes. When you create an application, you can select one of the following content moderation methods: no content moderation, built-in content moderation, and custom content moderation.

You can specify whether to moderate messages sent by clients. For system messages, we strongly recommend that you select no content moderation. When content moderation is enabled, the server reviews each incoming message using the method you selected. Messages that fail the review are blocked. Messages that pass the review are sent to all users in the group.

Does interactive messaging provide a Flutter SDK?

No. Currently, the interactive messaging SDKs are available for Android, iOS, WeChat mini-programs, and HTML5-based uni-app.

Does interactive messaging provide a Unity SDK?

No. Currently, the interactive messaging SDKs are available for Android, iOS, WeChat mini-programs, and HTML5-based uni-app.

What are the purposes of the NoAudit, NoStorage, and NoCache parameters in the API operations that are used to send a message?

Parameter

Description

NoAudit

Specifies whether to review the message. If the message fails the review, the server blocks it and returns an error message to the client. We recommend that you skip review for system messages.

NoStorage

Specifies whether to store the message in the database for future queries. We recommend that you store only non-system messages, such as comments and bullet comments.

NoCache

Specifies whether to cache the message. The server caches the 50 most recent cacheable messages. When a new member joins the group, the member can call an API operation to retrieve these messages. We recommend that you cache only non-system messages, such as comments and bullet comments.

Note

The NoStorage and NoCache parameters work in the same manner for client-side message sending API operations. You need to specify only one of the two parameters.