jdev - 2023-11-14

I found a quite old implementation of libsignal-js in WebAssembly, wondering if it could help with our current OMEMO implementation state in the browsers

https://github.com/Inria-Prosecco/libsignal-protocol-wasm-fstar

I'm kinda blocked with the outdated and unmaitained libsignal-js library that has horrible performances to fit with OMEMO :/

I was looking at the omemo code in converse.js yesterday and it looks pretty good?

https://github.com/conversejs/converse.js/blob/master/3rdparty/libsignal-protocol.js

The code look ok, the performances should be the same as Movim

The encoding/decoding is in the main JS thread, so blocking everything

Also the I/O rely on some JS interface that is kinda slow

https://github.com/movim/movim/blob/master/public/scripts/libsignal_protocol.js

Encoding/decoding you mean the base64?

encrypting/decrypting I mean

The whole ratchet process thing

When I looked encrypt/decrypt was being done with crypto subtle built into browser, I thought?

Maybe its the message I/O with the storage layer

I'll give it another try, see if I overlooked something

We are starting the workshop in about 45 minutes, lobby is officially open in 30. Everyone interested welcome. Join: https://teamjoin.de/XMPPVisionandStrategicWorkshop https://fosstodon.org/@xmpp/111405455575621613

Beherit: will this workshop be recorded?

nvm

meson: sorry no, but I think you managed, right? anyone who still want to provide input, we can do it together as followup

Beherit: yeah I had passively followed with one ear :)

Okay :-)

is there someone familiar with OMEMO 2 concept? Can someone validate if one of my accounts has garbage in bundles/devices pep nodes?