Content Notify

Playing around with a subscription module.

General design is to have subscription types that have categories that users subscribe to. The categories have optional conditional parameters associated with these (only entity type and flags supported). If the subscription type is targeted towards an specific entity type, administrators can push out a notification about that entity from the entity edit page or a custom block (for nodes).

When the subscription is pushed, each category is checked and all matching categories are parsed to generate the user subscription list. This is placed into the system queue and ONE queue pass sends all emails to users on the list (i.e. unsuitable for big lists)