![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
![[site community profile]](https://www.dreamwidth.org/img/comm_staff.png)
Improve entry subscription notification - include title, introduce delay
Title:
Improve entry subscription notification - include title, introduce delay
Area:
notifications, entries
Summary:
When sending notifications of new entries, set a delay for most cases, and include the entry's title.
Description:
Currently, subscribing to be notified of new entries in a given community or journal results in a notification that there is a new entry, and a link.
It would be useful to the person getting the notification to include more information about that entry. However, the current lack of information is probably deliberate, because no matter how many things are done to make sure nothing is posted with the wrong security or -- well, any of the other possible scenarios where something that wasn't meant to be shared is shared -- no matter how careful Dreamwidth is to make such situations unlikely, they will still occasionally happen.
To further decrease the chances that someone who's not meant to see the entry will be notified that it exists, I propose to delay the sending of most new-entry notifications for about 5 minutes (the same delay before new entries appear on the Latest Things page), which gives time for someone posting an entry to notice and edit before a notification is sent. (People with very slow internet connections or who have been pulled away from the internet would still have a higher chance of something slipping through.)
In exchange for the delay, send the title of the entry along with the emailed notification, and perhaps the tags.
For community administrators with subscriptions to new entries in their own communities, would it be acceptable to send a notification immediately, and with title and tags?
(This suggestion brought to you by Azz's automatic paranoia that something horrible is happening when there is a new entry in dw_antispam while out-and-about with mobile email but crappy internet from the smartphone.)
This suggestion:
Should be implemented as-is.
18 (38.3%)
Should be implemented with changes. (please comment)
6 (12.8%)
Shouldn't be implemented.
4 (8.5%)
(I have no opinion)
17 (36.2%)
(Other: please comment)
2 (4.3%)
no subject