Re: [Pan-users] New file posting feature, broken? Misunderstood?

[Heinrich Mueller]

On 06/28/11 11:17, Duncan wrote:
> Heinrich Mueller posted on Tue, 28 Jun 2011 10:21:41 +0200 as excerpted:
>
> > Normally attachments are yEnc-encoded with uuencode, then sent. The
> > message text is discarded for now, as it would be the same message for
> > possibly 100s of files anyway.
> OK, that answers another problem/question I had, what was happening to
> the text post I expected to appear along side the binary files.
>
> (Yes, the binaries did post once I changed the cachedir perms
> approriately.  But the text post that was supposed to accompany them
> didn't appear and I wondered why.  Now I know.)
>
> Could the text appear as another post, beside the others?  That's what I
> expected.
Perhaps, but I have to figure out what the subject/text would be then.
> Meanwhile, the binary posts all seem to strip the references header.  If
> the original post triggering them (the one the user selects files to post
> on) is a reply, the references header shouldn't IMO be stripped but
> instead should remain, so the posts ultimately end up threaded under the
> post the user was replying to when he selected the files to post.
Good point, I'll change that.
> Finally, could the encoding type be made user-selectable?  For posts to
> for example gmane, the mailing list to news and back gateway, most
> readers will be seeing the message in their /mail/ clients, many of which
> don't implement yenc.  That's the problem I just had (the guy with the
> question got the files but couldn't read them).  Being able to select
> encoding type would eliminate that issue.
Yes, that's possible. But again, the problem lies in the options:
If you want to post binary data, the text would be the same for _every_
file. Or at least every upload. Well, it's the user's choice.

I'll look into all of that if a have the time, but you point out some 
valid things,
thanks.

Cheers.