Subscribe to comment replies, instead of to all thread updates
alakon - May 31, 2008 - 18:15
| Project: | Subscriptions |
| Version: | 5.x-2.1 |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
Subscriptions currently sends out updates to every person subscribed to a node, even if the update is unrelated to that person's discussion-- IE, member X would receive a notification if member B posts a comment in reply to member A, even though member X may not care about that discussion.
This becomes particularly bothersome when a node has 50+ replies-- that mean a person replying to one aspect of say, comment #2, gets 48+ notifications...
Many of my users have asked for the option to ONLY receive updates when THEIR comment receives a reply, or when a node they authored gets an update.
Would other people find this useful as well?
#1
You're asking for more Subscribe choices here and for #261013: One button subscription on the same day?
#2
These are just suggestions to improve the module.
If my suggestions have any merit, they would improve the module for everyone.
If they don't, then please, go ahead and ignore them.
I've had about a dozen members on my site request this very feature, and I think it would be of great help for anyone else who runs a relatively high volume site. If nodes on your site receive only a few comments, then yes, this wouldn't be much of an improvement. But if nodes regularly receive large numbers of replies, you'll get members begging you for this. I have members subscribed to over a thousand threads after just a few months -- and they get bombed every day with replies to comments they didn't make. And digest mode isn't much help-- it cuts down on the number of emails, but the clutter is still there.
#3
@alakon, perhaps this is not the right scenario, if salvis considers not to include this in subscriptions api, there is subscriptions_author, still in alpha and waiting for cool feature request :)
Blessings!
#4
Yes, but you do see that your suggestions are conflicting, don't you?
Are you offering only thread subscriptions? Over a thousand of them and growing — this is a problem...
Would you want to offer only this new subscription type as a "one-button subscription"? How would you want to call it in the context of "Subscribe to this page"?
#5
Salvis, I will answer this comment in #261013.
#6
Here are my suggestions for default behavior:
When a person authors/edits a node, by default they get subscribed to all comments posted to that node.
When a person writes a comment, by default they get only replies to their comment. However, they should get the option to subscribe to the entire discussion. Perhaps this might be done by offering three radio buttons below the textarea field of the comment posting box. We might offer: "( ) Receive a notice for all activity on this thread (x) Receive a notice when another member replies to your comment ( ) Do not receive any notifications for this thread"
#7
Those are the Auto-subscribe to new content and Auto-subscribe to updated content options. They are off by default, because a site shouldn't start creating subscriptions without a conscious decision by the admin or the user, but the admin can easily turn them on.
Radio buttons on the comment/reply/NID form? Yes, that could work, but what about the node subform and user/UID/subscriptions/node? This new type of subscription would need to be listed there, too, at least when it's active, so that the user can cancel it. How would you represent it?