Any use case for subscribing to multiple versions
Hi, team,
Is there any use case for being subscribed to multiple versions of the same list? I can't think of a useful one.
I'm thinking of changing unsubscribe so it unsubscribes the user for any/all versions they are subscribed to, and subscribe so that if you are already subscribed to a different version, you 'switch' to the version you request the subscription for, in line with this enhancement request:
http://mlmmj.org/bugs/bug.php?id#
Is there any reason not to change this?
Ben.
Quoted 8 lines · Marco S Hyman
Quoted 2 lines · Ben Schmidt
Is there any use case for being subscribed to multiple versions of the same list? I can't think of a useful one.
I subscribe to both normal and digest versions of the lists I manage. It's the easiest way to see if I'm having digest issues. The cost is a daily hit of the delete key.
I guess this is something only the list owner would ever want. How about we make this available only from the commandline (via a switch to mlmmj-sub), but make the standard behaviour that subs unsub you from other versions of the list?
Ben.
Quoted 4 lines · Ben Schmidt
I guess this is something only the list owner would ever want. How about we make this available only from the commandline (via a switch to mlmmj-sub), but make the standard behaviour that subs unsub you from other versions of the list?
+1
JA
Quoted 2 lines · Ben Schmidt
Is there any use case for being subscribed to multiple versions of the same list? I can't think of a useful one.
Some of my lists, I subscribe to both the digest and the full version, and select items from the full version to read immediately using procmail, and otherwise I read the digests.
Signature · 4 lines
Robin Hugh Johnson Gentoo Linux: Developer, Trustee & Infrastructure Lead E-Mail : [email protected] GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85
Quoted 6 lines
Quoted 2 lines
Is there any use case for being subscribed to multiple versions of the same list? I can't think of a useful one.
Some of my lists, I subscribe to both the digest and the full version, and select items from the full version to read immediately using procmail, and otherwise I read the digests.
OK. I guess there's a use case here for regular list subscribers, though I doubt it's a common one.
Third suggestion!:
How about a single +unsubscribe to get you off the list (any and all delivery modes/versions), and +subscribe-nomail, +subscribe(-normal), +subscribe-digest and +subscribe-both (normal and digest), which switch you to that delivery mode if already subscribed (removing you from other versions)?
Ben.
Hi,
Quoted 7 lines · Ben Schmidt
Third suggestion!:
How about a single +unsubscribe to get you off the list (any and all delivery modes/versions), and +subscribe-nomail, +subscribe(-normal), +subscribe-digest and +subscribe-both (normal and digest), which switch you to that delivery mode if already subscribed (removing you from other versions)?
This sounds confusing and overcomplicated, to be honest.
Best regards,
Moritz
Quoted 7 lines · Moritz Wilhelmy
Quoted 5 lines
How about a single +unsubscribe to get you off the list (any and all delivery modes/versions), and +subscribe-nomail, +subscribe(-normal), +subscribe-digest and +subscribe-both (normal and digest), which switch you to that delivery mode if already subscribed (removing you from other versions)?
This sounds confusing and overcomplicated, to be honest.
At least I would not call it a priority.
Another completely different and really powerful (and administrator friendly) move would be to have the possibility to subscribe and unsubscribe users from the email interface, i.e., any email sent from an address listed in control/submod (and possibly control/owner) with the following syntax [email protected] would start the chain of events as if it were the email [email protected] sent by the user (envelope) [email protected]
This option, when applied to the usual subscribe, unsubscribe, subscribe-nomail, subscribe-digest, etc., would greatly reduce the need to keep logging to the server and go to the command line just to manage a busy mailing list of not very IT savvy users (and users are most of the time not very IT savvy).
r.
M.
Hi, everyone, and sorry for the LONG delays. A bunch of things have unfortunately got in the way of my Mlmmj work. I can't promise that I'll make good progress now, but I certainly hope to.
So, following up some loose ends before I do a final implementation sprint and push out a beta or release candidate.
Quoted 12 lines
Quoted 11 lines
I'm thinking of changing unsubscribe so it unsubscribes the user for any/all versions they are subscribed to, and subscribe so that if you are already subscribed to a different version, you 'switch' to the version you request the subscription for, ...
Quoted 6 lines
Quoted 2 lines
Is there any use case for being subscribed to multiple versions of the same list? I can't think of a useful one.
I subscribe to both normal and digest versions of the lists I manage. It's the easiest way to see if I'm having digest issues. The cost is a daily hit of the delete key.
Quoted 6 lines
Quoted 4 lines
I guess this is something only the list owner would ever want. How about we make this available only from the commandline (via a switch to mlmmj-sub), but make the standard behaviour that subs unsub you from other versions of the list?
+1
OK. I am going to use this approach.
I may implement the ability to do a subscribe-both via email, but this will not be documented in the default list texts. The default list texts will use the model described above.
One question for mail experts and sysadmins out there: Should 'switching' (i.e. changing an existing subscription to a different version) require moderation or confirmation? I think not. Does anyone disagree?
Cheers,
Ben.
Quoted 28 lines · Ben Schmidt
Hi, everyone, and sorry for the LONG delays. A bunch of things have unfortunately got in the way of my Mlmmj work. I can't promise that I'll make good progress now, but I certainly hope to.
So, following up some loose ends before I do a final implementation sprint and push out a beta or release candidate.
Quoted 12 lines
Quoted 11 lines
I'm thinking of changing unsubscribe so it unsubscribes the user for any/all versions they are subscribed to, and subscribe so that if you are already subscribed to a different version, you 'switch' to the version you request the subscription for, ...
Quoted 6 lines
Quoted 2 lines
Is there any use case for being subscribed to multiple versions of the same list? I can't think of a useful one.
I subscribe to both normal and digest versions of the lists I manage. It's the easiest way to see if I'm having digest issues. The cost is a daily hit of the delete key.
Quoted 6 lines
Quoted 4 lines
I guess this is something only the list owner would ever want. How about we make this available only from the commandline (via a switch to mlmmj-sub), but make the standard behaviour that subs unsub you from other versions of the list?
+1
OK. I am going to use this approach.
Quoted 8 lines
I may implement the ability to do a subscribe-both via email, but this will not be documented in the default list texts. The default list texts will use the model described above.
One question for mail experts and sysadmins out there: Should 'switching' (i.e. changing an existing subscription to a different version) require moderation or confirmation? I think not. Does anyone disagree?
And a third aspect: notification.
So, when a person switches from one version to another, should it trigger:
- confirmation
- gatekeeping (subscription moderation)
- notification to the list owner
?
I think no to all three. Any disagreement?
Ben.
Hi,
2011/6/26 Ben Schmidt <[email protected]>:
Quoted 3 lines
Hi, everyone, and sorry for the LONG delays. A bunch of things have unfortunately got in the way of my Mlmmj work. I can't promise that I'll make good progress now, but I certainly hope to.
hope all is ok - thanks for all your hard work! :-)
Quoted 8 lines
Quoted 6 lines
Quoted 4 lines
I guess this is something only the list owner would ever want. How about we make this available only from the commandline (via a switch to mlmmj-sub), but make the standard behaviour that subs unsub you from other versions of the list?
+1
OK. I am going to use this approach.
+1 from my side as well, sounds good.
Quoted 3 lines
I may implement the ability to do a subscribe-both via email, but this will not be documented in the default list texts. The default list texts will use the model described above.
+1, that's the best and less-confusing solution for end users.
Quoted 4 lines
One question for mail experts and sysadmins out there: Should 'switching' (i.e. changing an existing subscription to a different version) require moderation or confirmation? I think not. Does anyone disagree?
I don't think it's needed. Confirmation only is required when the address is subscribed the first time, but changing the subscription type, using the same address, doesn't need further confirmation.
Florian
Hi,
Quoted 5 lines
And a third aspect: notification.
So, when a person switches from one version to another, should it trigger:
Quoted 7 lines
- confirmation
- gatekeeping (subscription moderation)
- notification to the list owner?
I think no to all three. Any disagreement?
I share your view - no to all of them.
Florian
Quoted 4 lines · Ben Schmidt
- confirmation
- gatekeeping (subscription moderation)
- notification to the list owner
I think no to all three. Any disagreement?
+1 for 'no to all three'.
M.