channels: give kicked/banned/promoted/transferred users a real qts so their client applies it
updateChannelParticipant carries the account's qts per the MTProto spec, but the server always sent Qts: 0, so real clients silently discarded it as a stale duplicate -- the banned/kicked user's channel never vanished locally and no correct "removed by admin" message showed, even though the update was delivered successfully at the transport layer. Add a durable per-device qts queue (channel_participant_event_queue) sharing its qts number space with the existing secret-chat queue (one qts sequence per device, per spec), and use it to stamp a correct, monotonically increasing qts on the update for every device of the affected user -- for channel bans/kicks, admin promotion/demotion, and ownership transfer. A device offline when it happened can now recover the event via updates.getDifference instead of missing it permanently.
This commit is contained in:
parent
97711c9d2e
commit
206bde18e0
16 changed files with 482 additions and 42 deletions
|
|
@ -285,7 +285,7 @@ func TestInvokeWithoutUpdatesBaselineCommitsResultAndSecretEventsWithoutSubscrib
|
|||
authKeyID := [8]byte{21}
|
||||
deviceKey := businessAuthKeyInt64(authKeyID)
|
||||
queue := memory.NewEncryptedQueueStore()
|
||||
secret := appsecret.NewService(memory.NewSecretChatStore(), queue)
|
||||
secret := appsecret.NewService(memory.NewSecretChatStore(), queue, queue)
|
||||
eventID, err := queue.AppendStateEvent(context.Background(), domain.EncryptedStateEvent{
|
||||
TargetUserID: userID,
|
||||
ChatID: 77,
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue