Describe your problem or use case

I noticed that the compact_changesets function has been replaced with a stub. It doesn't do anything. This means that if a user connects to a database that already has many transactions, they are forced to download the entire history instead of just the latest state.

Describe the solution you'd like

For the case when a user connects to the server who does not yet have any data, the simplest implementation of this function would be to collect all transactions from the database and apply them to the local database. Then, the resulting database can be transferred to the user. On one hand, this would shift some of the load from the client to the server, and some consideration needs to be given to caching these results. On the other hand, packing and transferring all transactions can also be quite costly, so it's better to compress the data in advance.

What do you think? Are there any plans to reinstate this function?