GitHub's new notifications: a case of regressive design

Re:GitHub's new notifications: a case of regressive design by jkrems on Friday March 13, 2020 @01:27PM (#22569112)

I've seen a lot of active open source users talk positively about the new design. I personally disabled email notifications completely and wouldn't want to go back. Having a clear separation between unread, read, and archived is a huge step forward.

Also, I'm not sure why it matters to have notifications grouped by repo. At least for myself it rarely made sense and only wasted space in the UI.

[ Parent | on HN ]

Re:GitHub's new notifications: a case of regressive design by wildpeaks on Friday March 13, 2020 @02:38PM (#22569765)

For me, grouping by repo was useful because I don't care about every repo equally: some produce few notifications but are extremely important, while other repos (that happen to produce a lot of notifications) aren't that important.

[ Parent | on HN ]