Addition of way to add ids for recently deleted notes to search

[StephenArg]

Describe feature

So currently I'm making a trilium client mobile application for ios. I noticed there's no way to do incremental syncing the way joplin does, so I implemented my own way by using the search feature to find the last notes that were updated since the last time my application updated (this way it avoids doing a full sync every time).

The problem with this is though, if another application deletes the note, there is currently no way for my application to know there were any deleted notes.

So I'm wondering if it's possible to add a parameter to the search request that includes ids of notes deleted since a specific datetime.

If the server currently doesn't store those deleted note ids, maybe it would be necessary that it did, at least for a certain amount of time, so it can inform other applications.

Thoughts? Is there already a better way? Thanks

Additional Information

No response

[eliandoran]

Hi,

I noticed there's no way to do incremental syncing the way joplin does

If by incremental sync you mean pushing only the changes during a sync (e.g. delta), this is already implemented in Trilium. Whenever you make a change after activating sync, a special table called entity_changes is managed which informs you of any changes (note reordering, blob/content change or attributes).

There is an overview of how sync works in https://docs.triliumnotes.org/developer-guide/concepts/sync.

I believe @FliegendeWurst also got the sync to work on the Android version.

[StephenArg]

@eliandoran This is available through etapi?

[StephenArg]

It looks like I'd have to authenticate differently than I've been doing (I've been using the etapi bearer tokens).

Also, I could try to reimplement everything using the main api and websocket that the desktop browsers use, but I was reading that the /api/sync/* endpoints are internal to Trilium. They may not be guaranteed to be stable across Trilium releases. The request/response shapes could change without notice. The ETAPI is the supposedly stable contract for external clients.

[eliandoran]

@StephenArg , no, you should use the main API.
ETAPI is mostly meant for scripts and small integrations.
For a full-on reimplementation like a mobile app, the main API is the only possible solution.
Despite the warnings, the REST API is quite stable; however there would still be a maintenance burden on you in case something changes.

[StephenArg]

Are there docs for all the main endpoints?