Title:
New subscription: Entries I Have Posted
Area:
entries, esn, tracking our site participation
Summary:
Similar to 'email me copies of my comments', an 'email me copies/links to my entries' setting. Particularly useful for entries in communities.
Description:
One of the common wishes I've seen is "locate all my community entries over the years", and having a subscription to send those out as they happen (for someone who knows in the first place that they're going to want this) would help with that.
Comment notifications help with some locating community entries, because each comment notification includes the link, and top-level comments include a copy of the entry, but not all entries get comments, and not everyone has subscribed to comment notifications. This would be particularly helpful for people who post community entries but don't subscribe to notifications of new comments.
If it happens, there would be a couple things to work out.
Should it be for entries only in communities, or should it include entries to your own journal as well? Perhaps those should be separate subscriptions.
Should it only be a link to the entry, with, say, the community name and entry title (less volume to send, easier on your inbox), or should it be the whole entry (better preservation of your words in case the community up and disappears, fills up your storage space faster)? (I'm inclined to whole-entry myself, although a digest mode that took your community activity for the last day and linked to them all would certainly be interesting also.)
I'm going to go out on a limb here and guess that this would be a paid user feature, because the "email me a copy of my own comments" was a paid user feature last I checked, and subscriptions are srs bzns on the resource-eating end.
Poll #3189 New subscription: Entries I Have Posted
Open to: Registered Users, detailed results viewable to: All, participants: 46
This suggestion:
View AnswersShould be implemented as-is.
23 (50.0%)
Should be implemented with changes. (please comment)
12 (26.1%)
Shouldn't be implemented.
1 (2.2%)
(I have no opinion)
10 (21.7%)
(Other: please comment)
0 (0.0%)