3 ms·
Interesting... but I have to disagree. A lot of people would scream bloody-murder if their notifications were automatically marked as read. And if stars / fla
by Groxx 16y ago
Interesting... but I have to disagree. A lot of people would scream bloody-murder if their notifications were automatically marked as read. And if stars / flags are the only organizational option, any power-user will quickly feel the everything-bucket-migraine. Folders / tags are probably a better option there, and would indeed be useful for power-users. By all means, that'd be a useful addition, and can be ignored if one doesn't want to use it.
As to the auto-mark-as-read, and possibly everything, how about a plugin? I'm only familiar with Safari's API, but that has storage for settings / data - you could just migrate things to be saved into there, and mark everything automatically.
- alanh 16y agoGood point regarding automatically marking as read. Since there is already a “Mark as Read” button, automatically doing so would not required for my ideal solution (as described in the link). I have heard people describe notifications as “broken” for not auto-marking as read, which is why I assumed it was desirable. (That, and since Facebook does it this way, there is a very popular precedent and likely some broken expectations among new GitHub users.) Now regarding labels/folders… this is probably overkill IMO. That’s where GitHub "issues" or various To-do managers, which do have labels, come in.
- Groxx 16y agoI'm not familiar with the "issues"... I'm a very light GitHub user. So, a couple questions for you: Issues? Does GitHub have an API for their notification / message / what-have-you system(s)? What do you use the to-do managers to do? How do they help? Are there any other ways the notifications are "broken"? I ask because I may be interested in making a Safari plugin (which I gather is pretty trivially similar to making a Chrome plugin) to handle a few of the basics. And I'm a UI/UX nut, so how others handle workflow things like this fascinate me.
- steveklabnik 16y agoIssues is GitHub's built in ticket system. Se here, for example: http://github.com/hacketyhack/hacketyhack/issues http://github.com/hacketyhack/hacketyhack/issues They can be turned on per-project.