Astra
206bde18e0
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. |
||
|---|---|---|
| .. | ||
| appearancefetch | ||
| bots | ||
| catalogfetch | ||
| createuser | ||
| langpackfetch | ||
| otpwebhook-example | ||
| stickerfetch | ||
| stickerseeddeploy | ||
| telegramloginkeygen | ||
| telesrv | ||
| telesrv-admin | ||
| telesrv-load | ||
| telesrv-update | ||
| walletminiapp | ||