The order of pools posts are incorrect on search

[McSib]

There is a current bug when downloading pools where the pool is ordered incorrectly. The cause is from how the posts are grabbed. Initially, to save performance, pools were made to be downloaded in a single bulk search with the tag pool:{pool_id_here}. Because of this, it orders from the highest id to the lowest, meaning it relies on when the post is uploaded rather than where the post resides in the pool. This will be worked on before the release of 1.7.0.

[McSib]

This issue is now fixed after adding a for loop that swaps elements in the vector to the correct indexes. It's done by comparing the entry ids with the posts ids.