#5549 - Scheduled task to auto-delete lurkers
-
By PDStig
- Added
- 18 views
| Identifier | #5549 |
|---|---|
| Issue type | Feature request or suggestion |
| Title | Scheduled task to auto-delete lurkers |
| Status | Open |
| Tags |
AutonomousOrganisation (custom) Roadmap: Over the horizon (custom) Type: Legal compliance / Privacy (custom) |
| Handling member | Deleted |
| Addon | core_cns |
| Description | Add a feature where site admins can define lurker criteria to be automatically deleted / pruned by a scheduled task.
The available criteria should contain the following: * The same options as on the delete lurker form * A "grace period" setting where lurkers are e-mailed that their account will be deleted within X days if they don't satisfy the defined requirements (if set to 0 / disabled, no emails are ever sent out) * A tick box whether members should be emailed when their account is automatically deleted from the auto lurker removal The scheduled hook should start with oldest accounts first. Ideally it should run about once every 5 minutes and only process a defined number of accounts per run (to prevent server overload; defaults at 25). We will need to track at which member we are on in the list via a value (actually, let's track at which account date / age we are on). Once the task has reached a point where members are no longer old enough to meet the defined criteria, start over at the beginning on the next run. In the SQL, we might be able to JOIN on the members table with the custom profile fields for points (for the points criteria), their cached number of posts, and possibly do an internal SELECT COUNT on the action logs to also filter out those with more than defined number of actions. Ideally we want SQL to do all the filtering so we're not reiterating over members who will never qualify to be deleted. |
| Steps to reproduce | |
| Additional information | There might be a more efficient way to do this than what I specified. |
| Funded? | No |
The system will post a comment when this issue is modified (e.g., status changes). To be notified of this, click "Enable comment notifications".
Comments
"Ideally it should run about once every 5 minutes" - I think that needs to be configurable. The timer thing is your idea, but I think it's good for 2 reasons in particular that you may not have had in mind:
1) If we email these users, we may get a bad email reputation as our bounce rate will go up a lot
2) If we have put in bad settings it mitigates the damage
I'd like to be able to have it do like 10 a day, maybe just slightly above the rate of new accounts.
"In the SQL, we might be able to JOIN on the members table with the custom profile fields for points (for the points criteria), their cached number of posts, and possibly do an internal SELECT COUNT on the action logs to also filter out those with more than defined number of actions. Ideally we want SQL to do all the filtering so we're not reiterating over members who will never qualify to be deleted." - This would be an issue on non-Conversr, but I *think* we defined delurking as a Conversr-only feature.