DarkSky

currently we have the following features coupled in core/rpc/storage: - core: full text indexing, single page extract - rpc: websocket/webrtc connector - storage: image minify, stream storage, database/s3 support these...

```[tasklist] ### Tasks ```

In OctoBase, the sync protocol is designed to be transport layer agnostic. Developers only need to provide an mpsc sender and receiver to transmit data in different transport layers. For...

Using traits to abstract related concepts can make `connector` implementation easier, which is an important but not urgent todo

pre-task: #276

pre-task: #275

pre-task: #274

cloud feature split into independent crates

1

```[tasklist] ### modules - [x] mail feature #204 #259 - [x] firebase auth #261 - [x] sync endpoint #210 - [x] info broadcast #210 - [x] #212 - [ ]...

abstract reduction in jwt

2

In the original design, [jwt](https://github.com/toeverything/OctoBase/tree/master/apps/frontend/libs/jwt) will be responsible for docking multiple backends and supporting the export of different formats, so the data structure and API are abstracted in multiple layers....