To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.admin.generalOpen lugnet.admin.general in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 Administrative / General / 4124 (-10)
  Re: Posting problem with the web-interface!
 
(...) This is clear at least - Todd, CNews is in violation of this. I think implementing it could be a good idea, but not high-priority at this time, as I haven't noticed anything breaking from them. (...) Ah, the infamous Son-of. The problem there (...) (27 years ago, 8-Jan-00, to lugnet.admin.general)
 
  Re: Who hosts lugnet.com?
 
(...) (URL) of people here use them to host their websites. (27 years ago, 8-Jan-00, to lugnet.admin.general)
 
  Who hosts lugnet.com?
 
A friend of mine just bought a domain name (shafted.org, isn't it cool?!) and we're looking for a good web page hosting service. Which company hosts lugnet? I saw someone mention their name, but I couldn't find the reference again. Thx :) (27 years ago, 8-Jan-00, to lugnet.admin.general)
 
  Re: Posting problem with the web-interface!
 
(...) I think you are correct. 1038 doesn't seem to specify any limit. The Internet draft at <URL:(URL) suggests 998 as a _minimum_ ("MUST") and lines of arbitrary length as recommended ("SHOULD"). I'm not sure where they got that number from; it (...) (27 years ago, 8-Jan-00, to lugnet.admin.general)
 
  Re: Posting problem with the web-interface!
 
(...) Ok, I think I've finally got it narrowed down. Looks like there's a horrible bug in the spawn() function of spawn.c of the NNTP Reference Implementation. Here's the loop where it spools stdin out to a tempfile, minus a few superfluous lines of (...) (27 years ago, 8-Jan-00, to lugnet.admin.general)
 
  Re: Posting problem with the web-interface!
 
(...) Note that the GNKSA is here itself quoting another document, the in-progress update for RFC 1036. (27 years ago, 8-Jan-00, to lugnet.admin.general)
 
  Re: Posting problem with the web-interface!
 
(...) No. See <URL:(URL) and <URL:(URL) The magic number seems to actually be 998. (...) Yes. From the GNKSA, above: <<Followup agents SHOULD not shorten References headers. If it is absolutely necessary to shorten the header, as a des- perate last (...) (27 years ago, 8-Jan-00, to lugnet.admin.general)
 
  Re: Posting problem with the web-interface!
 
(...) Eeek, but it shouldn't *chop* at 512 characters, should it?! :-p What you said before -- keeping the first reference and eliminating some of the middle ones -- seems much more sane. That way they're all still <.*> . (...) slrn? (...) Dunno. (...) (27 years ago, 8-Jan-00, to lugnet.admin.general)
 
  Re: Posting problem with the web-interface!
 
On Sat, 8 Jan 2000 04:45:50 GMT, jasper@janssen.dynip.com (Jasper Janssen) wrote: References: <Fnv9B7.H2D@lugnet.com> <387356CD.F163AA7@voyager.net> <3882db17.91566531@lugnet.com> <38741821.9B62453@uswest.net> <38741B3F.F8D3F7F6@voyager.net> (...) (27 years ago, 8-Jan-00, to lugnet.admin.general)
 
  Re: Posting problem with the web-interface!
 
(...) Yeah.. I asked a few times about the related problem where the end of References: and the other headers after it show up after a \n. I suspect that CNews always inserts a \n after truncating a References: line to 511 (why not 512 beats me), (...) (27 years ago, 8-Jan-00, to lugnet.admin.general)

Next Page:  5 more | 10 more | 20 more
Redisplay Messages:  All | Compact

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR