 | | Re: Poll: Use of Images in Signatures
|
|
Todd, In the below-quoted message, some of the lines are exactly 80 characters. This causes them to wrap in my newsreader (GNU Emacs + GNUS). Please change the wrapping code to wrap at 72 which has long been the USENET standard. Note that in this (...) (21 years ago, 7-Jun-03, to lugnet.admin.nntp)
|
| |
| | Re: BRICKFEST MOONBASE (follow-up count)
|
|
(...) If you're using NNTP it's very unlikely that a .signature file is going to be FTX-safe.... I think that an exception in this case is warranted. (21 years ago, 6-Jun-03, to lugnet.admin.nntp)
|
| |
| | Re: BRICKFEST MOONBASE (follow-up count)
|
|
(...) Maybe we could define some optional add-on header that says, "Please interpret my sig as plain text even if I'm posting in FTX from an NNTP newsreader." --Todd (21 years ago, 5-Jun-03, to lugnet.admin.nntp, FTX)
|
| |
| | Re: BRICKFEST MOONBASE (follow-up count)
|
|
(...) Oh, BTW, the use of the 'Content-Type:' header isn't guaranteed to be supported forever. The server now posts FTX messages using a different header, because 'Content-Type: text/x-ftx' was causing problems for MSOE users (and some other (...) (21 years ago, 5-Jun-03, to lugnet.admin.nntp, FTX)
|
| |
| | Re: BRICKFEST MOONBASE (follow-up count)
|
|
As an experiment I posted the below-quoted message from my NNTP newsreader by using the Content-Type: text/x-ftx header. It worked! Only trouble is, it didn't recognize my signature file. Signature files should be treated as literal text when (...) (21 years ago, 5-Jun-03, to lugnet.admin.nntp, FTX)
|
