Subject:
|
Re: NO auction updates in non-auction groups (was: Re: FA : Soccers sets + much much more)
|
Newsgroups:
|
lugnet.admin.general
|
Date:
|
Thu, 19 Aug 1999 03:34:43 GMT
|
Viewed:
|
335 times
|
| |
|
|
In lugnet.admin.general, "Frank Filz" <ffilz@mindspring.com> writes:
> [...]
> Suggested filters:
>
> Any message with an apparent URL corresponding to any of the well known
> auction sites will be filtered from any group other than
> lugnet.market.auction and lugnet.market.theory (that may not be needed,
> though one might reasonably refer to an auction site or even a specific
> auction item in a theory discussion). Some kind of special exception rule
> might be allowed for lugnet.announce to announce the opening of a new
> auction site if that kind of announcement would be legit (I think it would
> be, but I could also see the case against).
It just so happens (any funny how it happens! :-) that someone earlier today
posted a legit URL on eBay to lugnet.general:
http://www.lugnet.com/general/?n=6781
And of course, the .off-topic.test group is also valid for testing out URL
line wrapping issues, even for actual particular auctions:
http://www.lugnet.com/off-topic/test/?n=610
http://www.lugnet.com/off-topic/test/?n=611
http://www.lugnet.com/off-topic/test/?n=612
http://www.lugnet.com/off-topic/test/?n=613
And it's also perfectly valid (I don't see why not) in lugnet.general to
post a URL of an active or past auction on eBay or any other auction siste
to help illustrate a pricing data point -- as long as it isn't shameless
shelf-promotion by someone. There's no way the server could make a judgment
call like that in a filter.
> Any message with "(FA)", "[FA]", or "FA:" (and possibly other combinations)
> in the subject would be rejected to any group other than
> lugnet.market.auction, similarly FS limited to lugnet.market.buy-sell-trade.
I would worry that some non-English language uses "FA:" or "Fa:" in place of
"RE:" or "Re:" in subject lines.
For example, I've seen quite a few posts in various places which use "FW:"
or "Fw:", whatever that means (maybe it means "forwarded").
> Any other easily identifiable, and very "sure" qualifiers?
I can't think of any which wouldn't be immediately defeatable by anyone
wishing to defeat them.
> Would there be a reasonable set of keys to detect for-sale items which are
> actually auctions, and pop out a rejection along with a reminder of the
> rule, and either suggestions of how to re-word for acceptability, or a
> "password" to use to re-submit with the understanding that you got a false
> positive, and if it really is an auction, your posting priviledges are going
> to be suspended.
I wish there were a way via NNTP to send longer error messages back to the
user. It would be helpful if you could say, "Hey, your post looks like it
might be an auction announcement or update in the wrong group. If you're
really sure that you're not breaking any rules, you can go ahead and
re-submit it, otherwise you should post it only to the .market.auction
group." Or even if you could ask the client a Yes/No question. But AFAIK
that's not possible.
> Oh, another filter... bounce any message with html keywords in a group other
> than lugnet.publish or lugnet.off-topic.geek (any others where discussion of
> html is acceptable?) (I bow my head in shame for forgetting the no html rule
> once, even more so because I knew I was being lazy - sentence him to build a
> 50 foot sign "I will not post html" out of Megabloks, and you can't come out
> of the room until the sign is suffiently sturdy that it won't fall apart in
> a light breeze...:-).
What do you do if someone has HTML in their sig? I know someone who signs
all of his correspondence like this:
</rr>
What if someone is talking about Star Wars T.I.E. fighters?--
<o> <-O->
What if someone makes a list like this?--
<a> Milk
<b> Cheese
<c> Coffee
> It may seem like we're all adults and shouldn't need filters, but as the
> community grows, we're going to have more and more incidents, and I'd rather
> see a filter block the post from ever making it onto the server.
Me too. Now there are a few filters in place which do quite a bit of
filtering already of purely objective things that the server can identify
easily:
- Posts to .announce.* must direct followups elsewhere
- Posts can't followup to .announce.*
- Posts outside of .cad.* and .off-topic.test can't contain LDraw DATs
- Posts can't be multipart/alternative, multipart/mixed, or text/html --
they have to be plain text
- Posts can't contain uuencoded/BinHex/etc. binaries
- etc.
But those cover black & white cases.
--Todd
|
|
Message is in Reply To:
5 Messages in This Thread:
  
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
