From b6d3d39dc201fccb04563786b1a6648ee907acd6 Mon Sep 17 00:00:00 2001 From: kaichaosun Date: Thu, 26 Sep 2024 15:18:25 +0800 Subject: [PATCH] status update message --- standards/application/bandwidth-optimization.md | 15 ++++++++++++++- 1 file changed, 14 insertions(+), 1 deletion(-) diff --git a/standards/application/bandwidth-optimization.md b/standards/application/bandwidth-optimization.md index 17d2102..0f342e0 100644 --- a/standards/application/bandwidth-optimization.md +++ b/standards/application/bandwidth-optimization.md @@ -157,7 +157,20 @@ User can enable periodically backup and set the intervals as needed. Currently, ### Status Update Messages -Users might receive status update messages for themselves, which should be filtered out to avoid unnecessary bandwidth usage. +User sends status update messages to the global shard every a few minutes. With the increase of users, the traffic can be heavy. + +**Option 1** + +Favor lightpush and filter protocol for such messages. + +**Option 2** + +Don't broadcast the message via Waku pubsub protocol, instead use p2p connection (WebRTC) directly to the contacts for routing messages. +If the status update message is for a community, it should bradcast to community assigned shard. + +_Concerns:_ + +- it may require a significant amount of work to implement the p2p connection between contacts. ## Summary