| | Re: Announcing FTX for discussion groups
|
|
(...) What if lines beginning with "#" in FTX denoted comments, and the URLs of referenced resources were summarized in a comment block? In other words, if someone said [LEGOSet 6954_1] and [LDrawPart 3004:4] it would append something like this: # (...) (21 years ago, 29-May-03, to lugnet.admin.nntp, lugnet.publish)
|
|
| | Re: Announcing FTX for discussion groups
|
|
(...) Yes, but the problem is that not all FTX extensions work as well as others. For example the set and part database items, polls, etc. will not display properly on a plaintext system. For those you should convert the FTX code to an URL that (...) (21 years ago, 29-May-03, to lugnet.admin.nntp, lugnet.publish)
|
|
| | Re: Announcing FTX for discussion groups
|
|
(...) That's a really good point, and so true!!! We gotta help each other out. Gotta love it. Free thought and brick treats while in the machine. I get the job done and always manage in a little fun. No shame there. e (21 years ago, 29-May-03, to lugnet.admin.nntp)
|
|
| | Re: Announcing FTX for discussion groups
|
|
Good suggestion. While sometimes I may like to play, it could annoy some people unintentionally, so by all means; if an FTX filter for E-mail and NNTP could be implimented - That would be great. I'm no expert, but the thought is there. e (...) snip (...) (21 years ago, 29-May-03, to lugnet.admin.nntp)
|
|
| | Re: Announcing FTX for discussion groups
|
|
(...) OK, I can think of four different RFC-2045 compliant workarounds: 1. Content-Type: text/plain; charset="ISO-8859-1" (FTX) 2. Content-Type: text/plain (FTX); charset="ISO-8859-1" 3. Content-Type: text/plain; charset="ISO-8859-1"; x-ftx=1.0 4. (...) (21 years ago, 29-May-03, to lugnet.admin.nntp)
|