Samuel Scheit
Samuel Scheit
> By providing a collection ID first (i.e. createItems('news', { items: { title: 'Hi' }} instead of createItems({ collection: 'news', items: { title: 'Hi' }}) we can make TypeScript aware...
@jrose-signal were you able to resolve this issue with signal? (I'm trying to generate signal_ffi)
@Auties00 I've unified web/mobile to always use the tcp socket. I've tested it and it everything still works as expected
@ripreal Messages were received, but the event was not emitted, because the app state keys weren't initialized (which aren't available on mobile). I've fixed the problem, by skipping app state...
We need to add documentation to the Readme how to use the mobile api, but other than that it is finished.
by adding this cli argument to the browser args, `--headless=new`
As a workaround until I find a solution you can prevent node from crashing on errors via ```js process.on('uncaughtException', function (err) { console.error(err); }); ``` The error is probably caused...
May be related to #74. The problem is I can't seem to replicate and isolate the issue. Are there any other logs indicating why it is failing to record?
any updates?
> https://github.com/jitsi/megolm.js could be useful for implementing E2EE. > And this is another suite for end-to-end message encryption, which implements IETF MLS standard: https://gitlab.matrix.org/matrix-org/mls-ts > signal protocol