To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.admin.termsOpen lugnet.admin.terms in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 Administrative / Terms of Use / 490
489  |  491
Subject: 
Re: LUGNET Posting Policy Update
Newsgroups: 
lugnet.admin.terms
Date: 
Wed, 29 Dec 2004 05:40:20 GMT
Viewed: 
9011 times
  
In lugnet.admin.terms, Marc Nelson, Jr. wrote:
In lugnet.admin.terms, Larry Pieniazek wrote:
{[8]. (do not) Post non-plain-text content such as HTML, multi-part MIME
messages, or so-called “binaries” including but not limited to: images,
sounds, multimedia files, computer programs, and blocks of text created
using  binary-to-text conversion utilities such as BinHex, uuencode,
btoa, and PGP  message encryptions (short PGP signatures, however, are
permitted by the  server).}
I was referring to the fact that FTX and images within posts are prohibited

Possibly prohibited. I don't see it that way, even without clarification

What part of the TOU is ambiguous?

The part that questions whether FTX is allowed specifically. Images, as they
appear in FTX are definitely ALLOWED by that rule, because you are not posting a
binary image, as the TOU specifically indicates not to do, you are posting a URL
to an image, which FTX resolves by displaying the results of the URL. That's
different than actually trying to include the image file in your post, which
(for example) some email programs allow.

The intent of #8 of the TOU is essentially that messages should be
human-readable and therefore safest in plain text. FTX in some forms gets close
to HTML with various formatting tidbits, and its binary-ish carriage returns and
whatnot, and as such may or may not be included with HTML in #8 of the TOU. It's
not 100% clear. But as Larry says, I think we safely assume that yes, it's
allowed.

Which (if any) of your seven examples are prohibited by the new rules?

The same ones as before.

And those are...?
Quoting Larry from:
http://news.lugnet.com/admin/terms/?n=479

#1 ... unless used in a clearly bantering context ... should be avoided

#2 ... ought to be avoided.

#3 ... If true ... ought to be used with care.
If false, it clearly ought to be avoided.

#4 ... is ok.

(Admittedly Larry didn't outrightly say "yay" or "nay" to #5, but I expect it's
a "yay", but potentially borderline)

#6 .. is ... perfectly fine

#7 .. should [n]ever be disallowed.

DaveE



Message is in Reply To:
  Re: LUGNET Posting Policy Update
 
(...) What part of the TOU is ambiguous? It says "It is a condition of your use of the discussion groups that you do not: (X)" - meaning that if you do X then you may not be allowed to use the discussion groups. Are there any other parts of the TOU (...) (19 years ago, 29-Dec-04, to lugnet.admin.terms, FTX)

48 Messages in This Thread:





















Entire Thread on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact
    

Custom Search

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