1ec5 created an issue (openstreetmap/openstreetmap-website#7123)

As with direct messages, we should track whether the user has read a given 
in-site notification. When listing notifications in the UI (#7018), the user 
would have an option to mark the notification as read (and perhaps unread). The 
API in #6896 should also indicate whether a given notification is read.

The total number of unread notifications can appear as a badge at the entry 
point for the list of notification. #3182 has some discussion about the 
potential design of this indicator. In the API, the [current user 
details](https://wiki.openstreetmap.org/wiki/API_v0.6#Details_of_the_logged-in_user:_GET_/api/0.6/user/details)
 should indicate the total number of unread notifications. This would enable a 
client such as JOSM to display the number of unread notifications alongside the 
number of unread messages.

An alternative design for an unread count could rely on each notification’s 
timestamp and timestamp parameters on the notification list API call. JOSM 
would need to keep track of the last time notifications were checked. The 
downside of this approach is that the user would see a different number of 
unread notifications on each of the clients they use (across their desktop 
browser, phone, JOSM, etc.).

-- 
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/issues/7123
You are receiving this because you are subscribed to this thread.

Message ID: <openstreetmap/openstreetmap-website/issues/[email protected]>
_______________________________________________
rails-dev mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/rails-dev

Reply via email to