Frontend & browser·State, data and re-rendering
the data on screen is a copy of something you do not own, and it went out of date while you were looking at it.
Server state
Also calledremote state, async state
Data whose source of truth lives on a server and is merely cached in the client. It has properties client state does not — it can be stale, it can be shared with other users, it needs loading and error states, and it needs revalidating — which is why hand-rolling it with a state atom and an effect reproduces a caching library badly. Recognising which of your state is this kind is the single most useful sorting exercise in a frontend codebase.