There are some examples in our repo that use op, rather than sequenceDelta event. These do not work, as processing op correctly is very difficult, and error prone. sequenceDelta is always correct. These legacy examples should be updated or removed.
When a client application using Antidote crashes or has incorrect transaction handling, some or even many transactions can stay open. These transactions are never forcefully aborted by Antidote. This can potentially leave many txn-coordinator-fsms running forever.
For a database that should be deployed as a long-running system, this behavior is unacceptable. Transactions, that are not used anym
We previously created our own plugin for our company based on this repository.
I'd like to share some points we noticed when we created it. We deleted it in the end because we no longer need collaborative editing features, though.
This is not an issue, so you can close this “issue” after you read it. I just want to pay you back.
I'm sorry I haven't
Collaborative text editor (like Google Docs or CoderPad) with integrated semi-anonymizing voice chat intended to help reduce bias in technical communication.
When a contact is already added, open the contact profile or the existant conversation
The error check is done here: https://github.com/berty/berty/blob/097eb0229f22e2abce3addd750c8dce98e92845f/js/packages/components/modals/InvalidScan.tsx#L126
We shouldn't show the invalid scan modal but navigate instead