As mentioned here some systems might employ heavy rate limiting. Right now there's no way around this because NMO loads a fixed number of items, which might or might not be too large for a specific instance.
In order to avoid this issue, lazy loading for e.g. LoadPosts should be employed, where a small batch of e.g. 10 latest items are loaded and, as soon as the user reaches e.g. the 7th item, the lazy-loading would kick in and load further (older) posts.
This requires for large parts of the logic to change and it requires an event to be fired for the lazy-loading to know when to load the next batch.
As mentioned here some systems might employ heavy rate limiting. Right now there's no way around this because NMO loads a fixed number of items, which might or might not be too large for a specific instance.
In order to avoid this issue, lazy loading for e.g.
LoadPostsshould be employed, where a small batch of e.g. 10 latest items are loaded and, as soon as the user reaches e.g. the 7th item, the lazy-loading would kick in and load further (older) posts.This requires for large parts of the logic to change and it requires an event to be fired for the lazy-loading to know when to load the next batch.