- embeddable like sqlite
- clustered like dqlite
- has a standalone node like rqlite
- can be backed up to S3 like litesteeam
- optionally AP like cr-sqlite alongside CP
4,362 karma · joined September 30, 2017
- embeddable like sqlite
- clustered like dqlite
- has a standalone node like rqlite
- can be backed up to S3 like litesteeam
- optionally AP like cr-sqlite alongside CP
Would it though? The problem with many issue trackers is that unlike many other tools, they do not encapsulate the right way of doing things, and so it's easy to add paperwork without making the work more straightforward.
And if there is someone who can set up Jira and teach people to use it well, they don't necessarily need Jira.
One thing I don't know is whether these delayed source releases are enough to validate releases published to app stores. If they are, this means Telegram is building up reputation and would have to burn it to publish a release with a backdoor not present in the source.
The other thing this allows is for a third party to maintain a fork without having too much trouble keeping up with new features.