Prioritise notifications - take 2: now with more anonymisation.
-
More a feature request with a bug, I think:
bug) I have 18 unread notifications, only 7 are visible in the dropdown. If I clear some of the unreads, then some of the remaining ones will become visible replacing the ones I've just read. This sort of thing happens all the time. Notifications were originally 24 unread, with only 9 of them visible (the rest of the ones shows were read.)
request) Can we have the unreads at the top of that list?
-
The previous image was only downloaded by 2 IPs before it was deleted, both admins.
-
Wow, we have some real deplorables on the forum these days.
-
@boomzilla
We keep trying to lynch Hitler in the @Mafia-Club-Ded thred, but Mussolini keeps splitting the lynchwagon.
-
@PJH said in Prioritise notifications - take 2: now with more anonymisation.:
request) Can we have the unreads at the top of that list?
Ideally I want to have (pseudo code):
top n from { notifications order by unread desc, timestamp desc } order by timestamp desc
...so it'd take the unread notifications first, in order from newest to oldest, followed by the most recent read notifications, up to n notifications total; then in the end it'd sort the notifications in chronological order.
-
@anotherusername So if you have more than
n
unread, you want to getn
unread items at random and not just then
most recent unread?
-
@PleegWat whoops. Yeah okay, it should be ordered by timestamp there, also.
Although,
n
unread items at random would still be better than the current behavior...
-
@anotherusername said in Prioritise notifications - take 2: now with more anonymisation.:
...so it'd take the unread notifications first, but in the end it'd sort the notifications in chronological order.
I want the read ones replaced by unread when the list contains less items than there are unread.
In chronological order (whatever that means - in some contexts the time appears to be the time of the post, in others it's the time of whatever event generated the notification.)
-
@PJH yes.
I want as many read notifications to be displayed as possible (up to n), but the n notifications that it displays should be sorted by timestamp (time of the event which generated the notification). So the unread ones will come to the top page (where the page size is n, and you can only see the top page anyway), but not necessarily to the top of the top page.
-
I think what it currently does is take the N latest unread notifications and the N latest read notifications and then sorts them by date.