A place to cache linked articles (think custom and personal wayback machine)
Du kannst nicht mehr als 25 Themen auswählen Themen müssen mit entweder einem Buchstaben oder einer Ziffer beginnen. Sie können Bindestriche („-“) enthalten und bis zu 35 Zeichen lang sein.

index.html 22KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182
  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` element
  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,initial-scale=1">
  11. <!-- Required to make a valid HTML5 document. -->
  12. <title>How a Wikipedia volunteer editor became a very vocal Web3 critic (archive) — David Larlet</title>
  13. <meta name="description" content="Publication mise en cache pour en conserver une trace.">
  14. <!-- That good ol' feed, subscribe :). -->
  15. <link rel="alternate" type="application/atom+xml" title="Feed" href="/david/log/">
  16. <!-- Generated from https://realfavicongenerator.net/ such a mess. -->
  17. <link rel="apple-touch-icon" sizes="180x180" href="/static/david/icons2/apple-touch-icon.png">
  18. <link rel="icon" type="image/png" sizes="32x32" href="/static/david/icons2/favicon-32x32.png">
  19. <link rel="icon" type="image/png" sizes="16x16" href="/static/david/icons2/favicon-16x16.png">
  20. <link rel="manifest" href="/static/david/icons2/site.webmanifest">
  21. <link rel="mask-icon" href="/static/david/icons2/safari-pinned-tab.svg" color="#07486c">
  22. <link rel="shortcut icon" href="/static/david/icons2/favicon.ico">
  23. <meta name="msapplication-TileColor" content="#f7f7f7">
  24. <meta name="msapplication-config" content="/static/david/icons2/browserconfig.xml">
  25. <meta name="theme-color" content="#f7f7f7" media="(prefers-color-scheme: light)">
  26. <meta name="theme-color" content="#272727" media="(prefers-color-scheme: dark)">
  27. <!-- Documented, feel free to shoot an email. -->
  28. <link rel="stylesheet" href="/static/david/css/style_2021-01-20.css">
  29. <!-- See https://www.zachleat.com/web/comprehensive-webfonts/ for the trade-off. -->
  30. <link rel="preload" href="/static/david/css/fonts/triplicate_t4_poly_regular.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: light), (prefers-color-scheme: no-preference)" crossorigin>
  31. <link rel="preload" href="/static/david/css/fonts/triplicate_t4_poly_bold.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: light), (prefers-color-scheme: no-preference)" crossorigin>
  32. <link rel="preload" href="/static/david/css/fonts/triplicate_t4_poly_italic.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: light), (prefers-color-scheme: no-preference)" crossorigin>
  33. <link rel="preload" href="/static/david/css/fonts/triplicate_t3_regular.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: dark)" crossorigin>
  34. <link rel="preload" href="/static/david/css/fonts/triplicate_t3_bold.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: dark)" crossorigin>
  35. <link rel="preload" href="/static/david/css/fonts/triplicate_t3_italic.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: dark)" crossorigin>
  36. <script>
  37. function toggleTheme(themeName) {
  38. document.documentElement.classList.toggle(
  39. 'forced-dark',
  40. themeName === 'dark'
  41. )
  42. document.documentElement.classList.toggle(
  43. 'forced-light',
  44. themeName === 'light'
  45. )
  46. }
  47. const selectedTheme = localStorage.getItem('theme')
  48. if (selectedTheme !== 'undefined') {
  49. toggleTheme(selectedTheme)
  50. }
  51. </script>
  52. <meta name="robots" content="noindex, nofollow">
  53. <meta content="origin-when-cross-origin" name="referrer">
  54. <!-- Canonical URL for SEO purposes -->
  55. <link rel="canonical" href="https://www.fastcompany.com/90733574/how-a-wikipedia-engineer-became-one-of-the-loudest-web3-skeptics">
  56. <body class="remarkdown h1-underline h2-underline h3-underline em-underscore hr-center ul-star pre-tick" data-instant-intensity="viewport-all">
  57. <article>
  58. <header>
  59. <h1>How a Wikipedia volunteer editor became a very vocal Web3 critic</h1>
  60. </header>
  61. <nav>
  62. <p class="center">
  63. <a href="/david/" title="Aller à l’accueil"><svg class="icon icon-home">
  64. <use xlink:href="/static/david/icons2/symbol-defs-2021-12.svg#icon-home"></use>
  65. </svg> Accueil</a> •
  66. <a href="https://www.fastcompany.com/90733574/how-a-wikipedia-engineer-became-one-of-the-loudest-web3-skeptics" title="Lien vers le contenu original">Source originale</a>
  67. </p>
  68. </nav>
  69. <hr>
  70. <div><p>A new blockchain-based internet that abhors huge tech platforms, embraces digital currencies, and lets individuals control their data and identity sounds like a lovely idea. But a growing <a href="https://moxie.org/2022/01/07/web3-first-impressions.html" target="_blank" rel="noopener noreferrer">chorus</a> of <a href="https://www.youtube.com/watch?v=YQ_xWvX1n9g" target="_blank" rel="noopener noreferrer">skeptics</a> are saying that Web3–the term used to sum up these concepts–is at best highly aspirational and at worst a flat-out scam.</p></div>
  71. <div><p>Some of these critics express their doubts on Substack, or in YouTube rants, or on company blogs. Others voice their skepticism with their wallets, <a href="https://www.investopedia.com/news/short-bitcoin/#:~:text=Can%20Bitcoin%20be%20shorted%3F,of%20which%20there%20are%20many." target="_blank" rel="noopener noreferrer">shorting cryptocurrencies</a> like Bitcoin or Eth. <span>Molly White, a software engineer and volunteer Wikipedia editor, has a simpler approach, and it’s a good one. </span></p><p><span>White has emerged as one of Web3’s sharpest critics by simply compiling Web3’s day-to-day mishaps and ripoffs–its non-theoretical real-world consequences–at </span><a href="http://web3isgoinggreat.com/" target="_blank" rel="noopener noreferrer"><span>Web3 Is Going Great</span></a><span>, a website (and </span><a href="https://twitter.com/web3isgreat" target="_blank" rel="noopener noreferrer"><span>Twitter account</span></a><span>) she created and curates. The steady stream of these news stories (many of which aren’t covered in mainstream media) strongly suggests that Web3, in fact, isn’t going as great as its legions of cheerleaders would have you believe.</span></p><p>I spoke with White via email about her views on Web3 fixtures such as DAOs (distributed autonomous organizations), cryptocurrencies, and NFTs (non-fungible tokens). Our conversation has been lightly edited for length and clarity. <em>(Disclosure: I own a modest amount of Bitcoin, mainly for research purposes.)</em></p></div>
  72. <div><p><strong>Why were you compelled to start the Web3 Is Going Great? What were you seeing at the time?</strong></p><p>Although cryptocurrencies and blockchains have been around for a long time now, last year this “web3” shift really seemed to take off: this idea that blockchains will be the “future of the web.” People pushing this were saying that before long, everyone would use crypto, many services would be built on top of some blockchain or another, and all web interactions would be <a href="https://en.wikipedia.org/wiki/Financialization" target="_blank" rel="noopener noreferrer">financialized</a> in some way—all things that sound like a pretty terrible “future of the web” to me. Last year also felt like the year when the scamminess of the crypto space truly exploded, and also the year where the people behind a lot of these projects really set their sights on the average layperson (rather than the computer geek or the speculative investor) as their target audience. Everyday people were being told that they should put their money into crypto in one form or another, and I was beginning to see a lot of projects that to me seemed to be targeting the particularly vulnerable: totally unregulated apps encouraging people to take out sketchy loans to get out of a financial pinch, or projects promising to help people “invest” their retirement money into crypto, for example.</p><p>As I began learning about the topic a little more, I also began coming across just <a href="https://www.justice.gov/usao-sdny/pr/president-sham-united-nations-affiliate-convicted-cryptocurrency-scheme" target="_blank" rel="noopener noreferrer">scam</a> after <a href="https://cointelegraph.com/news/binance-tells-regulators-it-will-cease-operations-in-ontario-for-real-this-time" target="_blank" rel="noopener noreferrer">scam</a> after <a href="https://www.coindesk.com/tech/2022/03/15/derivatives-platform-deus-finance-exploited-for-3m-on-fantom-network/" target="_blank" rel="noopener noreferrer">scam</a>, and <a href="https://cointelegraph.com/news/espn-s-baseball-reporter-s-twitter-account-hacked-by-nft-scammers" target="_blank" rel="noopener noreferrer">hack</a> after <a href="https://floridapolitics.com/archives/509932-hackers-hijack-nikki-fried-campaign-twitter-account/" target="_blank" rel="noopener noreferrer">hack</a> after <a href="https://www.theblockcrypto.com/post/138250/hacker-steals-790000-of-nfts-and-crypto-from-owners-of-rare-bears" target="_blank" rel="noopener noreferrer">hack</a>. It seemed like every day a <a href="https://www.nbcnews.com/tech/security/bitcoin-crypto-exchange-hacks-little-anyone-can-do-rcna7870" target="_blank" rel="noopener noreferrer">huge project was being hacked</a>, or someone was launching something and <a href="https://www.coindesk.com/markets/2016/10/27/the-plot-thickens-as-dao-attacker-trades-stolen-funds-for-bitcoin/" target="_blank" rel="noopener noreferrer">making off</a> with all the money, or people were getting their crypto wallets compromised through some technique or another. But the stories were all very fleeting—I would see them on Twitter or in a brief news headline, and then the social media/news attention span would move along and it was like it never even happened. I realized it could be really informative and meaningful to gather all of these disasters in one place, to both show how unfit this technology is for practically all use cases, and to show just how much people are <a href="https://www.ftc.gov/news-events/news/press-releases/2021/05/ftc-data-shows-huge-spike-cryptocurrency-investment-scams" target="_blank" rel="noopener noreferrer">getting scammed</a> when they try to dip their toes in.</p></div>
  73. <div><p><strong>Why do you think we’re seeing such shocking amounts of scams around cryptocurrencies, NFTs, and the like? What is it about these models that make it such fertile ground for scammers?</strong></p><p>It’s enormously unregulated, and the regulations that should apply have been slow to be enforced. People seem to have this opinion that, because a cryptocurrency is involved, they can do anything they want: <a href="https://jacobinmag.com/2022/01/cryptocurrency-scam-blockchain-bitcoin-economy-decentralization" target="_blank" rel="noopener noreferrer">operate a Ponzi scheme</a>, or <a href="https://news.bitcoin.com/coinbase-sued-for-allegedly-selling-79-unregistered-crypto-securities-xrp-dogecoin-shiba-inu/" target="_blank" rel="noopener noreferrer">sell unregistered securities</a>. To some extent, they have been able to do anything they want, even the blatantly illegal stuff, because the regulatory enforcement has been so slow. But I also think we’re starting to see a change in that, and there are probably more than a few people behind various crypto projects who have been seeing <a href="https://www.sec.gov/news/press-release/2021-172" target="_blank" rel="noopener noreferrer">enforcement actions by the SEC</a> and others on scams that were happening several years ago, and thinking “uh oh, that looks a lot like what I’ve been doing”.</p><p>I think the amount of hype that’s being pumped into the space is contributing to the issue, too. It’s coming from everywhere—the media, <a href="https://www.washingtonpost.com/arts-entertainment/2022/02/04/celebrities-cryptocurrency-nfts/" target="_blank" rel="noopener noreferrer">big-name celebrities</a>, advertisements on mainstream TV networks, and of course social media. There’s a reason that get-rich-quick schemes are so enticing, and because it tends to be the success stories that get the attention, I think people start to believe that it’s actually common for people to make money from these things. It’s also a bit of a perfect storm with economic uncertainty facing fairly young people (who by far seem to be the ones being pulled into these scams): They’re more likely to have the types of jobs that were impacted particularly severely by the pandemic, and many of them are facing enormous debts from things like student loans.</p></div>
  74. <div><p><strong>Has your opinion NFTs, crypto, and other blockchain models evolved at all since you started W3IGG?</strong></p><p>If anything, I probably have an even stronger opinion that these technologies are enabling a lot of harm, with few promising use cases or upsides. I’ve spent the last couple of months pretty immersed in this stuff—both learning about a ton of specific Web3 projects just to be able to cover them in the site, but also researching the underlying technologies and problems they’re trying to solve, as well as speaking with a lot of other experts on the subject and hearing their opinions.</p><p><strong>It seems like a lot of VCs are very excited about the blockchain and crypto. Do you have any thoughts about why this might be?</strong></p></div>
  75. <div><p>VCs are excited about blockchains and cryptocurrencies for the same reason VCs are excited about anything: It’s a moneymaking opportunity. People are putting a lot of money into crypto, and despite all the ideological talk about how crypto might democratize wealth or remove such outsized amounts of it from the hands of a few big players (including some of the same enormous venture capital firms investing in crypto), that’s not actually what’s happening. The wealth is even more centralized in crypto, in many ways, and the space is beautifully designed for that to continue.</p><p>Crypto also promises the opportunity of quicker returns than a lot of their more traditional investments—if a VC firm’s share in a project is represented in crypto, they can cash out anytime, rather than having to wait for a company to IPO.</p><p><strong>What is your impression of DAOs?</strong></p></div>
  76. <div><p>My overwhelming impression is that most of the projects calling themselves DAOs are neither distributed nor autonomous, and the ones that are trying to be have been organized by people who have done a lot of thinking about how such an organization might work in theory, but have little practical experience with those kinds of organizations.</p><p><strong>In some of the reporting I’ve done about DAOs, I got the impression that it’s not always practical or possible to create something that’s totally decentralized and democratic. </strong></p><p>If you take a look at a lot of the groups calling themselves “DAOs”, you’ll see that they are often just one person or group of people controlling the project. Some of them ostensibly have governance tokens and community votes on proposals for the project, but we’ve seen more than one instance where a community has voted for one thing and the leaders of the so-called decentralized project have just decided to do something else. In other cases, there is not even a nominal attempt at having any sort of community governance. Some of those projects say they have plans for community governance to be added later (usually after the money is raised, of course), but whether they actually follow through on those promises is anyone’s guess.</p></div>
  77. <div><p><strong>Do you think people might eventually find a way to make DAOs functional and useful?</strong></p><p>There are lots of existing structures for decentralized governance that have existed in society for far, far longer than DAOs have been around. Look at co-ops, for example. You could even argue that shareholders of most public companies have rights similar to participants in DAOs. Outside of the business world there are all sorts of examples of decentralized, leaderless groups: the Wikimedia movement, for example, or also groups like Occupy Wall Street or Alcoholics Anonymous. I personally find it unlikely that anyone with significant experience in any group like this would ever argue that the goals or mechanisms of these groups could be fully, reasonably represented in code.</p><p>DAOs are, I think, one of the best illustrations of the problem with a lot of these Web3 projects: They are trying to find technological solutions that will somehow codify very complex social structures. A lot of them also seem to operate under the assumption that everyone is acting in good faith, and that project members’ interests will generally align—a baffling assumption given the amount of bad actors in the crypto space.</p></div>
  78. <div><p><strong>I think a lot of people are trying to understand if there are real, practical use cases for Web3 models like NFTs and DAOs that will emerge after all the initial hype and hucksterism fade away. What do you think? Is there a “there” there?</strong></p><p>No, there isn’t.</p><p>NFTs and DAOs are both great examples of solutions desperately in search of a problem. People have tried to come up with <a href="https://www.fastcompany.com/90704232/new-uses-for-nfts" target="_blank" rel="noopener noreferrer">ideas for how NFTs might be useful</a> if the interest in them as a speculative investment fades, and the ideas seem incredibly uncompelling—using them for things like event tickets, which are already being bought and sold quite adequately on existing systems.</p></div>
  79. <div><p>I suspect that the hype and hucksterism will fade away when <a href="https://www.fastcompany.com/90731182/what-president-bidens-executive-order-on-crypto-really-means" target="_blank" rel="noopener noreferrer">regulators step in</a>, and make it a lot harder for influencers to pump and dump tokens without disclosing their financial interests, or for people to promise impossible returns on what are clearly Ponzi schemes, or for people to sell what are pretty obviously unregistered securities. But when that aspect is taken away, so is much of the incentive to use the technology in the first place. You’re just left with a slow, expensive datastore that doesn’t scale well, and some really complex hurdles to overcome around privacy and data ownership.</p></div>
  80. <p id="collapsible-placeholder"></p>
  81. </article>
  82. <hr>
  83. <footer>
  84. <p>
  85. <a href="/david/" title="Aller à l’accueil"><svg class="icon icon-home">
  86. <use xlink:href="/static/david/icons2/symbol-defs-2021-12.svg#icon-home"></use>
  87. </svg> Accueil</a> •
  88. <a href="/david/log/" title="Accès au flux RSS"><svg class="icon icon-rss2">
  89. <use xlink:href="/static/david/icons2/symbol-defs-2021-12.svg#icon-rss2"></use>
  90. </svg> Suivre</a> •
  91. <a href="http://larlet.com" title="Go to my English profile" data-instant><svg class="icon icon-user-tie">
  92. <use xlink:href="/static/david/icons2/symbol-defs-2021-12.svg#icon-user-tie"></use>
  93. </svg> Pro</a> •
  94. <a href="mailto:david%40larlet.fr" title="Envoyer un courriel"><svg class="icon icon-mail">
  95. <use xlink:href="/static/david/icons2/symbol-defs-2021-12.svg#icon-mail"></use>
  96. </svg> Email</a> •
  97. <abbr class="nowrap" title="Hébergeur : Alwaysdata, 62 rue Tiquetonne 75002 Paris, +33184162340"><svg class="icon icon-hammer2">
  98. <use xlink:href="/static/david/icons2/symbol-defs-2021-12.svg#icon-hammer2"></use>
  99. </svg> Légal</abbr>
  100. </p>
  101. <template id="theme-selector">
  102. <form>
  103. <fieldset>
  104. <legend><svg class="icon icon-brightness-contrast">
  105. <use xlink:href="/static/david/icons2/symbol-defs-2021-12.svg#icon-brightness-contrast"></use>
  106. </svg> Thème</legend>
  107. <label>
  108. <input type="radio" value="auto" name="chosen-color-scheme" checked> Auto
  109. </label>
  110. <label>
  111. <input type="radio" value="dark" name="chosen-color-scheme"> Foncé
  112. </label>
  113. <label>
  114. <input type="radio" value="light" name="chosen-color-scheme"> Clair
  115. </label>
  116. </fieldset>
  117. </form>
  118. </template>
  119. </footer>
  120. <script src="/static/david/js/instantpage-5.1.0.min.js" type="module"></script>
  121. <script>
  122. function loadThemeForm(templateName) {
  123. const themeSelectorTemplate = document.querySelector(templateName)
  124. const form = themeSelectorTemplate.content.firstElementChild
  125. themeSelectorTemplate.replaceWith(form)
  126. form.addEventListener('change', (e) => {
  127. const chosenColorScheme = e.target.value
  128. localStorage.setItem('theme', chosenColorScheme)
  129. toggleTheme(chosenColorScheme)
  130. })
  131. const selectedTheme = localStorage.getItem('theme')
  132. if (selectedTheme && selectedTheme !== 'undefined') {
  133. form.querySelector(`[value="${selectedTheme}"]`).checked = true
  134. }
  135. }
  136. const prefersColorSchemeDark = '(prefers-color-scheme: dark)'
  137. window.addEventListener('load', () => {
  138. let hasDarkRules = false
  139. for (const styleSheet of Array.from(document.styleSheets)) {
  140. let mediaRules = []
  141. for (const cssRule of styleSheet.cssRules) {
  142. if (cssRule.type !== CSSRule.MEDIA_RULE) {
  143. continue
  144. }
  145. // WARNING: Safari does not have/supports `conditionText`.
  146. if (cssRule.conditionText) {
  147. if (cssRule.conditionText !== prefersColorSchemeDark) {
  148. continue
  149. }
  150. } else {
  151. if (cssRule.cssText.startsWith(prefersColorSchemeDark)) {
  152. continue
  153. }
  154. }
  155. mediaRules = mediaRules.concat(Array.from(cssRule.cssRules))
  156. }
  157. // WARNING: do not try to insert a Rule to a styleSheet you are
  158. // currently iterating on, otherwise the browser will be stuck
  159. // in a infinite loop…
  160. for (const mediaRule of mediaRules) {
  161. styleSheet.insertRule(mediaRule.cssText)
  162. hasDarkRules = true
  163. }
  164. }
  165. if (hasDarkRules) {
  166. loadThemeForm('#theme-selector')
  167. }
  168. })
  169. </script>
  170. </body>
  171. </html>