Re: nginx TLS 1.3 doesn't seem to work
So you know how to quote, but choose to never give even the tiniest bit of context when you reply because you think we all keep an entire archive of arch-general locally and never delete anything, just so we can follow your blank replies to threads?
When something is a straight forward reply to the previous email, there is no need to quote, because you are replying directly to the email. And yes, I expect you store the email for longer than 2 seconds after reading it, this is not 1980s, you have a few kb of storage spare!
I've been on this list for years, and while I don't participate much, I do read everything. But I don't keep it all, as I expect most people don't.
I never said keep it all, I said keep the recent conversations so you know what is going on.
Your attitude sucks.
Subjective! Now can we please go back on topic, I would rather my nginx instance supports tlsv1.3, than arguing about when and when not to quote, and also how long we should store emails for! Thank you! -- Polarian GPG signature: 0770E5312238C760 Website: https://polarian.dev JID/XMPP: polarian@polarian.dev
On 2023-03-29 12:16 AM, Polarian wrote:
Your attitude sucks.
Subjective!
Now can we please go back on topic, I would rather my nginx instance supports tlsv1.3, than arguing about when and when not to quote, and also how long we should store emails for!
Thank you!
For those following at home, I used the wrong alias to reply from, so my message was rejected by the list (as expected). But I have been accurately quoted and stand by what I said to Polarian. --- Simon Perry
participants (2)
-
Polarian
-
Simon Perry