 | | Re: Excessive Cross Posting
|
|
(...) I mostly concur, I just sometimes wonder if it might be the best solution (of course the counter to that is that you get the jerks who work around the cross posting rules by posting individually to each group - but they can be TOSed). (...) (...) (24 years ago, 18-Dec-00, to lugnet.admin.general)
|
| |
| | Re: Excessive Cross Posting
|
|
(...) Again, I am not trying to be argumentative, but I don't see this problem as one of maliciousness. That is, it isn't "jerks" who are multiposting individual groups, or not setting followups correctly. Just lazy people and people who know (...) (24 years ago, 18-Dec-00, to lugnet.admin.general)
|
| |
| | Re: Excessive Cross Posting
|
|
(...) I guess I should have clarified that I don't think the current round of excessive cross posting is jerks, I'm just pointing out that trivial things like requiring a follow-up header when cross posting doesn't remove the possibility of jerks (...) (24 years ago, 18-Dec-00, to lugnet.admin.general)
|
| |
| | Re: Excessive Cross Posting
|
|
(...) Thanks for the clarification, I think we're in total agreement. I think it WOULD be nice to have some automation that helped people remember not to excessively cross post (and the place to put the one page netiquette FAQ link for people to (...) (24 years ago, 18-Dec-00, to lugnet.admin.general)
|
| |
| | Re: Excessive Cross Posting
|
|
(...) I can't think of a practical example for putting multiple groups in the followup-to header. Maybe it's just me ??? I don't think jerk-proofing needs to be a *high* priority around here, although it's good to jerk-proof when it doesn't impact (...) (24 years ago, 18-Dec-00, to lugnet.admin.general)
|
| |
| | Re: Excessive Cross Posting
|
|
(...) There are reasons to keep a thread in multiple groups, see below. (...) Problem with requiring it on ANY cross posting is the discussions which legitimately belong in two or even three groups. (...) Because of how the web interface works (and (...) (24 years ago, 18-Dec-00, to lugnet.admin.general)
|
