A place to cache linked articles (think custom and personal wayback machine)
Vous ne pouvez pas sélectionner plus de 25 sujets Les noms de sujets doivent commencer par une lettre ou un nombre, peuvent contenir des tirets ('-') et peuvent comporter jusqu'à 35 caractères.

index.html 36KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722723724725726727728729730731732733734735736737738739740741742743744745746747748749750751752753754755756757758759760761762763764765766767768769770771772773774775776777778779780781782783784785786787788789790791792793794795796797798799800801802803804805806807808809810811812813814815816817818819820821822823824825826827828829830831832833834835836837838839840841842843844845846847848849850851852853854855856857858859860861862863864865866867868869870871872873874875876877878879880881882883884885886887888889890891892893894895896897898899900901902903904905906907908909910911912913914915916917918919920921922923924925926927928929930931932933934935936937938939940941942943944945946947948949950951952953954955956957958959960961962963
  1. <!doctype html><!-- This is a valid HTML5 document. -->
  2. <!-- Screen readers, SEO, extensions and so on. -->
  3. <html lang=fr>
  4. <!-- Has to be within the first 1024 bytes, hence before the <title>
  5. See: https://www.w3.org/TR/2012/CR-html5-20121217/document-metadata.html#charset -->
  6. <meta charset=utf-8>
  7. <!-- Why no `X-UA-Compatible` meta: https://stackoverflow.com/a/6771584 -->
  8. <!-- The viewport meta is quite crowded and we are responsible for that.
  9. See: https://codepen.io/tigt/post/meta-viewport-for-2015 -->
  10. <meta name=viewport content="width=device-width,minimum-scale=1,initial-scale=1,shrink-to-fit=no">
  11. <!-- Required to make a valid HTML5 document. -->
  12. <title>the fragility of effort (archive) — David Larlet</title>
  13. <!-- Generated from https://realfavicongenerator.net/ such a mess. -->
  14. <link rel="apple-touch-icon" sizes="180x180" href="/static/david/icons/apple-touch-icon.png">
  15. <link rel="icon" type="image/png" sizes="32x32" href="/static/david/icons/favicon-32x32.png">
  16. <link rel="icon" type="image/png" sizes="16x16" href="/static/david/icons/favicon-16x16.png">
  17. <link rel="manifest" href="/manifest.json">
  18. <link rel="mask-icon" href="/static/david/icons/safari-pinned-tab.svg" color="#5bbad5">
  19. <link rel="shortcut icon" href="/static/david/icons/favicon.ico">
  20. <meta name="apple-mobile-web-app-title" content="David Larlet">
  21. <meta name="application-name" content="David Larlet">
  22. <meta name="msapplication-TileColor" content="#da532c">
  23. <meta name="msapplication-config" content="/static/david/icons/browserconfig.xml">
  24. <meta name="theme-color" content="#f0f0ea">
  25. <!-- That good ol' feed, subscribe :p. -->
  26. <link rel=alternate type="application/atom+xml" title=Feed href="/david/log/">
  27. <meta name="robots" content="noindex, nofollow">
  28. <meta content="origin-when-cross-origin" name="referrer">
  29. <!-- Canonical URL for SEO purposes -->
  30. <link rel="canonical" href="http://www.aaronland.info/weblog/2015/02/24/effort/">
  31. <style>
  32. /* http://meyerweb.com/eric/tools/css/reset/ */
  33. html, body, div, span,
  34. h1, h2, h3, h4, h5, h6, p, blockquote, pre,
  35. a, abbr, address, big, cite, code,
  36. del, dfn, em, img, ins,
  37. small, strike, strong, tt, var,
  38. dl, dt, dd, ol, ul, li,
  39. fieldset, form, label, legend,
  40. table, caption, tbody, tfoot, thead, tr, th, td,
  41. article, aside, canvas, details, embed,
  42. figure, figcaption, footer, header, hgroup,
  43. menu, nav, output, ruby, section, summary,
  44. time, mark, audio, video {
  45. margin: 0;
  46. padding: 0;
  47. border: 0;
  48. font-size: 100%;
  49. font: inherit;
  50. vertical-align: baseline;
  51. }
  52. /* HTML5 display-role reset for older browsers */
  53. article, aside, details, figcaption, figure,
  54. footer, header, hgroup, menu, nav, section { display: block; }
  55. body { line-height: 1; }
  56. blockquote, q { quotes: none; }
  57. blockquote:before, blockquote:after,
  58. q:before, q:after {
  59. content: '';
  60. content: none;
  61. }
  62. table {
  63. border-collapse: collapse;
  64. border-spacing: 0;
  65. }
  66. /* http://practicaltypography.com/equity.html */
  67. /* https://calendar.perfplanet.com/2016/no-font-face-bulletproof-syntax/ */
  68. /* https://www.filamentgroup.com/lab/js-web-fonts.html */
  69. @font-face {
  70. font-family: 'EquityTextB';
  71. src: url('/static/david/css/fonts/Equity-Text-B-Regular-webfont.woff2') format('woff2'),
  72. url('/static/david/css/fonts/Equity-Text-B-Regular-webfont.woff') format('woff');
  73. font-weight: 300;
  74. font-style: normal;
  75. font-display: swap;
  76. }
  77. @font-face {
  78. font-family: 'EquityTextB';
  79. src: url('/static/david/css/fonts/Equity-Text-B-Italic-webfont.woff2') format('woff2'),
  80. url('/static/david/css/fonts/Equity-Text-B-Italic-webfont.woff') format('woff');
  81. font-weight: 300;
  82. font-style: italic;
  83. font-display: swap;
  84. }
  85. @font-face {
  86. font-family: 'EquityTextB';
  87. src: url('/static/david/css/fonts/Equity-Text-B-Bold-webfont.woff2') format('woff2'),
  88. url('/static/david/css/fonts/Equity-Text-B-Bold-webfont.woff') format('woff');
  89. font-weight: 700;
  90. font-style: normal;
  91. font-display: swap;
  92. }
  93. @font-face {
  94. font-family: 'ConcourseT3';
  95. src: url('/static/david/css/fonts/concourse_t3_regular-webfont-20190806.woff2') format('woff2'),
  96. url('/static/david/css/fonts/concourse_t3_regular-webfont-20190806.woff') format('woff');
  97. font-weight: 300;
  98. font-style: normal;
  99. font-display: swap;
  100. }
  101. /* http://practice.typekit.com/lesson/caring-about-opentype-features/ */
  102. body {
  103. /* http://www.cssfontstack.com/ Palatino 99% Win 86% Mac */
  104. font-family: "EquityTextB", Palatino, serif;
  105. background-color: #f0f0ea;
  106. color: #07486c;
  107. font-kerning: normal;
  108. -moz-osx-font-smoothing: grayscale;
  109. -webkit-font-smoothing: subpixel-antialiased;
  110. text-rendering: optimizeLegibility;
  111. font-variant-ligatures: common-ligatures contextual;
  112. font-feature-settings: "kern", "liga", "clig", "calt";
  113. }
  114. pre, code, kbd, samp, var, tt {
  115. font-family: 'TriplicateT4c', monospace;
  116. }
  117. em {
  118. font-style: italic;
  119. color: #323a45;
  120. }
  121. strong {
  122. font-weight: bold;
  123. color: black;
  124. }
  125. nav {
  126. background-color: #323a45;
  127. color: #f0f0ea;
  128. display: flex;
  129. justify-content: space-around;
  130. padding: 1rem .5rem;
  131. }
  132. nav:last-child {
  133. border-bottom: 1vh solid #2d7474;
  134. }
  135. nav a {
  136. color: #f0f0ea;
  137. }
  138. nav abbr {
  139. border-bottom: 1px dotted white;
  140. }
  141. h1 {
  142. border-top: 1vh solid #2d7474;
  143. border-bottom: .2vh dotted #2d7474;
  144. background-color: #e3e1e1;
  145. color: #323a45;
  146. text-align: center;
  147. padding: 5rem 0 4rem 0;
  148. width: 100%;
  149. font-family: 'ConcourseT3';
  150. display: flex;
  151. flex-direction: column;
  152. }
  153. h1.single {
  154. padding-bottom: 10rem;
  155. }
  156. h1 span {
  157. position: absolute;
  158. top: 1vh;
  159. left: 20%;
  160. line-height: 0;
  161. }
  162. h1 span a {
  163. line-height: 1.7;
  164. padding: 1rem 1.2rem .6rem 1.2rem;
  165. border-radius: 0 0 6% 6%;
  166. background: #2d7474;
  167. font-size: 1.3rem;
  168. color: white;
  169. text-decoration: none;
  170. }
  171. h2 {
  172. margin: 4rem 0 1rem;
  173. border-top: .2vh solid #2d7474;
  174. padding-top: 1vh;
  175. }
  176. h3 {
  177. text-align: center;
  178. margin: 3rem 0 .75em;
  179. }
  180. hr {
  181. height: .4rem;
  182. width: .4rem;
  183. border-radius: .4rem;
  184. background: #07486c;
  185. margin: 2.5rem auto;
  186. }
  187. time {
  188. display: bloc;
  189. margin-left: 0 !important;
  190. }
  191. ul, ol {
  192. margin: 2rem;
  193. }
  194. ul {
  195. list-style-type: square;
  196. }
  197. a {
  198. text-decoration-skip-ink: auto;
  199. text-decoration-thickness: 0.05em;
  200. text-underline-offset: 0.09em;
  201. }
  202. article {
  203. max-width: 50rem;
  204. display: flex;
  205. flex-direction: column;
  206. margin: 2rem auto;
  207. }
  208. article.single {
  209. border-top: .2vh dotted #2d7474;
  210. margin: -6rem auto 1rem auto;
  211. background: #f0f0ea;
  212. padding: 2rem;
  213. }
  214. article p:last-child {
  215. margin-bottom: 1rem;
  216. }
  217. p {
  218. padding: 0 .5rem;
  219. margin-left: 3rem;
  220. }
  221. p + p,
  222. figure + p {
  223. margin-top: 2rem;
  224. }
  225. blockquote {
  226. background-color: #e3e1e1;
  227. border-left: .5vw solid #2d7474;
  228. display: flex;
  229. flex-direction: column;
  230. align-items: center;
  231. padding: 1rem;
  232. margin: 1.5rem;
  233. }
  234. blockquote cite {
  235. font-style: italic;
  236. }
  237. blockquote p {
  238. margin-left: 0;
  239. }
  240. figure {
  241. border-top: .2vh solid #2d7474;
  242. background-color: #e3e1e1;
  243. text-align: center;
  244. padding: 1.5rem 0;
  245. margin: 1rem 0 0;
  246. font-size: 1.5rem;
  247. width: 100%;
  248. }
  249. figure img {
  250. max-width: 250px;
  251. max-height: 250px;
  252. border: .5vw solid #323a45;
  253. padding: 1px;
  254. }
  255. figcaption {
  256. padding: 1rem;
  257. line-height: 1.4;
  258. }
  259. aside {
  260. display: flex;
  261. flex-direction: column;
  262. background-color: #e3e1e1;
  263. padding: 1rem 0;
  264. border-bottom: .2vh solid #07486c;
  265. }
  266. aside p {
  267. max-width: 50rem;
  268. margin: 0 auto;
  269. }
  270. /* https://fvsch.com/code/css-locks/ */
  271. p, li, pre, code, kbd, samp, var, tt, time, details, figcaption {
  272. font-size: 1rem;
  273. line-height: calc( 1.5em + 0.2 * 1rem );
  274. }
  275. h1 {
  276. font-size: 1.9rem;
  277. line-height: calc( 1.2em + 0.2 * 1rem );
  278. }
  279. h2 {
  280. font-size: 1.6rem;
  281. line-height: calc( 1.3em + 0.2 * 1rem );
  282. }
  283. h3 {
  284. font-size: 1.35rem;
  285. line-height: calc( 1.4em + 0.2 * 1rem );
  286. }
  287. @media (min-width: 20em) {
  288. /* The (100vw - 20rem) / (50 - 20) part
  289. resolves to 0-1rem, depending on the
  290. viewport width (between 20em and 50em). */
  291. p, li, pre, code, kbd, samp, var, tt, time, details, figcaption {
  292. font-size: calc( 1rem + .6 * (100vw - 20rem) / (50 - 20) );
  293. line-height: calc( 1.5em + 0.2 * (100vw - 50rem) / (20 - 50) );
  294. margin-left: 0;
  295. }
  296. h1 {
  297. font-size: calc( 1.9rem + 1.5 * (100vw - 20rem) / (50 - 20) );
  298. line-height: calc( 1.2em + 0.2 * (100vw - 50rem) / (20 - 50) );
  299. }
  300. h2 {
  301. font-size: calc( 1.5rem + 1.5 * (100vw - 20rem) / (50 - 20) );
  302. line-height: calc( 1.3em + 0.2 * (100vw - 50rem) / (20 - 50) );
  303. }
  304. h3 {
  305. font-size: calc( 1.35rem + 1.5 * (100vw - 20rem) / (50 - 20) );
  306. line-height: calc( 1.4em + 0.2 * (100vw - 50rem) / (20 - 50) );
  307. }
  308. }
  309. @media (min-width: 50em) {
  310. /* The right part of the addition *must* be a
  311. rem value. In this example we *could* change
  312. the whole declaration to font-size:2.5rem,
  313. but if our baseline value was not expressed
  314. in rem we would have to use calc. */
  315. p, li, pre, code, kbd, samp, var, tt, time, details, figcaption {
  316. font-size: calc( 1rem + .6 * 1rem );
  317. line-height: 1.5em;
  318. }
  319. p, li, pre, details {
  320. margin-left: 3rem;
  321. }
  322. h1 {
  323. font-size: calc( 1.9rem + 1.5 * 1rem );
  324. line-height: 1.2em;
  325. }
  326. h2 {
  327. font-size: calc( 1.5rem + 1.5 * 1rem );
  328. line-height: 1.3em;
  329. }
  330. h3 {
  331. font-size: calc( 1.35rem + 1.5 * 1rem );
  332. line-height: 1.4em;
  333. }
  334. figure img {
  335. max-width: 500px;
  336. max-height: 500px;
  337. }
  338. }
  339. figure.unsquared {
  340. margin-bottom: 1.5rem;
  341. }
  342. figure.unsquared img {
  343. height: inherit;
  344. }
  345. @media print {
  346. body { font-size: 100%; }
  347. a:after { content: " (" attr(href) ")"; }
  348. a, a:link, a:visited, a:after {
  349. text-decoration: underline;
  350. text-shadow: none !important;
  351. background-image: none !important;
  352. background: white;
  353. color: black;
  354. }
  355. abbr[title] { border-bottom: 0; }
  356. abbr[title]:after { content: " (" attr(title) ")"; }
  357. img { page-break-inside: avoid; }
  358. @page { margin: 2cm .5cm; }
  359. h1, h2, h3 { page-break-after: avoid; }
  360. p3 { orphans: 3; widows: 3; }
  361. img {
  362. max-width: 250px !important;
  363. max-height: 250px !important;
  364. }
  365. nav, aside { display: none; }
  366. }
  367. ul.with_columns {
  368. column-count: 1;
  369. }
  370. @media (min-width: 20em) {
  371. ul.with_columns {
  372. column-count: 2;
  373. }
  374. }
  375. @media (min-width: 50em) {
  376. ul.with_columns {
  377. column-count: 3;
  378. }
  379. }
  380. ul.with_two_columns {
  381. column-count: 1;
  382. }
  383. @media (min-width: 20em) {
  384. ul.with_two_columns {
  385. column-count: 1;
  386. }
  387. }
  388. @media (min-width: 50em) {
  389. ul.with_two_columns {
  390. column-count: 2;
  391. }
  392. }
  393. .gallery {
  394. display: flex;
  395. flex-wrap: wrap;
  396. justify-content: space-around;
  397. }
  398. .gallery figure img {
  399. margin-left: 1rem;
  400. margin-right: 1rem;
  401. }
  402. .gallery figure figcaption {
  403. font-family: 'ConcourseT3'
  404. }
  405. footer {
  406. font-family: 'ConcourseT3';
  407. display: flex;
  408. flex-direction: column;
  409. border-top: 3px solid white;
  410. padding: 4rem 0;
  411. background-color: #07486c;
  412. color: white;
  413. }
  414. footer > * {
  415. max-width: 50rem;
  416. margin: 0 auto;
  417. }
  418. footer a {
  419. color: #f1c40f;
  420. }
  421. footer .avatar {
  422. width: 200px;
  423. height: 200px;
  424. border-radius: 50%;
  425. float: left;
  426. -webkit-shape-outside: circle();
  427. shape-outside: circle();
  428. margin-right: 2rem;
  429. padding: 2px 5px 5px 2px;
  430. background: white;
  431. border-left: 1px solid #f1c40f;
  432. border-top: 1px solid #f1c40f;
  433. border-right: 5px solid #f1c40f;
  434. border-bottom: 5px solid #f1c40f;
  435. }
  436. </style>
  437. <h1>
  438. <span><a id="jumper" href="#jumpto" title="Un peu perdu ?">?</a></span>
  439. the fragility of effort (archive)
  440. <time>Pour la pérennité des contenus liés. Non-indexé, retrait sur simple email.</time>
  441. </h1>
  442. <section>
  443. <article>
  444. <h3><a href="http://www.aaronland.info/weblog/2015/02/24/effort/">Source originale du contenu</a></h3>
  445. <h1 class="cooperhewitt dataporn email law moma motive museum">the holodeck of motive</h1>
  446. <div class="slide" id="moma-big-data-001">
  447. <div class="image640">
  448. <img src="http://www.aaronland.info/weblog/2015/02/24/effort/images/moma-big-data.001.jpg"/>
  449. </div>
  450. <div>
  451. <p>Last night I had the privilege of being asked to
  452. participate in the thirteenth <a href="http://momarnd.moma.org/">MoMA R&amp;D
  453. Salon</a> on <q>big(ger) data</q> alongside <a href="http://www.hilarymason.com">Hillary Mason</a>, <a href="http://blog.hannahdonovan.com">Hannah
  454. Donovan</a> and <a href="https://twitter.com/cocteau">Mark Hansen</a>. The bulk of the evening was a panel discussion
  455. with <a href="http://www.moma.org/explore/inside_out/author/pantonelli">Paola
  456. Antonelli</a>. Each participant was asked to do a
  457. short presentation, where short was defined as
  458. <q>about seven minutes</q>.</p>
  459. <p>What follows is clearly more than seven minutes
  460. so the talk itself got a little wobbly towards the
  461. middle and the end. There is also <a href="http://momarnd.moma.org/salons/salon-13-bigger-data/">video of the event</a> so you can compare the text below that I meant and what I actually did say. This is what I tried to say.</p>
  462. </div>
  463. <p>I'd like to start with three quotes. The first is
  464. by Brian Barrett, <a href="http://gizmodo.com/the-sony-hacks-are-goddamn-terrifying-1668911102">writing about the Sony hack</a> for Gizmodo:</p>
  465. <blockquote>
  466. <p><q>The most painful stuff in the Sony cache is a
  467. doctor shopping for Ritalin. It's an email about
  468. trying to get pregnant. It's shit-talking coworkers
  469. behind their backs ... It's even the harmless,
  470. mundane, trivial stuff that makes up any day's email
  471. load that suddenly feels ugly and raw out in the
  472. open ... You may assume you'd
  473. be fine in the same scenario, that you have nothing
  474. to hide, that you wouldn't mind. But just take a
  475. look through your Sent folder's last month. Last
  476. week. Yesterday. There's something in there you
  477. wouldn't want the world to see. There's some
  478. conversation that would be misread without context,
  479. or read correctly for its cloddishness. Our inboxes
  480. are increasingly our id, a water cooler with
  481. infinitely expandable memory.</q></p>
  482. </blockquote>
  483. <p>The second is by the sociologist <a href="http://www.karen-levy.net">Karen Levy</a>
  484. speaking at a panel about <a href="https://soundcloud.com/eyebeamnyc/new-topics-in-social-computing-consent-and-the-network">Consent and the Network</a>,
  485. at Eyebeam last month. Paraphrasing, she said:</p>
  486. <blockquote>
  487. <p><q>...we act as though if we are able to develop
  488. a technical means around a user's consent then we
  489. have a right to do whatever we want.</q></p>
  490. </blockquote>
  491. <p>The third and final quote is by <a href="http://www.keirdotnet.net">Keir Winesmith</a>
  492. describing how they think about the social and privacy
  493. implications of <a href="http://www.sfmoma.org/about/research_projects/lab">the work they are do at SFMoMA</a>.</p>
  494. </div>
  495. <div class="slide" id="moma-big-data-002">
  496. <div class="image640">
  497. <img src="http://www.aaronland.info/weblog/2015/02/24/effort/images/moma-big-data.002.jpg"/>
  498. </div>
  499. <p>He said:</p>
  500. <blockquote>
  501. <p><q>We walk right up to the line of creepy. And then we take two steps back.</q></p>
  502. </blockquote>
  503. <p>When Flickr launched geotagging – the ability to
  504. associate your photos with a physical location – we
  505. did not try to establish so-called <q>sensible
  506. defaults</q>. Instead we forced users to choose defaults
  507. before they could use the feature.</p>
  508. <p>First, they had to choose a default privacy setting
  509. for all their geotagged photos. Second, they needed to
  510. expressly indicate that they wanted us to import
  511. any geographic metadata that their phone or camera
  512. might have embedded in their photos.</p>
  513. <p>This was back in August of 2006, six months before
  514. the iPhone was announced and just under a year before
  515. the phone was actually released and the whole notion
  516. of camera phones automatically embedding GPS
  517. information in a photo's metadata had not really been
  518. normalized yet.</p>
  519. <p>One of the consequences of our decision is that as
  520. other photo-sharing services became more popular (most
  521. notably Instagram) many never bothered to ask users
  522. whether they wanted or expected that metadata to be
  523. exposed. As if by magic their photos were suddenly
  524. geotagged and a lot of people started thinking that our
  525. geotagging support was broken.</p>
  526. <p>Keep in mind that it wasn't even until 2008 that,
  527. then NSA director, Keith Alexander asked his staff:
  528. <q>Actually, why don't we just keep all the signals?</q> so
  529. everyone was still pretty excited by the opportunity
  530. that all of this data presented. People have always
  531. written dates and places on the backs of their
  532. photographs so having your technology take care of
  533. those details as-if by magic is pretty cool.</p>
  534. <p>It's not like we weren't excited about geotagging.
  535. It's just that we were trying to be mindful of the implications of what
  536. users were getting in to. But being mindful and
  537. successfully conveying that mindfulness to people are
  538. not the same thing and, like I said, it was 2008 and
  539. everyone was feeling pretty good about things. We
  540. still believed that the sum of the Internet was
  541. so big, too big, to prevent anyone from stitching it
  542. all back together.</p>
  543. <p>Did you know that if you assign a Creative Commons
  544. license to one of your Flickr photos that setting trumps your
  545. ability to prevent other people from downloading the
  546. original photo? Even if you've said you don't want to
  547. let other people download your original photos and
  548. you've said you don't want to make your geotagged
  549. photos public (because unless you explicitly opt-out
  550. <em>all</em> photos are geotagged now) the license setting
  551. takes precedence.</p>
  552. <p>I mention that because even I didn't realize that's
  553. what we were doing and I worked there for five
  554. years. Or rather I had always assumed that we would
  555. err on the side of caution when asked to choose
  556. an order of precedence for something like that.</p>
  557. <p>I tell you this because if there was ever a
  558. cardinal rule at Flickr it was: Don't fuck with
  559. people's original photos. This included the
  560. metadata. We wouldn't have purged the EXIF data from
  561. your pictures even if you had asked us to.</p>
  562. <p>In a world where you might be able to imagine
  563. something with the breadth and reach of a <a href="https://pinboard.in/search/u:straup?query=national+security+letter">National
  564. Security Letter</a>, but perhaps the not apparent
  565. liberalness of its application, this is a "feature"
  566. right?</p>
  567. <p>In a world where you might imagine a junior lawyer
  568. drafting an argument claiming that algorithmic facial
  569. detection, by virtue of its automated nature, should
  570. be classified as <q><a href="https://www.schneier.com/blog/archives/2013/09/metadata_equals.html">just metadata</a></q> along with all the
  571. date/time and geographic information present in
  572. digital photographs... well, yeah.</p>
  573. <p>In a world where the phrase <a href="https://en.wikipedia.org/wiki/Open-source_intelligence#Definers_for_OSINT">open-source
  574. information</a> even exists...</p>
  575. </div>
  576. <div class="slide" id="moma-big-data-003">
  577. <div class="image640">
  578. <img src="http://www.aaronland.info/weblog/2015/02/24/effort/images/moma-big-data.003.jpg"/>
  579. </div>
  580. <p>One of the burdens of the present is that we are all, forever, being forced to
  581. pay the cost of someone else's near-future opportunity. The core of the
  582. opportunity myth, in the United States anyway, is a celebration of someone seeing
  583. value in something that no one else has recognized or
  584. understood yet and in <a href="http://www.aaronland.info/weblog/2014/09/11/brand/#dconstruct">reaping the reward of extracting
  585. that worth</a>.</p>
  586. <p>In legal circles there is something known as the "exclusionary rule" which
  587. doesn't seek to prevent the collection of data by making it a physical
  588. impossibility but achieves the same result by nullifying its admissibility in
  589. court. It is a very real example of a community simply deciding that <code>2 + 2 =
  590. 5</code>. We say that the manner in which cause and effect are established is,
  591. frankly, more important than the fact being proved. Most people know the
  592. exclusionary rule by its umbrella principle the Fourth Amendment – or the right to privacy – of the US
  593. Constitution.</p>
  594. <p>Right now <a href="http://www.aaronland.info/www.scotusblog.com/2014/06/symposium-in-riley-v-california-a-unanimous-supreme-court-sets-out-fourth-amendment-for-digital-age/">the manner in which the exclusionary rule is applied to big-data a
  595. mess</a>. One court has ruled that the police can not physically install a GPS unit
  596. on your car and track your movements while another has ruled that the police can
  597. still demand that the phone companies hand over all the location data tied to
  598. your cell phone.</p>
  599. <p>I don't think anyone is entirely certain how the exclusionary rule squares with
  600. something like a National Security Letter but Australia, at least, has made
  601. short work of that debate by simply legislating that anything collected under
  602. the auspices of their own surveillance laws is admissible in court.</p>
  603. <p>There is a whole other discussion to be had about the approach Europe is taking with
  604. their "right to privacy" laws and I want to mention
  605. them only in passing because they are the closest
  606. thing we may have gotten to something approaching an
  607. exclusionary rule for the data that private companies
  608. collect or the uses they put it to.</p>
  609. <p>In the meantime absent our ability to craft narratives and social norms in step
  610. with the instrumentation of our lives the resultant
  611. "big-data" will remain a bountiful frontier of
  612. opportunity for anyone willing to see the implications
  613. of their actions as tomorrow's problem.</p>
  614. </div>
  615. <div class="slide" id="moma-big-data-004">
  616. <div class="image640">
  617. <img src="http://www.aaronland.info/weblog/2015/02/24/effort/images/moma-big-data.004.jpg"/>
  618. </div>
  619. <p>One of the things that we've been thinking about, at the Cooper Hewitt, is how
  620. we collect contemporary design objects. What does a design museum do when the
  621. meat of their practice has either become entirely digital – that is lacking any
  622. singular manifest physicality – or whose full meaning and understanding, whose
  623. implications, are opaque absent access to the underlying source code or the data
  624. it produces.</p>
  625. <p>To some degree thus has it ever been. We may never know, truly, the motivations
  626. of an artists or a designer but there's usually a pretty thing to can
  627. look at, fifty years later. This might be the actual thing that was produced or
  628. it might be the relentless documentation that seems to define people hell-bent
  629. on a practice that claims to leave no trace behind.</p>
  630. <p>Take the Nest thermostat, for example. <a href="https://collection.cooperhewitt.org/search/collection/?query=Nest+thermostat">We acquired a pair in 2013</a> but that's
  631. really all we did. We took them out of their boxes and put them on a shelf. We
  632. also acquired some of <a href="https://collection.cooperhewitt.org/search/collection/?query=Nest+thermostat+sketch">the early sketches and preparatory drawing for the devices</a>
  633. which are arguably more interesting, in the long-term, than the things
  634. themselves. It would have been unfair and unrealistic for the Smithsonian to ask
  635. Nest, or any on-going commercial interest, for the source code to their
  636. device. In the case of Nest we would have been asking them to forfeit the 3.2
  637. billion dollars they earned selling their company to Google.</p>
  638. <p>Absent the source code with which we might investigate how the Nest
  639. distinguishes itself from other thermostats or the decision to acquire the data
  640. that those units collected (I'm not sure they've ever been plugged in...) in
  641. order to demonstrate its use we are left with a lump of metal and plastic that
  642. <a href="https://collection.cooperhewitt.org/exhibitions/51669015/section/69070603">we quite literally hang on a wall next its widely acknowledge inspiration</a>: Henry
  643. Dreyfuss' classic <q>T68 Round</q> thermostat.</p>
  644. <p>Note: We're actually
  645. exhibiting Dreyfuss' <q>CT87K</q> thermostat, and not
  646. the <q>T68</q> but you
  647. get the idea.</p>
  648. <p>With that in mind we have been asking ourselves:
  649. What would it mean for museums and libraries establish
  650. a kind of escrow for intellectual property for
  651. products or the data they emit? Assuming we could
  652. define a shared social contract around the practice
  653. what would it mean for both individuals and
  654. corporations to participate in the collection and
  655. nurturing of this data not with a focus on the present
  656. but with an eye to the future?</p>
  657. <p>It is important to understand that the cultural
  658. heritage sector is <span>in no way</span>
  659. ready to take on the burden of maintaining an infrastructure like this. Some of
  660. us, by virtue of the value of our collections, can imagine the kinds of targets
  661. of opportunity we would become shepherding this kind
  662. of stuff but the sheer volume and physicality of many
  663. collections is a defense that "big data" doesn't enjoy.</p>
  664. <p>What we do have though is a disposition for the long game, for keeping things
  665. safe and at least in recent times doing these things <a href="http://www.vam.ac.uk/content/exhibitions/all-of-this-belongs-to-you/all-of-this-belongs-to-you/">in the service of the
  666. community, at large</a>.</p>
  667. </div>
  668. <div class="slide" id="moma-big-data-005">
  669. <div class="image640">
  670. <img src="http://www.aaronland.info/weblog/2015/02/24/effort/images/moma-big-data.005.jpg"/>
  671. </div>
  672. <p>I mention this because there is a fairly new and often uncomfortable reality for
  673. those of us in the cultural heritage business. That we are starting to share
  674. more in common with agencies like the NSA than anyone quite knows how to
  675. conceptualize.</p>
  676. </div>
  677. <div class="slide" id="moma-big-data-006">
  678. <div class="image640">
  679. <img src="http://www.aaronland.info/weblog/2015/02/24/effort/images/moma-big-data.006.jpg"/>
  680. </div>
  681. <p>Every time someone talks to you about <a href="http://www.aaronland.info/weblog/2008/10/08/tree/#pattern">personal
  682. informatics</a>, or <a href="https://collection.cooperhewitt.org/objects/35457211/">census data
  683. from a distant past</a>, understand that the NSA is trying to solve the same
  684. basic set of problems and replace the number of miles you ran or the colour of
  685. your baby's poo with the question of Original Sin. In seeing the meaning of past
  686. actions as a way to make sense of present intent. Of judgement.</p>
  687. <p>Which is not unlike what the humanities does. It used to be that I would have
  688. conversations with people where they would sketch out all sorts of
  689. pie-in-the-sky database systems and inference engines that could be plumbed in
  690. order to answer all their scholarly questions. What I've now come to realize is
  691. that many of them were simply describing <a href="https://archive.org/search.php?query=subject%3A%22Edward%20Snowden%22">the systems that Edward Snowden says
  692. the NSA has been building for itself</a> all along.</p>
  693. <p>Those tools evoke many reactions but if we are honest we will be forced to admit
  694. that envy is one of them.</p>
  695. </div>
  696. <div class="slide" id="moma-big-data-007">
  697. <div class="image640">
  698. <img src="http://www.aaronland.info/weblog/2015/02/24/effort/images/moma-big-data.007.jpg"/>
  699. </div>
  700. <p>Note: I didn't really
  701. get to this part during the talk itself. I pointed to
  702. it but it was all a bit rushed and disjointed by this
  703. point. The slide for this
  704. section is titled <q>post conspicuously</q> which is
  705. a reference to the instructions from the New York City
  706. Department of Health for restaurant owners to place
  707. their permit to operate in a place where anyone can see it, without having to ask. There's something about that idea which relates
  708. to everything below but you would be forgiven for not
  709. really seeing where those two things are holding hands
  710. because it's all still a fuzzy for me too...</p>
  711. <p>One day all of that data the NSA is reported to be storing will be the raw
  712. material for an AP high school digital humanities homework assignment.</p>
  713. <p>One day that data will be where most of us long since forgotten after our deaths
  714. might live on even the brief moments that someone sees
  715. our past as something more than an abstraction.</p>
  716. <p>One day that data may be used to demonstrate that
  717. it was, in fact, a fifth
  718. column that finally ushered in a
  719. global <a href="http://www.cbc.ca/player/Radio/The+Sunday+Edition/ID/2618301311/">confessional uniformity</a> — a
  720. pursuit that seems to be present in every age for as long as we've been
  721. telling these stories.</p>
  722. <p>One day that data will be subpoenaed and used to
  723. tell the stories that we may not want to remember but that
  724. we need to. If you've not read the US Senate Intelligence
  725. Committee's <a href="http://www.intelligence.senate.gov/study2014.html">Study of the Central Intelligence Agency's Detention
  726. and Interrogation Program</a> you should. Someone has
  727. to. It's
  728. profoundly depressing but it is important
  729. reading. Beyond the actions described in the report
  730. the thing that struck me is that most of the proof
  731. seems to have been found in the email that the various
  732. actors sent themselves.</p>
  733. <p>Email. <em>They talked about this stuff in email.</em></p>
  734. <blockquote>
  735. <p><q>It's even the harmless,
  736. mundane, trivial stuff that makes up any day's email
  737. load that suddenly feels ugly and raw out in the
  738. open.</q></p>
  739. </blockquote>
  740. <p>Lots of private companies are establishing
  741. corporate policies whereby email archives are purged
  742. on a regular interval. Lots of security professionals
  743. are recommending the practice to individuals precisely
  744. because the cost to an opportunist to hoarde that data
  745. and discover some clever use for it in the future is
  746. negligable.</p>
  747. <p>Or <a href="http://www.washingtonpost.com/news/post-nation/wp/2014/11/26/national-archives-backing-away-from-cia-e-mail-destruction-plan/">this</a>:</p>
  748. <blockquote>
  749. <p>The CIA sought permission in January to
  750. destroy e-mail communications of all but 22 top CIA
  751. officials within three years of their leaving the
  752. agency — <q>or when no longer needed, whichever is
  753. sooner.</q></p>
  754. </blockquote>
  755. <p><q>No longer needed.</q> I know, right?</p>
  756. <p>In the end the National Archives announced that, at
  757. least for now, <a href="http://fas.org/blogs/secrecy/2014/11/nara-cia-email/">they
  758. won't indulge the CIA's request</a>. This isn't
  759. necessarily about the CIA either. It seems that we give them a
  760. long-enough leash that by their actions they routine provoke these
  761. questions, but ask yourselves:
  762. Do you really want <a href="http://gothamist.com/2015/02/25/email_enema_healthy_ny.php">any government agency</a> to have the
  763. luxury of choosing the shadow it casts in to the
  764. future and the stories it tells at dinner parties?</p>
  765. <p>The practice is hardly new, historically,
  766. but I'm not sure its one that's worked out very well
  767. for most people, most of the time.</p>
  768. <p>I do not mean to suggest that we supplicate ourselves to the imagined benefits
  769. of the hypothetical futures I am describing. The question remains: How do we
  770. protect the present from itself? The question remains:
  771. How long needs to pass before the sting of all that
  772. data in the moment is worth its yield in the
  773. future?</p>
  774. <p>We have never stopped looking back and trying to
  775. figure out <em>what the fuck</em> the past was
  776. thinking and I don't imagine we will stop anytime
  777. soon. I think that is important to remember because
  778. one of the opportunities that <q>big-data</q> suggests
  779. is a better window on the past and, now that we've
  780. seen it, it's difficult to imagine anyone choosing the
  781. forfeit that possibility.</p>
  782. <p>What upsets me about the "big-data" discussion is the way that
  783. it is so often couched in a rhetoric of inevitability. It is the rhetoric of the
  784. <a href="https://web.archive.org/web/20140814040031/http://www.gutenberg.org/files/37364/37364-h/37364-h.htm#page_29">Law of the Jungle</a> and some of us, at least, have been
  785. struggling to find viable alternatives for as
  786. long as we've recognized it as such.</p>
  787. <p>The rhetoric of
  788. big-data is too often about absolute certainties and
  789. not about choices, or reasons. On bad days it is an abdication of our shared
  790. responsibility to articulate <em>why</em> we choose to
  791. live the ways that we do.</p>
  792. </div>
  793. <div class="slide" id="moma-big-data-008">
  794. <div class="image640">
  795. <img src="http://www.aaronland.info/weblog/2015/02/24/effort/images/moma-big-data.008.jpg"/>
  796. </div>
  797. </div>
  798. </article>
  799. </section>
  800. <nav id="jumpto">
  801. <p>
  802. <a href="/david/blog/">Accueil du blog</a> |
  803. <a href="http://www.aaronland.info/weblog/2015/02/24/effort/">Source originale</a> |
  804. <a href="/david/stream/2019/">Accueil du flux</a>
  805. </p>
  806. </nav>
  807. <footer>
  808. <div>
  809. <img src="/static/david/david-larlet-avatar.jpg" loading="lazy" class="avatar" width="200" height="200">
  810. <p>
  811. Bonjour/Hi!
  812. Je suis <a href="/david/" title="Profil public">David&nbsp;Larlet</a>, je vis actuellement à Montréal et j’alimente cet espace depuis 15 ans. <br>
  813. Si tu as apprécié cette lecture, n’hésite pas à poursuivre ton exploration. Par exemple via les <a href="/david/blog/" title="Expériences bienveillantes">réflexions bimestrielles</a>, la <a href="/david/stream/2019/" title="Pensées (dés)articulées">veille hebdomadaire</a> ou en t’abonnant au <a href="/david/log/" title="S’abonner aux publications via RSS">flux RSS</a> (<a href="/david/blog/2019/flux-rss/" title="Tiens c’est quoi un flux RSS ?">so 2005</a>).
  814. </p>
  815. <p>
  816. Je m’intéresse à la place que je peux avoir dans ce monde. En tant qu’humain, en tant que membre d’une famille et en tant qu’associé d’une coopérative. De temps en temps, je fais aussi des <a href="https://github.com/davidbgk" title="Principalement sur Github mais aussi ailleurs">trucs techniques</a>. Et encore plus rarement, <a href="/david/talks/" title="En ce moment je laisse plutôt la place aux autres">j’en parle</a>.
  817. </p>
  818. <p>
  819. Voici quelques articles choisis :
  820. <a href="/david/blog/2019/faire-equipe/" title="Accéder à l’article complet">Faire équipe</a>,
  821. <a href="/david/blog/2018/bivouac-automnal/" title="Accéder à l’article complet">Bivouac automnal</a>,
  822. <a href="/david/blog/2018/commodite-effondrement/" title="Accéder à l’article complet">Commodité et effondrement</a>,
  823. <a href="/david/blog/2017/donnees-communs/" title="Accéder à l’article complet">Des données aux communs</a>,
  824. <a href="/david/blog/2016/accompagner-enfant/" title="Accéder à l’article complet">Accompagner un enfant</a>,
  825. <a href="/david/blog/2016/senior-developer/" title="Accéder à l’article complet">Senior developer</a>,
  826. <a href="/david/blog/2016/illusion-sociale/" title="Accéder à l’article complet">L’illusion sociale</a>,
  827. <a href="/david/blog/2016/instantane-scopyleft/" title="Accéder à l’article complet">Instantané Scopyleft</a>,
  828. <a href="/david/blog/2016/enseigner-web/" title="Accéder à l’article complet">Enseigner le Web</a>,
  829. <a href="/david/blog/2016/simplicite-defaut/" title="Accéder à l’article complet">Simplicité par défaut</a>,
  830. <a href="/david/blog/2016/minimalisme-esthetique/" title="Accéder à l’article complet">Minimalisme et esthétique</a>,
  831. <a href="/david/blog/2014/un-web-omni-present/" title="Accéder à l’article complet">Un web omni-présent</a>,
  832. <a href="/david/blog/2014/manifeste-developpeur/" title="Accéder à l’article complet">Manifeste de développeur</a>,
  833. <a href="/david/blog/2013/confort-convivialite/" title="Accéder à l’article complet">Confort et convivialité</a>,
  834. <a href="/david/blog/2013/testament-numerique/" title="Accéder à l’article complet">Testament numérique</a>,
  835. et <a href="/david/blog/" title="Accéder aux archives">bien d’autres…</a>
  836. </p>
  837. <p>
  838. On peut <a href="mailto:david%40larlet.fr" title="Envoyer un courriel">échanger par courriel</a>. Si éventuellement tu souhaites que l’on travaille ensemble, tu devrais commencer par consulter le <a href="http://larlet.com">profil dédié à mon activité professionnelle</a> et/ou contacter directement <a href="http://scopyleft.fr/">scopyleft</a>, la <abbr title="Société coopérative et participative">SCOP</abbr> dont je fais partie depuis six ans. Je recommande au préalable de lire <a href="/david/blog/2018/cout-site/" title="Attention ce qui va suivre peut vous choquer">combien coûte un site</a> et pourquoi je suis plutôt favorable à une <a href="/david/pro/devis/" title="Discutons-en !">non-demande de devis</a>.
  839. </p>
  840. <p>
  841. Je ne traque pas ta navigation mais mon
  842. <abbr title="Alwaysdata, 62 rue Tiquetonne 75002 Paris, +33.184162340">hébergeur</abbr>
  843. conserve des logs d’accès.
  844. </p>
  845. </div>
  846. </footer>
  847. <script type="text/javascript">
  848. ;(_ => {
  849. const jumper = document.getElementById('jumper')
  850. jumper.addEventListener('click', e => {
  851. e.preventDefault()
  852. const anchor = e.target.getAttribute('href')
  853. const targetEl = document.getElementById(anchor.substring(1))
  854. targetEl.scrollIntoView({behavior: 'smooth'})
  855. })
  856. })()
  857. </script>