[erlang-questions] Announcing Erlang.org Code of Conduct
Thu Mar 19 07:58:22 CET 2015
When advocating top posts as better than inline quotes, one reason
mentioned is that it is possible to use inline quotes to manipulate the
discussion whereas a top post will keep all quotes un-edited below.
The retort to this argument is that to prevent improper quotations no
quotes should be allowed.
I can not make the leap from, if keeping all text is better than editing
it, then the really large edit of removing all text is even better.
Someone care to explain the steps?
On 03/18/2015 05:10 PM, e@REDACTED wrote:
> On 03/18/2015 04:32 PM, Joe Armstrong wrote:
>> I like top posts:
>> 1) People have short span of attention - they only read the first few
>> lines, then decide
> pardon me,
> do you seriously assume that people have only sequential access to a
>> I know for a fact that people
>> follow links near the top of my
>> blogs and not near the end - the stuffs so boring they don't get to
>> the end.
> very good filter for those who are not interested in a productive
>> 2) Interleaving replies with previously posted text often results in a
>> mess where it's impossible
> cooking often results in a mess.
> repair often results in a mess.
> publishing books often results in a mess.
> programming often results in a mess.
>> to see who said what, especially if their are multiple interleaving. I
>> have recently heard of
>> deliberate manipulation of previously published text, in attempt to
>> manipulate a discussion.
> in order to prevent improper quotations let's just omit all quotation
> at once!
> good riddance!
> i also suggest to forbid all tools that might be misused.
>> Separately posted articles makes it clear who said what
> leaving totally unclear WHY did they say that.
>> 3) Top postings aren't really at the top - the subject line in the
>> mail is at the top.
> "Return-Path:" line is on the top.
>> 4) The topmost posting is often the most interesting and an indication
>> that a topic is worth of a discussion.
> it is so incomprehensible and ridiculous claim that i just decided to
> quote it as is.
> erlang-questions mailing list
More information about the erlang-questions