Extend "track all comments in this community" to non-members
Title:
Extend "track all comments in this community" to non-members
Area:
communities, notifications
Summary:
Extend the "members of a paid community can track comments on all entries" to be "anyone can track comments on all entries in a paid comm" so it is useful for comms like <user name=changelog> which cannot easily have open membership.
Description:
The feature to "track all comments in this community, on any entry" is available to admins in free communities and all members in paid communities. However, this leaves us a bit stuck where you want to restrict membership to just people with posting access, or for things like <user name=changelog>. I suggest that if the community is paid, or possibly just premium paid, the "track all comments" option should be available to everyone, not just members, just the same as for tracking comments on an individual entry.
Downsides: Possibly more server load, as more people will see the option and use it. However, they could already use it if the community has open membership, or by tracking every entry manually in a closed community. If it was made premium-paid only, that would be an incentive for communities to upgrade, which would counteract the extra server load. The feature is also already only for paid communities.
This suggestion:
Should be implemented as-is.
31 (62.0%)
Should be implemented with changes. (please comment)
0 (0.0%)
Shouldn't be implemented.
6 (12.0%)
(I have no opinion)
13 (26.0%)
(Other: please comment)
0 (0.0%)

no subject
no subject
no subject
no subject
Because that way openID users who only come to the site for that comm can subscribe in full to the comm. In other words, it'd be a good feature for those of us using the site for public facing blogs.
Have it for both paid comms and paid users on non paid comms would be fine for me (as a mostly paid user), but I'd really like to use DW for public facing group blogs on a serious scale, and this would be a good revenue raiser for that use.
no subject
But it's the community generating the load, and it's a lot easier to check "is the community paid" at the very beginning of sending out the notifications than it is to check "is each of these members paid" -- the former is one check, the latter could be thousands.
no subject
no subject
no subject
no subject
no subject
no subject
no subject
no subject
I'm not sure how to reconcile this concern with the helpful uses for the idea. It seems silly to want to restrict ability to track all comments to people who publicly subscribe on their reading list, but...