Bruno Windels

> > list things of things that would need their updates passed over the message channel between the worker and the page > > @bwindels Is the opposite scenario also...

Just saw that workers of type es module are coming to firefox! This means we may not need a build-step to convert `import` to `importScripts` for the SDK, depending on...

Sorry for the late reply, I don't think we have bandwidth to support this at this time. We do plan on improving our storage layer in the future, and perhaps...

Just came across this in the code. We could update it after a disconnection/startup.

(partial) list of projects that depend on js-sdk, whose build we could potentially break: https://www.npmjs.com/package/matrix-js-sdk?activeTab=dependents Thinking if it would be ok to switch to exporting ES6 if we'd release it...

> Also we should have a safe function to read fields/paths of an event, and act predictably when that field is missing/wrong type/ ... this exists in `utils/validate.js` now as...

To be able to look up a `RoomSummary` by the room id of a previous version of the room, the `RoomSummary` store could have a [`multiEntry`](https://developer.mozilla.org/docs/Web/API/IDBIndex/multiEntry) index on the `previousRoomVersions`...

The spurious onnegotiationneeded event on the polite side (non-initiating side) doesn't seem to have a good explanation in the logs. The event should only fire when `signallingState === stable`, but...

The signalling messages in that end up in the queue when they shouldn't looks like an unrelated issue, have created https://github.com/vector-im/hydrogen-web/issues/1015 for this

Had it happen again with travis, see linked rageshake at position https://logviewer.bruno.bzh/#53/1/0/5