I think to make MSC3983 work over the bindings, we'd need a way (function? flag?) to tell the OlmMachine that it shouldn't bother doing /key/upload for anything other than the fallback keys. Then, a function to route the /keys/claim query into the OlmMachine to have it do stuff.
Note that the implementation effort here is effectively to treat all OTKs as "uploaded" then manually track which ones are used in claim responses, followed by which ones are actually used in toDevice messages. The last bit (toDevice messages) is already present.
(relative priority: low, as of writing)
MSC: https://github.com/matrix-org/matrix-spec-proposals/pull/3983 bot-sdk(NodeJS) implementation: https://github.com/turt2live/matrix-bot-sdk/pull/307
I think to make MSC3983 work over the bindings, we'd need a way (function? flag?) to tell the
OlmMachinethat it shouldn't bother doing/key/uploadfor anything other than the fallback keys. Then, a function to route the/keys/claimquery into theOlmMachineto have it do stuff.Note that the implementation effort here is effectively to treat all OTKs as "uploaded" then manually track which ones are used in claim responses, followed by which ones are actually used in toDevice messages. The last bit (toDevice messages) is already present.