Notifications feature

[joeytwiddle]

Notify authors when:

• A new issue is posted on one of their scripts
• A reply is posted on one of their scripts' issues
• One of their scripts is forked
• A reply is made to a thread which the user has participated in. (Would need an opt-out for spammy threads!)

Also consider notifying normal users when:

• A script they like has been updated. (If they are using GreaseMonkey and the script @version has been incremented, then they would have got the update through Firefox. But in any other situation they would not, so a notification could be useful to them.)

[Martii]

Most likely #15 since we don't always have everyones email address depending on authentication method.

-1 for notification on script updates... that is redundant with built in update checking in all of the user.js engines. I might consider porting installWith at a much later date as other features come online.

Closing as duplicate.

[sizzlemctwizzle]

I don't see this as a duplicate since PMs and notifications are entirely different features.

Re-opening because I'd like to have on-site notifications. Somewhat like how GitHub does it. I'd like to be able to watch topics and also be notified by the @username syntax. But this feature is currently in the "nice to have" category imo.

I'm -1 on the script update notifications.

[joeytwiddle]

Re. "Script update notifications" yeah forget it. There is a good existing solution now with @version and auto-update.

Re. "notifications", to clarify, I didn't mean to suggest e-mails. (Although some users might like that, I do not care for it!)

I meant instead a feature like Github's or Facebooks's. There is a "bell icon" in the header bar which would have a number next to it if the user has unread notifications (and unread PMs). Clicking it would drop down a list of "personal news items" the user might want to check. (There could also be a notifications page that keeps a history of notifications, even the read/seen ones.)

It seems it would share a lot with a PM feature but it could have some minor differences:

• A notification takes you to an existing part of the site when clicked (the page of a new issue, or the first unread reply on an existing issue page, or the page of the forked script).
• Notifications might end up clearing themselves automatically. -- Imagine the user visited that issue page without having clicked the notification to go there. Then the notification would still be cleared, because the user has seen the page. -- Another example: User B forks user A's script. But then user B deletes his fork. The notification that user A would have got is now of no interest, so it disappears.
• Some notifications might not enter the queue. E.g. a notification might be generated when an issue is replied to, but if the user already has a notification about replies on that page, then the new one is redundant, so we won't add it.

So yay some fiddly bits of logic there, which no doubt other devs are also implementing on their own websites! ;)

If we don't want to do it perfectly to begin with, then a good starting point would be:

• Let the user know when a new issue or new comment has been made on one of his scripts.

[Martii]

Re. "notifications", to clarify, I didn't mean to suggest e-mails. (Although some users might like that, I do not care for it!)

I meant instead a feature like Github's or Facebooks's. There is a "bell icon" in the header bar which would have a number next to it if the user has unread notifications (and unread PMs).

Email could work but we don't have it most of the time @sizzlemctwizzle which is why the notifications could be a system generated and referenced PM like @joeytwiddle is saying here which is part of the PM system in #15 which hasn't been implemented yet to my knowledge yet.

[sizzlemctwizzle]

I guess, but I'd like my PMs and notifications displayed separate but that could probably handled with a filter.

which hasn't been implemented yet to my knowledge yet.

It hasn't. I'm thinking of using the discussion software (once I get around to finally completing it), but just making it between two people. Unless you use the @username syntax and essentially invite someone else to join the private discussion. I guess the PM notifications would just be notifications pointing to private discussions. Anyway, I'm still thinking about it and very open to the suggestions of others.

[TimidScript]

There is a "bell icon" in the header bar which would have a number next to it if the user has unread notifications (and unread PMs).

:+1:

I would like to suggest, have a list of the number of open issues displayed in the author's scripts page beside the number of installs and ratings. Not really notification but very useful and it will allow third party developers to add something like this.

[Ede123]

Since I just realized I missed an issue notification by @Martii on one of my scripts I'd suggest something very similar to what TimidScript has in mind (and I could imagine it wouldn't be too hard to implement after all): On user pages we already have "Scripts" and "Comments" feeds. Basically I'd love to have another section "Issues" which would be another feed which just combines the issues from all of the authors scripts.

This should probably be a higher priority, since as far as I can see there is currently no possibility to view the issues for the scripts one uploaded, without opening every script page separately (or did I overlook something?).