 | | FTX & NNTP
|
|
Todd, The introduction of FTX into LUGNET postings has caused the NNTP interface to be much less useful than it formerly was. The FTX codes are mostly readable, but can be awkward. I have a solution to the problem that should make all users happy, (...) (21 years ago, 8-Jul-03, to lugnet.admin.suggestions, lugnet.admin.nntp)
|
| |
| | Re: New LPC and Top 10 at www.rotule.qc.ca
|
|
What are all the \254 characters for??? Is this some kind of FTX-ism? If so, Todd please make it stop! --Bill. (...) (21 years ago, 25-Jun-03, to lugnet.admin.nntp)
|
| |
| | Re: link labels
|
|
(...) Actually, back in 1994, which is when RFC1738 was written, there was all sorts of discussion about URN's (Universal Resource Names), URI's (Univesal Resource Identifiers), and URL's (Universal Resource Locators). The concept is that a URN (...) (21 years ago, 17-Jun-03, to lugnet.admin.suggestions, lugnet.admin.nntp)
|
| |
| | Re: link labels
|
|
(...) What an strange and unfortunate outcome. (...) Thanks for the links. (...) I think you're right. Eudora isn't known for strict adherence to SMTP/NNTP standards, but Mozilla is a totally different story. If this is confusing a modern-day (...) (21 years ago, 17-Jun-03, to lugnet.admin.suggestions, lugnet.admin.nntp)
|
| |
| | Re: top-posting (was: posting oddities)
|
|
(...) Spiffatronic. Were I ever to have made a mistake by leaving such text topside, I would of course click it to restore karmic balance... but I don't make misteaks, so I'm not seeing that as a problem for me. :-) (...) (21 years ago, 8-Jun-03, to lugnet.admin.nntp)
|
| |
| | 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)
|
