From: Thien-Thi Nguyen <ttn@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: pirate bay, w3m, and the interface is just an interface (BEST post ever)
Date: Mon, 15 Dec 2014 09:30:08 +0100 [thread overview]
Message-ID: <87oar55n8v.fsf@zigzag.favinet> (raw)
In-Reply-To: <m21to2dzjn.fsf@tilk.co> (Paul Rankin's message of "Mon, 15 Dec 2014 01:25:00 +1000")
[-- Attachment #1: Type: text/plain, Size: 1205 bytes --]
() Paul Rankin <paul@tilk.co>
() Mon, 15 Dec 2014 01:25:00 +1000
Thank you, good to know someone sees the difference between
someone's work and the digital representation of it!
The digital representation of work is the key and click stream.
That is a third concept in this discussion (that you raise to
add to the confusion, i suppose). In outline form:
1. production
a. context (community, vibe, etc)
b. Emacs hacker
c. keystrokes / mouse clicks
2. product
a. Emacs
b. "private"[0] / mailing list messages
c. "intangible" :-D perturbations in the context
That 2.[abc] feeds into 1 is vexing to the proprietary mindset,
so we see the rise of professional (paid) confounders, and must
endure their wiles, both opportunistic and premeditated. It's a
good opportunity to hone one's patience and astuteness, and help
others to do likewise.
__________________________________________
[0] See rms email boilerplate.
--
Thien-Thi Nguyen
GPG key: 4C807502
(if you're human and you know it)
read my lisp: (responsep (questions 'technical)
(not (via 'mailing-list)))
=> nil
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2014-12-15 8:30 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-14 0:46 pirate bay, w3m, and the interface is just an interface (BEST post ever) Emanuel Berg
2014-12-14 1:57 ` Paul Rankin
2014-12-14 5:14 ` Stefan Monnier
2014-12-14 5:45 ` Paul Rankin
2014-12-14 8:22 ` Marko Vojinovic
2014-12-14 9:40 ` Paul Rankin
2014-12-14 14:46 ` Óscar Fuentes
2014-12-14 15:08 ` Paul Rankin
2014-12-14 18:31 ` Óscar Fuentes
2014-12-14 18:39 ` Marcin Borkowski
2014-12-14 19:00 ` Óscar Fuentes
2014-12-14 14:59 ` Marcin Borkowski
2014-12-14 22:18 ` Stefan Monnier
[not found] ` <mailman.16023.1418550049.1147.help-gnu-emacs@gnu.org>
2014-12-23 5:50 ` Emanuel Berg
[not found] ` <mailman.16020.1418545381.1147.help-gnu-emacs@gnu.org>
2014-12-14 9:02 ` Rusi
2014-12-14 9:43 ` Paul Rankin
2014-12-23 5:39 ` Emanuel Berg
2014-12-14 13:19 ` Stefan Monnier
2014-12-14 14:03 ` Paul Rankin
2014-12-14 15:20 ` Thien-Thi Nguyen
2014-12-14 15:25 ` Paul Rankin
2014-12-15 8:30 ` Thien-Thi Nguyen [this message]
[not found] ` <mailman.16063.1418578427.1147.help-gnu-emacs@gnu.org>
2014-12-14 17:54 ` Rusi
2014-12-14 15:22 ` Paul Rankin
2014-12-14 14:01 ` Marcin Borkowski
2014-12-14 14:39 ` Paul Rankin
2014-12-14 16:08 ` Rasmus
2014-12-14 22:08 ` Stefan Monnier
[not found] ` <mailman.16048.1418567978.1147.help-gnu-emacs@gnu.org>
2014-12-17 21:28 ` Ted Zlatanov
[not found] ` <mailman.16043.1418565713.1147.help-gnu-emacs@gnu.org>
2014-12-23 5:59 ` Emanuel Berg
[not found] ` <mailman.16017.1418535962.1147.help-gnu-emacs@gnu.org>
2014-12-23 5:36 ` Emanuel Berg
[not found] ` <mailman.16010.1418522266.1147.help-gnu-emacs@gnu.org>
2014-12-22 22:08 ` Emanuel Berg
2015-03-24 13:52 ` Glen Stark
2015-03-25 0:54 ` Emanuel Berg
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87oar55n8v.fsf@zigzag.favinet \
--to=ttn@gnu.org \
--cc=help-gnu-emacs@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 read-only IMAP folder(s) and NNTP newsgroup(s).