Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Emanuel Berg <embe8573@student.uu.se>
To: info-gnus-english@gnu.org
Subject: Re: Posting styles, identities... and my stupdity
Date: Fri, 03 Oct 2014 02:59:08 +0200	[thread overview]
Message-ID: <87mw9e0y03.fsf@debian.uxu> (raw)
In-Reply-To: <mailman.10278.1412260103.1147.info-gnus-english@gnu.org>

asjo@koldfront.dk (Adam Sjøgren) writes:

> Yes. I would _never_ use my work email address for
> private emails, and I would _never_ use my private
> email address for work email.

Why not? What does it matter?

I don't consider mail a uniform (tho I can instantly
spot if someone is custom to doing it or not) - it is a
method of communication. The contents is what matters -
just as you can speak formally just as you can write
informally (even in paleo-Greek).

>> Quoting should always be done and always exactly as
>> we do here... or else!
>
> Sure. And then you meet the real world.

So supposedly computer people who cannot use email
properly and do not quote and insist on age-long
meetings in person (which are negotiated in five, six,
or seven mails), the meeting itself boils down to what
could have been communicated in a mail in five seconds
- is that any more "real" than what we are doing right
now?

Just because it is stupid doesn't make it any more
real. On the contrary, in my opinion - people who
cannot use mail or only use it as overhead to setup
pointless age-long meetings - that is *less* real,
because that upholds the illusion (to some people) that
something productive is going on.

I've seen this a hundred times: especially to people in
positions of authority or supposedly computer people it
is embarrassing beyond belief.

No, with computers, I'm proud of my elitism, and I
expect the same from all craftsmen, be it computers or
carpentry or even poetry (even though I can't identify
with that).

-- 
underground experts united
_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english

  parent reply	other threads:[~2014-10-03  0:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.10045.1412071233.1147.info-gnus-english@gnu.org>
2014-09-30 21:23 ` Emanuel Berg
2014-09-30 23:40   ` Rasmus
     [not found]   ` <mailman.10123.1412120483.1147.info-gnus-english@gnu.org>
2014-09-30 23:51     ` Emanuel Berg
2014-10-01  5:47       ` Adam Sjøgren
     [not found]       ` <mailman.10135.1412142496.1147.info-gnus-english@gnu.org>
2014-10-02  0:17         ` Emanuel Berg
2014-10-02 14:27           ` Adam Sjøgren
     [not found]           ` <mailman.10278.1412260103.1147.info-gnus-english@gnu.org>
2014-10-03  0:59             ` Emanuel Berg [this message]
2014-10-12 16:57               ` Adam Sjøgren
     [not found]               ` <mailman.11046.1413133054.1147.info-gnus-english@gnu.org>
2014-10-12 18:36                 ` Emanuel Berg
2014-10-12 19:05                   ` Adam Sjøgren
2014-10-01  6:53   ` Igor Sosa Mayor
2014-10-01 20:48     ` Peter Münster
2014-10-03 12:21       ` Igor Sosa Mayor
     [not found]   ` <mailman.10136.1412146351.1147.info-gnus-english@gnu.org>
2014-10-02  0:06     ` Emanuel Berg
2014-09-30  9:51 Igor Sosa Mayor
2014-10-03 15:06 ` Igor Sosa Mayor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87mw9e0y03.fsf@debian.uxu \
    --to=embe8573@student.uu.se \
    --cc=info-gnus-english@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).