but what you can do is store the list locally, in the paged data source factory for example

• pagination data source loads list and keeps reference to all data (in my case the domain objects before mapping to ui friendly objects) • when you press like button, invalidate the old list • from the pagination factory, fetch the old data from the invalidated list • construct new list with passing the old data • instead of fetching the new data in the initial loading, simply use the old data, which should have the new like state included.

If you pass on the new list to the existing paged list adapter (with submitList) then the paged list adapter will use a list differ to update your list

so if Paging 3 does this the same as paging 2, then this would be a start 🙂

Paging 3 have RemoteMediator https://developer.android.com/topic/libraries/architecture/paging/v3-network-db maybe this help

i will try this @Joost Klitsie