Bah, I remembered why unread/read notifications is not a single list. Basically, because it breaks the pagination. When notifications are marked as read (ex: on visit), and we go to the next page, the next unread notifications will move to the previous page, as the previous page notifications are all read.
The infinite pagination cannot fix this, because the order is not defined by a single field. I'm not sure it can be fixed to handle this case, but I don't think so.
Reverts #292
Bah, I remembered why unread/read notifications is not a single list. Basically, because it breaks the pagination. When notifications are marked as read (ex: on visit), and we go to the next page, the next unread notifications will move to the previous page, as the previous page notifications are all read.
The infinite pagination cannot fix this, because the order is not defined by a single field. I'm not sure it can be fixed to handle this case, but I don't think so.