Re: posting without being subscribed

[pali () cpan org]

On Saturday 11 February 2017 19:14:52 Solar Designer wrote:
> On Sat, Feb 11, 2017 at 06:46:43PM +0100, pali () cpan org wrote:
> > On Friday 10 February 2017 17:39:45 Solar Designer wrote:
> > > As far as I can tell, pali () cpan org is not subscribed.
> >
> > No, I'm not. I hope it is not a requirement.
>
> Not a requirement, but you should expect to miss replies if you're
> not subscribed, especially if you didn't state so in your posting.

Understand.

> Another issue is that now that you brought the reply back to the
> list, you almost broke the thread.  I fixed that by manually editing
> the headers on your message before approving it (as a list admin).
> Sometimes I do that, although I don't consider it to be part of my
> "job".  If a co-moderator were to approve your message first, then
> your message would have started a new thread rather than being added
> to the existing thread.  That's not great.

Hm... breaking thread should not happen... at least with non-broken 
email clients. If everybody in discussion correctly set In-Reply-To 
header then whole thread (correctly tree) will be preserved. And if 
everybody correctly set References header then even missing emails does 
not break threading visualization. Information from References headers 
provide transitive closure of thread tree from which original tree can 
be reconstructed... But if somebody does not fill References or In-
Reply-To headers then thread will be broken independently of 
subscription to list.

Now I see that message to which I replied was without In-Reply-To and 
also without References headers. So thread was already broken.

I understand that breaking threading is bad and cause problems, but in 
lot of times it is problem of broken email clients which do not fill 
needed headers :-(

> So we'd appreciate it if you do subscribe to the list for the
> duration of discussions you participate in, or at least explicitly
> state when you're posting without being subscribed (ask to be CC'ed
> on replies).
>
> Alexander