 | | 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)
|
| |
| | Re: // and ** vs {} and [] (was: testing in rtl...)
|
|
(...) I see. With extensive modifications, I assume? I'm sure there's a way to link libperl.so to CNews but that could be unweildy to say the least. (...) Sorry I can't view the FTX results of that on my browser. But I assume that's right. (...) I (...) (21 years ago, 3-Jun-03, to lugnet.publish, lugnet.admin.nntp)
|
| |
| | top-posting (was: posting oddities)
|
|
(...) I'll do you even one better than that. Instead of moving your text to the bottom automatically and telling you that it has done this, it now simply tells you that you're going against netiquette by top-posting and it *suggests* that you move (...) (21 years ago, 3-Jun-03, to lugnet.admin.nntp)
|
| |
| | Re: Badges, buttons, and the like...
|
|
(...) Has it done weird stuff before? Like on your desktop? (...) Ya, there is, but if the second HTTP POST comes in before the first one has had a chance to stuff a copy of the article in the "recently posted" area, then the test for duplicity in (...) (21 years ago, 3-Jun-03, to lugnet.admin.nntp)
|
| |
| | Re: Badges, buttons, and the like...
|
|
(...) Maybe that's my haywire mouse - the wiring's a bit screwy in it. Isn't/wasn't there a double-posting filter? -Tim (21 years ago, 3-Jun-03, to lugnet.admin.nntp)
|
| |
| | Re: Badges, buttons, and the like...
|
|
(...) Huh...me too. The webserver log shows a GET at 23:18:05 EST (that's clicking the Reply button), followed by a POST returning 12685 bytes at 23:18:51 (that's probably the Preview button), followed by 2 POSTS both returning 3023 bytes both at (...) (21 years ago, 3-Jun-03, to lugnet.admin.nntp)
|
| |
| | Re: Badges, buttons, and the like...
|
|
(...) I wonder why this double-posted? I don't recall hitting post twice. -Tim (21 years ago, 3-Jun-03, to lugnet.admin.nntp)
|
| |
| | Re: // and ** vs {} and [] (was: testing in rtl...)
|
|
(...) CNews. (...) Doesn't that look a bit redundant? /italics/ and *boldface* What do underlined underlines look like? Like this?-- _N_ew _E_ngland _L_EGO _U_sers _G_roup Not sure how either any of those are an improvement. --Todd (21 years ago, 3-Jun-03, to lugnet.publish, lugnet.admin.nntp, FTX)
|
| |
| | Re: // and ** vs {} and [] (was: testing in rtl...)
|
|
(...) What NNTP server do you use? I was under the impression that it was written in Perl itself. [...] (...) How about a different interpretation - // and ** (and don't forget __ for underlining) might not be interpreted the same as the {} and [] (...) (21 years ago, 2-Jun-03, to lugnet.publish, lugnet.admin.nntp)
|
| |
| | Re: posting oddities (was: <dcx is cool!>
|
|
(...) Yah. (...) By adding something at the bottom that doesn't look like a sig (i.e., something that doesn't begin with "-- "). Would you prefer a button-clickie or something to override it and say, "Yes, thank you, I know what I'm doing and I (...) (21 years ago, 2-Jun-03, to lugnet.admin.nntp)
|
| |
| | Re: posting oddities (was: <dcx is cool!>
|
|
(...) How does it work now? Based on what the previous post was set to? That usually makes sense I guess, I just got bit by it. (...) in 7487... ((URL) the new content there is "in the below example..." so it belongs on top. That's where I put it. (...) (21 years ago, 2-Jun-03, to lugnet.admin.nntp)
|
