 | | Re: Bulk Lego Auctions
|
|
(...) I honestly can't remember if this is true or not once the charter got revised... LUGNET in general has a policy that posts never are modified, ever, but I forget if that policy applies to charters. I *thought* BST has had charter revisions but (...) (23 years ago, 4-Jan-02, to lugnet.admin.general)
|
| |
| | Re: Bulk Lego Auctions
|
|
(...) I don't use the NNTP interface, but isn't the first message in each group it's charter? So if your newsreader supports it, you could just look at the first message, and see the charter? Also, if you're trying to look up the charter, I don't (...) (23 years ago, 4-Jan-02, to lugnet.admin.general)
|
| |
| | Re: Bulk Lego Auctions
|
|
(...) If this is a problem, and I'm not sure it is, I'm sure Todd could have the server automatically re-post the charter every X days or N posts. A quick look at .announce shows that the group consistently receives highlighted posts: (URL) on this, (...) (23 years ago, 4-Jan-02, to lugnet.admin.general)
|
| |
| | Re: Bulk Lego Auctions
|
|
(...) Because of revisions, the most current charter is not always post #1 but with a news reader you should be able to sort by topic. Locate message #1 and then sort to see if others show up with the same topic heading. With a news reader this is (...) (23 years ago, 4-Jan-02, to lugnet.admin.general)
|
| |
| | Re: Bulk Lego Auctions
|
|
(...) Is it always in message #1? What if the charter has been revised at some point later on? It's easy in my newsreader (emacs+gnus) to jump to message #1, or any message in the group I'm reading if I know its number, but I didn't think that was (...) (23 years ago, 4-Jan-02, to lugnet.admin.general)
|
| |
| | Cool LUGNET MOC of the Week (was: lugnet.announce is not for MOCs)
|
|
(...) An addendum to this idea of mine (I can't shake it...it's a good idea, so it's rattling around in my head...): If there were a lugnet.build.announce, everyone with a new MOC of any genré would post their MOC announcement there and in their (...) (23 years ago, 4-Jan-02, to lugnet.admin.general)
|
| |
| | Re: Bulk Lego Auctions
|
|
(...) You asked how one is supposed to determine things. I answered. No critcism of your first post to .announce was intended, I've said (twice or three times now) that it fits the charter as it's written. I think the charter needs changing but (...) (23 years ago, 4-Jan-02, to lugnet.admin.general)
|
| |
| | Re: Bulk Lego Auctions
|
|
(...) Is it true that there's no easy way? When I was viewing lugnet via NNTP I had my newsreader set to never discard posts (that was a long time ago, it took a lot less space than it would now) so I could go look at post #1 in a group without too (...) (23 years ago, 4-Jan-02, to lugnet.admin.general)
|
| |
| | Re: lugnet.announce is not for MOCs
|
|
(...) A thought I have is to have a lugnet._.announce for each theme and probably some of the other areas also where folks could announce new MOCs or other newsworthy items related to that theme. It would then provide an easy place to go find just (...) (23 years ago, 4-Jan-02, to lugnet.admin.general)
|
| |
| | Re: lugnet.announce is not for MOCs
|
|
"Matthew Gerber" <matthew@digitaliris.com> wrote in message news:GpDzIt.Ltw@lugnet.com... (...) fairly (...) content (...) across (...) made (...) Hey, I'm for it! -Tim (23 years ago, 4-Jan-02, to lugnet.admin.general)
|
| |
| | Re: Bulk Lego Auctions
|
|
(...) My apologies for making any assumptions. I wondered if the mail had perhaps bounced at the other end without generating an error at my end. (...) As mentioned (twice or three times now) I did, most certainly, read the charter for that group. I (...) (23 years ago, 4-Jan-02, to lugnet.admin.general)
|
| |
| | Re: lugnet.announce is not for MOCs
|
|
(...) Well, lugnet.build can be rather high volume at times, and announcements can get lost in the noise. It's nice to have a place where MOCs can be announced with followups directed elsewhere. I'd like to see it under lugnet.announce.{moc,build} (...) (23 years ago, 4-Jan-02, to lugnet.admin.general)
|
| |
| | Re: Bulk Lego Auctions
|
|
(...) I don't know what the ratios are as to who uses the web vs. nntp interfaces, but for people using nntp there is no easy way to access the charter of a newsgroup. --Bill. (23 years ago, 4-Jan-02, to lugnet.admin.general)
|
| |
| | Re: Shop At Home catalog Engine Shed
|
|
(...) If you're adding comments to the message as you add the other newsgroup(s), then I think it's reasonable. But to just crosspost it for the sake of spreading the word is in violation of the spirit of the lugnet.lego.* restriction. Whether you (...) (23 years ago, 3-Jan-02, to lugnet.admin.general)
|
| |
| | Re: lugnet.announce is not for MOCs
|
|
(...) Not that my opinion counts for anything (since I haven't found the time to build a darn thing lately), but if I may, I would like to chime in with my support for the idea of lugnet.build.announce for strictly LUGNET-wide MOC announcements, for (...) (23 years ago, 3-Jan-02, to lugnet.admin.general)
|
| |
| | Re: Bulk Lego Auctions
|
|
(...) Maybe your mail is being bounced silently on the way in or out? I sent you a complaint via email when you posted the second time but got no reply, leading me to believe you never saw it or your reply never made it back to me. (...) Read the (...) (23 years ago, 3-Jan-02, to lugnet.admin.general)
|
| |
| | Re: lugnet.announce is not for MOCs
|
|
(...) Yes. Or maybe just lugnet.build... the announce is a bit redundant, perhaps. (...) It's not the low volume per se, it's the pithiness. Posts that appear there are indeed breaking news. When I want breaking news I would like to review .announce (...) (23 years ago, 3-Jan-02, to lugnet.admin.general)
|
| |
| | Re: lugnet.announce is not for MOCs
|
|
(...) IMHO, this would be the better choice, to meld well with the current architecture. .moc.announce is counter-intuitive with what's currently in place. May I suggest that if an .announce.moc group is set up that it does not boost posts into the (...) (23 years ago, 3-Jan-02, to lugnet.admin.general)
|
| |
| | Re: lugnet.announce is not for MOCs
|
|
(...) Well, lugnet.bulid.announce would be more appropriate in that case. No need to create a new top-level hierarchy. Do the brickshelf and LSAHS subgroups bother you in the web interface? Probably not, but only because of their volume of traffic. (...) (23 years ago, 3-Jan-02, to lugnet.admin.general)
|
| |
| | Re: Shop At Home catalog Engine Shed
|
|
(...) If someone feels that a post in a .lego group has relevance to a particular theme or group (whether it be train or castle or what-have-you), why shouldn't they cross-post it? If that someone happens to be a LEGO employee without posting (...) (23 years ago, 3-Jan-02, to lugnet.admin.general)
|
