No description
9b94c4bb61
it only has content and *some* of the meta fields, but we want to threat pendingevententry and evententry as one and the same in the rest of the application, so don't give access to entire event object. |
||
---|---|---|
doc | ||
prototypes | ||
scripts | ||
src | ||
.editorconfig | ||
.eslintrc.js | ||
.gitignore | ||
index-build-debug.html | ||
index-build.html | ||
index.html | ||
package-lock.json | ||
package.json | ||
README.md | ||
rollup.config.js | ||
yarn.lock |
Brawl
A javascript matrix client prototype, trying to minize RAM usage by offloading as much as possible to IndexedDB
Status
Syncing & storing rooms with state and timeline, with a minimal UI syncing room list and timeline on screen. Filling gaps supported, detecting overlapping events. The [0/1]
in the gif below is the local event key, consisting of a fragment id and event index. No sending yet. Using Fractal here to update the room name and send messages:
Features that this approach would be well suited for
- store all fetched messages, not just synced ones
- fast local search (with words index)
- scroll timeline with date tooltip?
- jump to timestamp
- multi-account