 | | Re: Newsgroup structure: some tough decisions
|
|
(...) Hmmm. I'm not sure we need a .au.org. Couldn't we just have .au.LegOz, .au.SLUG, .au.BUG, .au.MUG, etc., with any national stuff just going in .au.LegOz? This forces people to think about which organisation they're posting to / about. (...) (...) (24 years ago, 15-Mar-01, to lugnet.admin.nntp, lugnet.loc.au, lugnet.org.au)
|
| |
| | Re: Newsgroup structure: some tough decisions
|
|
(...) I like the idea, so I'm piping up now ;~). One of the main reasons we asked for .org.au was to stop Australian .market-style flogs from getting lost in the USian traffic. This was always (IMHO) a fairly awkward solution, and I don't think it (...) (24 years ago, 15-Mar-01, to lugnet.admin.nntp, lugnet.loc.au, lugnet.org.au)
|
| |
| | Re: Official vs. unofficial LEGO postings
|
|
So Ashley can no longer post in the legoland thread? If so, I do not see why not - he gave us good information and it would not belong in any other threads - and it was official lego(land) information. And what about the lego guy posting in the (...) (24 years ago, 15-Mar-01, to lugnet.admin.nntp, lugnet.general)
|
| |
| | Re: Newsgroup structure: some tough decisions
|
|
(...) I just want to try to curb kneejerk reactions. It would be a big change, not without disadvantages, but I think for the better in the long run, unless I'm missing something. --Todd (24 years ago, 15-Mar-01, to lugnet.admin.nntp)
|
| |
| | Re: Newsgroup structure: some tough decisions
|
|
(...) Do you mean the kind of cross-org talk that happens in groups like lugnet.org and lugnet.org.xx, or the kind that happens when someone from one org posts in another org's group? I don't see a reason why lugnet.org couldn't and shouldn't still (...) (24 years ago, 15-Mar-01, to lugnet.admin.nntp)
|
| |
| | Official vs. unofficial LEGO postings
|
|
FYI, a filter was installed today on the news server to accept lego.com postings (i.e., LEGO Company employees using their official email address) in the following groups only: lugnet.lego lugnet.lego.announce lugnet.lego.direct (essentially the (...) (24 years ago, 15-Mar-01, to lugnet.admin.nntp, lugnet.lego.direct)
|
| |
| | Re: 7-Eleven and Starbucks
|
|
(...) (I tried to email you, but ... of course ... the mail bounced) Uh, Tony, you really ought to fill out the news-posting setup form again for your new email address. (URL) (24 years ago, 15-Mar-01, to lugnet.trains, lugnet.town, lugnet.admin.nntp)
|
| |
| | (canceled)
|
|
|
| |
| | Re: I can't access LUGNET through nntp today
|
|
(...) 199? You mean 119, ya? (...) Odd... traceroute from 209.68.63.236 (lugnet.com) to your IP address just sits there and hangs, then gives a "can't find" error. Same with nslookup. Either this is some low-level TCP/IP networking issue or some (...) (24 years ago, 15-Mar-01, to lugnet.admin.nntp)
|
| |
| | Re: Reducing the level of chatter in lugnet.lego.direct
|
|
(...) Yes, please add my name to that list ;] In-your-face notification/warning is a Good Thing. I already "lose" threads that I post in because I didn't notice a FUT was set. 'Course I've been known to lose my keyboard, too, but that's a different (...) (24 years ago, 15-Mar-01, to lugnet.admin.nntp)
|
| |
| | Re: Reducing the level of chatter in lugnet.lego.direct
|
|
(...) ROTFL True - I hadn't thought of that. Guess an adviso is needed. SRC L#765 (24 years ago, 14-Mar-01, to lugnet.admin.nntp)
|
| |
| | Re: I can't access LUGNET through nntp today
|
|
(...) the (...) min. (...) I am connecting through port 199 (yesterday I tried 1119, 8000, and 8080 as a test...same results). I am using Netscape Communicator 4.7's built-in newsreader my ip address is 152.10.28.104 Thanks for your help. -- Thomas (...) (24 years ago, 14-Mar-01, to lugnet.admin.nntp)
|
| |
| | Re: I can't access LUGNET through nntp today
|
|
I've noticed that if you use IE and Netzero as an ISP getting messages is_very_ _VERY_ long. Is this the case? -- Kenneth A. Drumm Ph.D. "Thomas Main" <main@appstate.edu> wrote in message news:GA74so.1M0@lugnet.com... (...) tried to (...) message, (...) (24 years ago, 14-Mar-01, to lugnet.admin.nntp)
|
| |
| | Re: Top 1000 noisemakers (was: Re: Posting frequency?)
|
|
In lugnet.people, Todd Lehman writes: <snip> Wow, I've been (mostly) away for almost a year and I'm still the #31 in the list of noisemakers: *fear* :-) Richard (24 years ago, 14-Mar-01, to lugnet.people, lugnet.admin.nntp)
|
| |
| | Re: I can't access LUGNET through nntp today
|
|
I've noticed that if you use IE and Netzero as an ISP getting messages is_very_ _VERY_ long. Is this the case? -- Kenneth A. Drumm Ph.D. "Thomas Main" <main@appstate.edu> wrote in message news:GA74so.1M0@lugnet.com... (...) tried to (...) message, (...) (24 years ago, 14-Mar-01, to lugnet.admin.nntp)
|
| |
| | Re: I can't access LUGNET through nntp today
|
|
(...) Which port are you connecting with? The default (119)? What groups are in your subscription list? What software client are you using? Can you email me your IP address and I'll try doing a traceroute. --Todd (24 years ago, 14-Mar-01, to lugnet.admin.nntp)
|
| |
| | Re: Reducing the level of chatter in lugnet.lego.direct
|
|
(...) If it were automatic and silent (i.e., no error message), I worry that people would post and then say, "Hey, where did my post go? It didn't show up! I'll post it again. Hey, where did my post go?" --Todd (24 years ago, 14-Mar-01, to lugnet.admin.nntp)
|
| |
| | Re: An Idea for NNTP headers.
|
|
(...) Is CLAX86 a newsreader or a protocol extension? (...) What kind of info would you suggest be included? (...) Indeed! --Todd (24 years ago, 14-Mar-01, to lugnet.admin.general, lugnet.admin.nntp)
|
| |
| | Re: I can't access LUGNET through nntp today
|
|
(...) Hmmm...it seems that my initial connect is what is terribly slow, and then another long wait until the first message comes up. I just reconnected to the news server and it seems to take about 3 mins. to connect, then another 3 min. to display (...) (24 years ago, 14-Mar-01, to lugnet.admin.nntp)
|
| |
| | Re: I can't access LUGNET through nntp today
|
|
In lugnet.admin.nntp, Thomas Main writes: <snip> (...) Just an update, moving between messsages is a lot faster now...moving between messages in groups is also moving at a decent, although lesser speed. -- Thomas Main main@appstate.edu (24 years ago, 14-Mar-01, to lugnet.admin.nntp)
|
