Methods for prioritizing content

WARNING: THIS DOCUMENT IS DEPRECATED.

Below is a suggested method to prioritize content properly on client size. If you have an alternative method, add it below and open an issue if it requires API spec changes.

Method 1

After bodies are loaded initially, and the events data structure is created, iterate over events and for each event, count the number of conducting bodies that the user follows (this can be done by finding in the followed_bodies using the uuid that will be there in the event #10).

Priority is given to the events in the following order:

1. If the event has two or more bodies followed, it has maximum priority. Further arrangement in order of number of followings.
2. Featured events #13.
3. Events with one body followed.
4. In case the user is not following enough bodies, display other events as well.