neopostmodern

Entities that only have `updatedAt` greater than the last fetch are not actually included int response! There needs to be a union of newly visible items (either by creation or...

*All stats for roughly 8.5k notes and 3k tags* ### General - `leanTypeEnumFixer` has 90%) is spent pulling data, not querying/getting a cursor. This was tested by running the query...

Fetch tag frequency / sorted list from server

1

This would speed up the crazy slow cache-rebuilding on cold devices, plus it could easily be refreshed irregularly.

Nearly every DB operation should change `updatedAt` including tagging Only select operations should change `changedAt`: - created - changed title - changed note content Would also fix the unexpected behavior...

Could e.g. `md5` the JSON of all notes sorted by `createdAt`, mapped to objects with only `_id` and `updatedAt` on the server, send that along with every request for updated...

Discovered so far: - structure - post When searching for these, all notes are shown