Weekly Update 5

[wh201906]

Progress

• Found the source of extra size overhead.
• Posted a performance test report of Node.js.
• Added some tables to show the performance test data of react-native-quick-crypto.
• Working on integrating react-native-quick-crypto and node:crypto into Joplin.
• Tested the actual supported ciphers in the underlying OpenSSL library of react-native-quick-crypto. (details)
• Discussed with the developers of react-native-quick-crypto and facebook/hermes for the possibility of integrating simdutf. (link1, link2)

Plans

• Check the compatibility of encryption parameters in Web Crypto API.
  • The priority of this task is not high.
• Add some graphs to the performance reports.
• Continue integrating react-native-quick-crypto and node:crypto into Joplin.
  • This might take several weeks.
• Evaluate the size cost of integrating simdutf into the Hermes engine and submit a PR for it if possible.
  • This will happen after we switch to the native encryption libraries.

Problems

None

[laurent]

@wh201906

Continue integrating react-native-quick-crypto and node:crypto into Joplin.

Could you maybe try to focus on just the mobile part, maybe event just Android for now, to see if you can get to a working version? And it means you can also submit a pull request more quickly.

[wh201906]

OK I will.