myTeamSpeak: two-way sync of bookmarks and identities
MyTeamSpeakSync compares each item against what the last run left: a change on one side goes to the other, deletions too, and an item changed on both sides is a conflict for the user. The first run pairs items up by identity key or bookmark name and address. Edits are written over the item's Item_Data field by field, so what we do not model survives. The protocol was probed live and checked against the official client: the server stores whatever revisions it is sent and never reports a collision, so the client re-reads the cursors before writing. Edits carry last_known_version like the official client's, which applies them within its one-minute poll. All requests now share one session; signing in for each got the account's logins throttled. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -84,9 +84,5 @@ Recovered constructions:
|
||||
|
||||
## Remaining reverse-engineering gaps
|
||||
|
||||
Password login, key unwrap, item encryption/integrity framing, two-phase comparison, and the local
|
||||
manipulation flags are recovered. The remaining uncertainties are narrower: where ordinary edits rotate
|
||||
`sync_version_uuid`, the exact lifecycle of `last_known_version`, the official collision winner/merge
|
||||
policy, and instruction-level confirmation of the deletion-detail builder. Recovery-key import is also
|
||||
not yet recovered. The read-only pull is implemented in `eu.lixko.ts3j.client.myts` (see IMPLEMENTATION.md); destructive upload
|
||||
should remain gated until the deletion mapping has a fixture or controlled integration test.
|
||||
The synchronisation protocol is settled by live probing and capture; see IMPLEMENTATION.md "How the
|
||||
service and the official client behave". Recovery-key import is not recovered.
|
||||
|
||||
Reference in New Issue
Block a user