Brian Carpenter writes:
I was going to respond in detail but it will be an effort in futility. My opinions are DEFINITELY not valued by you
But they are. I 100% buy the part about providing full option data and controls in the list format (as in Mailman 2). Isn't that the most important aspect of your proposal for Postorius?
In the rest of the discussion, all I did was ask what are the use cases for distinguishing admin-disabled from user-disabled. I don't know anybody better to ask than you! IMO, these use cases matter, because as I explained in another post, it seems it would be useful to provide the admin with *more* information than just the disabling agent in cases where an admin is considering reenabling a disabled subscription. I could be wrong, that's why I ask. I apologize for not ending with a question mark, I should have done so.
I ask again, please, if you know, explain when admins are reenabling disabled subscriptions (other than the OP's mass disable case, which I think we understand pretty well). I personally have never reenabled a subscription except at user request. I understand my experience is extremely limited AND biased, but it is what it is, and it's all I have right now. I wouldn't be surprised if Mark's and Abhilash's are similar (although Mark does have his bicycle club list, and they're mostly not power users). So, please share yours.
As for the abandoning Postorius part, do you think that hurts my feelings? On the contrary, if you can do that, I feel pride. Affinity being proprietary hurts my feelings (even though I understand perfectly well why it's necessary), but list admins and subscribers benefitting from Affinity is vindication of Barry's decision to split out the UIs from the core, despite the pain that causes some site admins. I had nothing to do with that decision, but I'm happy to be associated with a project that cares enough for users to enable such progress.
Sincere regards, Steve