I've really enjoyed this service. Much better than steemit.com notifications because of the flexibility it provides, such as blacklisting certain users.

One thing that has been driving me nuts though, which I hope can be resolved in the future, is how each edit of a post/comment triggers notifications as if it is a new post/comment.

It would be great if I could configure it so that I only get notified of a new reply comment, not every time the user submits an edit to their comment.

And in particular this has gotten annoying with mentions. I often have around 3 or 4 notifications in a short span of time from the same post/user that mentioned me in their post because they, understandably, are fixing minor errors (I also often make quick typo corrections that I only notice after submitting and I would hate to annoy any users I mention in the post with excessive notifications).

For both of these issues, it would require the service to check the user and permlink of a comment_operation to see if it already exists in the database. For reply comments, the logic is pretty simple: if it already exists, this is an edit, so do not notify again. For mentions, I think a more sophisticated rule would be needed. If the comment_operation is a new post/comment then the mention notification logic would be as it currently is. But if it is an edit, the service would have to grab the json_metadata of the existing post/comment (prior to the edit being applied), extract the array of the users field, and then diff that with the users field of the json_metadata of the edit comment_operation. Only the newly added users, if any, would be mentioned. This way editing a post to correct some typos and not to add new mentions doesn't trigger new mention notifications, but editing a post to mention someone new still would notify just that new user.