On 11/5/20 12:20 PM, Stephen J. Turnbull wrote:
Brian Carpenter writes:
I think everyone should care that data should be removed when there is an expectation that it is being removed.
I do care, and I agree that everyone should care.
The difference is that I also think that everyone should care that data *should not* be removed when there is an expectation that it *will be retained*, and, therefore, that the base Mailman we distribute should at least ask before deleting data as a side effect of some other action.
I don't see how I can make it plainer than that, so I'm done here.
Well I am having the same difficulty. *With your statement here, let me ask you this:*
If someone subscribes to a public list, are they being notified that a user account is being created (by Mailman 3 core) as part of the subscription process?
When someone unsubscribes from mailing list, are they being notified that their data is being retained when they unsubscribe (by Mailman 3 core)?
When someone subscribes to a public list, are they being made aware that there is no way, for them, the subscriber, to remove their user data *except* if they also register an account through Postorius and then proceeds to delete that account along with them unsubscribing from a list?
Am I correct to assume when someone unsubscribes from all lists, AND deletes their Postorius/Django account, that all data on them is being removed?
So please understand that questions 1-3 are for a scenario of a subscriber that is only subscribing to a SINGLE list and has not registered with Postorius/Django.
Question 4 is dealing with someone who has multiple subscriptions AND is also a registered Postorius/Django user.
*This is what I believe are valid reasons for an expectation that data being retained:*
A subscriber who is NOT a Postorius/Django user but has multiple subscriptions to various lists on the same Mailman 3 instance subscribes from a single list. They should expect their user data to be retained because they still have active subscriptions to other lists.
A subscriber who IS a registered Postorius/Django user is subscribed to a single list and unsubscribes from that single list but did NOT delete their Postorius/Django account.
A combination of 1&2.
All I am requesting is that for single list subscribers who are not registered users of Postorius/Django, to have their user data totally removed when they unsubscribe. I simply fail to see how someone could claim a right to data retention when they unsubscribe from the one list that they were subscribed to.
This is important to me because almost all of the list members of the lists that I host fall into this category: single list member who is not a registered user of Affinity/Postorius.
If you need help implementing the "delete everything" policy in Affinity because of some insufficiency in the REST API, let me know and I will make sure the REST API allows you to do that. But I'm pretty sure it's already possible.
It has already been done with Affinity and the REST API was sufficient to allow us to do that. Thanks for offering.
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
-- Brian Carpenter Harmonylists.com Emwd.com