Chris Anderson

we'll need to redo cacheCarReader for async blocks

document how to run on edge functions with remote storage

2

https://github.com/fireproof-storage/fireproof/pull/83/files#r1476859216 ```js import { type Database, fireproof } from 'use-fireproof' import { makeStores, ConnectS3 } from '@fireproof/connect' import { ConnectPartyKit } from '@fireproof/partykit' const dbs = new Map() export function...

fast forward remote changes

2

When a remote makes a sequence of changes in quick succession, they might come faster than the local can merge them. Most of the time when this happens we can...

The prolly index supports getMany, so this can be optimized https://github.com/fireproof-storage/fireproof/blob/388b43a32f42dddd26e822dbf27c2fa911e57087/packages/fireproof/src/index.ts#L156

multiple connectors on same database

1

It will take making the remote stores in this file into lists, or adding a dispatcher: https://github.com/fireproof-storage/fireproof/blob/da9e0a82f4b75f86f97000e7dc52b4173a97bd08/packages/encrypted-blockstore/src/loader.ts#L46

undo feature

2

it should be simple to broadcast writes that undo the previous history, while still being append only in the crdt log

This would allow collection like behavior and independent sync settings. Mostly useful if we want to have a merge view across multiple remotes with different crypto keys. Where the writes...

Local REST server for connect integration tests

1

We have the beginnings of a REST server here: https://github.com/fireproof-storage/fireproof/blob/main/packages/fireproof/scripts/server.js It would be fairly easy to write a connector to use it, and then use all that to integration test...

a test with two dbs with different storage, connected to the same server. we can use that to reproduce bugs we see in the load tests

Currently we discard the File object's name in favor of the document key. However I think we should just keep the name as additional metadata so we can make it...