Administrator
|
Dear all,
There were several posts in the "Beacon for Pharo 7" thread which top-posted on top of massive unsnipped quotes that were several-previous-posts deep. IMHO this made the conversation impossible to follow. This issue has cropped up from time to time in other threads. Please adhere to basic ML etiquette [1] to maximize our effectiveness. Two essential guidelines are: 1) snip quoted material to just what's necessary to understand what's being replied to 2) Post reply /after/ the quote from the OP, not before. 1. https://www.freebsd.org/doc/en_US.ISO8859-1/articles/mailing-list-faq/etiquette.html#idp55179976 ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html
Cheers,
Sean |
On 28 May 2018 at 11:48, Sean P. DeNigris <[hidden email]> wrote: Dear all, e.g... Because it messes up the order in which people normally read text. >Why is top-posting such a bad thing? >>The lost context. >>>What makes top-posted replies harder to read than bottom-posted? >>>>Yes. >>>>>Should I trim down the quoted part of an email to which I'm replying? http://www.idallen.com/topposting.html Part of the problem is the way gmail and other clients *hide* the original text behind three ellipses dots, so its not immediately obvious how much a thread has grown. Its good to make a habit of clicking those dots immediately after clicking <Reply>. cheers -ben |
In a world of mobile phones, I think you have to accept top posting, it’s just too hard to work otherwise on a small screen ... that said, quoting a small piece to reply to - is doable, and I think we can all try to do that?
Tim Sent from my iPhone
|
On Mon, May 28, 2018 at 1:40 PM, Tim Mackinnon <[hidden email]> wrote:
Nice example of top-posting xD
|
In reply to this post by Tim Mackinnon
Tim Mackinnon <[hidden email]> wrote:
> In a world of mobile phones, I think you have to accept top posting, it’s > just too hard to work otherwise on a small screen ... that said, quoting > a small piece to reply to - is doable, and I think we can all try to do that? I strongly prefer ML-etiquette. > Sent from my iPhone That supports NewsTap, which makes it easy to not top-post. I’m not sure why lines are not broken though. Stephan |
Sent from my iPhone > On 28 May 2018, at 17:26, Stephan Eggermont <[hidden email]> wrote: > > >> Sent from my iPhone > > That supports NewsTap, which makes it easy to not top-post. I’m not sure > why lines are not broken though. I’ll try my best - but the normal iPhone mail client simply doesn’t work this way - it top posts. I think we’re on a losing battle with this one. I do have a copy of NewsTap - I’ll try it again, but I recall mail is just more convenient. I think Stef is possibly right - if we’re arguing about top vs bottom - we’re better off writing code instead - it possibly means a thread has gone in too long. Tim |
On 28/05/2018 12:36, Tim Mackinnon wrote:
> Sent from my iPhone >> On 28 May 2018, at 17:26, Stephan Eggermont <[hidden email]> wrote: >>> Sent from my iPhone >> That supports NewsTap, which makes it easy to not top-post. I’m not sure >> why lines are not broken though. > > I’ll try my best - but the normal iPhone mail client simply doesn’t work this way - it top posts. I'm fine with top posting. Even when a thread has both top and in-between replies. What really bothers me is that top posting "hides" the huge list of replies at the bottom. So a two line, top posted reply is a 500 lines of quoted email below. Top posting should be limited to one quoted email only. Otherwise you need to start referencing things by letters/numbers or better... reply below :) > I think we’re on a losing battle with this one. I agree. But I'm not giving it away without a fight :P Regards, -- Esteban A. Maringolo |
In reply to this post by Sean P. DeNigris
> Sent: Sunday, May 27, 2018 at 11:48 PM
> From: "Sean P. DeNigris" <[hidden email]> > To: [hidden email] > Subject: [Pharo-dev] IMPORTANT: ML Etiquette > > Dear all, > > There were several posts in the "Beacon for Pharo 7" thread which top-posted > on top of massive unsnipped quotes that were several-previous-posts deep. > IMHO this made the conversation impossible to follow. This issue has cropped > up from time to time in other threads. > > Please adhere to basic ML etiquette [1] to maximize our effectiveness. Two > essential guidelines are: > 1) snip quoted material to just what's necessary to understand what's > being replied to > 2) Post reply /after/ the quote from the OP, not before. 3) Use plain text. Disable any HTML formatting in your mail client. > 1. > https://www.freebsd.org/doc/en_US.ISO8859-1/articles/mailing-list-faq/etiquette.html#idp55179976 > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html > > ___ montyos.wordpress.com |
Free forum by Nabble | Edit this page |