Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.mobile.android > #57809
| From | "J. P. Gilliver (John)" <G6JPG-255@255soft.uk> |
|---|---|
| Newsgroups | comp.mobile.android |
| Subject | "tl; dr" (was: Re: charging policy) |
| Date | 2018-11-23 15:28 +0000 |
| Organization | 255 software |
| Message-ID | <G2KBKRikyB+bFw17@255soft.uk> (permalink) |
| References | (7 earlier) <pCzKXLONbu9bFw6F@255soft.uk> <221120181254418054%nospam@nospam.invalid> <v7Vb5OUX8x9bFwoL@255soft.uk> <231120180114292026%nospam@nospam.invalid> <g5pvhgF46giU1@mid.individual.net> |
In message <g5pvhgF46giU1@mid.individual.net>, Andy Burns <usenet@andyburns.uk> writes: >nospam wrote: > >> it's a common internet idiom to mark a summary of something longer. >> that's all. > >I see it used both ways, originally a bare 'tl;dr' reply meant > >"you wasted your time writing an unnecessarily detailed message because >I didn't read it" Yes, that's how I encountered it. > >Over time, it seems to have developed into a pre-emptive way of >including a terse summary for the benefit of those who might otherwise >send a 'tl;dr' reply. > I hadn't realised that. I still think it's at least confusing if used in the second way, because of the initial use. -- J. P. Gilliver. UMRA: 1960/<1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf Have you ever heard about a petition, disagreed with it, but been frustrated that there's no way you can *show* that you disagree? If so, have a look at https://petition.parliament.uk/petitions/232770 - and please pass it on if you agree, especially to twitter, facebook, gransnet/mumsnet, or any such forum. I'm too lazy to have a bigger ego. - James May, RT 2016/1/23-29
Back to comp.mobile.android | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
charging policy "Linea Recta" <bleep.bleep@bleep.invalid> - 2018-11-21 18:24 +0100
Re: charging policy Andy Burns <usenet@andyburns.uk> - 2018-11-21 17:36 +0000
Re: charging policy Libor Striz <poutnik4REMOVEnntp@CAPITALSgmail.com.INVALID> - 2018-11-21 19:02 +0100
Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-21 15:10 -0500
Re:charging policy Libor Striz <poutnik4REMOVEnntp@CAPITALSgmail.com.INVALID> - 2018-11-21 18:53 +0100
Re: Re:charging policy Frank Slootweg <this@ddress.is.invalid> - 2018-11-21 18:42 +0000
Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-21 15:10 -0500
Re: charging policy Libor Striz <poutnik4REMOVEnntp@CAPITALSgmail.com.INVALID> - 2018-11-22 07:13 +0100
Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-22 01:50 -0500
Re: charging policy Libor Striz <poutnik4REMOVEnntp@CAPITALSgmail.com.INVALID> - 2018-11-22 09:15 +0100
Re: charging policy "J. P. Gilliver (John)" <G6JPG-255@255soft.uk> - 2018-11-22 16:09 +0000
Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-22 11:57 -0500
Re: charging policy "J. P. Gilliver (John)" <G6JPG-255@255soft.uk> - 2018-11-22 16:18 +0000
Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-22 11:57 -0500
Re: charging policy "J. P. Gilliver (John)" <G6JPG-255@255soft.uk> - 2018-11-22 17:26 +0000
Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-22 12:54 -0500
Re: charging policy "J. P. Gilliver (John)" <G6JPG-255@255soft.uk> - 2018-11-22 21:26 +0000
Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-23 01:14 -0500
Re: charging policy Andy Burns <usenet@andyburns.uk> - 2018-11-23 09:28 +0000
"tl; dr" (was: Re: charging policy) "J. P. Gilliver (John)" <G6JPG-255@255soft.uk> - 2018-11-23 15:28 +0000
Re: charging policy 123456789 <12345@12345.com> - 2018-11-22 18:39 -0700
Re: charging policy 123456789 <12345@12345.com> - 2018-11-22 10:22 -0700
Re: charging policy Frank Slootweg <this@ddress.is.invalid> - 2018-11-22 18:45 +0000
Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-22 13:47 -0500
Re: charging policy "NY" <me@privacy.net> - 2018-11-22 20:40 +0000
Re: charging policy David Higton <dave@davehigton.me.uk> - 2018-11-22 21:29 +0000
Re: charging policy 123456789 <12345@12345.com> - 2018-11-22 18:39 -0700
Re: charging policy 123456789 <12345@12345.com> - 2018-11-22 18:39 -0700
Re: charging policy "J. P. Gilliver (John)" <G6JPG-255@255soft.uk> - 2018-11-22 21:30 +0000
Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-23 01:14 -0500
Re: charging policy "J. P. Gilliver (John)" <G6JPG-255@255soft.uk> - 2018-11-23 15:26 +0000
Re: charging policy Frank Slootweg <this@ddress.is.invalid> - 2018-11-23 16:13 +0000
Re: charging policy Frank Slootweg <this@ddress.is.invalid> - 2018-11-23 19:52 +0000
Re: charging policy Frank Slootweg <this@ddress.is.invalid> - 2018-11-23 21:29 +0000
Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-23 16:40 -0500
Re: charging policy "J. P. Gilliver (John)" <G6JPG-255@255soft.uk> - 2018-11-23 21:48 +0000
Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-23 17:06 -0500
Re: charging policy "J. P. Gilliver (John)" <G6JPG-255@255soft.uk> - 2018-11-23 22:09 +0000
Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-23 17:23 -0500
Re: charging policy The Real Bev <bashley101@gmail.com> - 2018-11-23 21:00 -0800
Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-24 09:05 -0500
Re: charging policy Frank Slootweg <this@ddress.is.invalid> - 2018-11-24 15:46 +0000
Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-24 10:51 -0500
Re: charging policy 123456789 <12345@12345.com> - 2018-11-24 10:01 -0700
Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-24 12:55 -0500
Re: charging policy 123456789 <12345@12345.com> - 2018-11-24 13:07 -0700
Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-24 16:33 -0400
Re: charging policy 123456789 <12345@12345.com> - 2018-11-24 18:52 -0700
Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-25 00:42 -0500
Re: charging policy 123456789 <12345@12345.com> - 2018-11-25 11:33 -0700
Re: charging policy "J. P. Gilliver (John)" <G6JPG-255@255soft.uk> - 2018-11-25 19:06 +0000
Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-25 14:46 -0500
Re: charging policy 123456789 <12345@12345.com> - 2018-11-25 19:37 -0700
Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-25 22:07 -0500
Re: charging policy "J. P. Gilliver (John)" <G6JPG-255@255soft.uk> - 2018-11-26 04:46 +0000
Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-26 00:32 -0500
Re: charging policy 123456789 <12345@12345.com> - 2018-11-25 22:37 -0700
Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-25 14:46 -0500
Re: charging policy 123456789 <12345@12345.com> - 2018-11-25 19:37 -0700
Re: charging policy Frank Slootweg <this@ddress.is.invalid> - 2018-11-26 15:45 +0000
Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-26 10:49 -0500
Re: charging policy 123456789 <12345@12345.com> - 2018-11-26 16:04 -0700
Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-26 19:11 -0500
Re: charging policy Frank Slootweg <this@ddress.is.invalid> - 2018-11-24 20:14 +0000
Re: charging policy 123456789 <12345@12345.com> - 2018-11-24 18:52 -0700
Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-25 00:42 -0500
Re: charging policy Anssi Saari <as@sci.fi> - 2018-11-26 10:36 +0200
Re: charging policy "J. P. Gilliver (John)" <G6JPG-255@255soft.uk> - 2018-11-26 16:37 +0000
Re: charging policy nospam <nospam@nospam.invalid> - 2018-11-21 15:10 -0500
Re: charging policy 123456789 <12345@12345.com> - 2018-11-21 15:01 -0700
csiph-web