Congratulations!

[Valid RSS] This is a valid RSS feed.

Recommendations

This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.

Source: http://www.zeldman.com/feed/zeldman.xml

  1. <?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
  2. xmlns:content="http://purl.org/rss/1.0/modules/content/"
  3. xmlns:wfw="http://wellformedweb.org/CommentAPI/"
  4. xmlns:dc="http://purl.org/dc/elements/1.1/"
  5. xmlns:atom="http://www.w3.org/2005/Atom"
  6. xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
  7. xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
  9. xmlns:georss="http://www.georss.org/georss"
  10. xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#"
  11. >
  12.  
  13. <channel>
  14. <title>Zeldman on Web and Interaction Design</title>
  15. <atom:link href="https://zeldman.com/feed/" rel="self" type="application/rss+xml" />
  16. <link>https://zeldman.com/</link>
  17. <description>Since 1995. Formerly “The Daily Report.”</description>
  18. <lastBuildDate>Fri, 19 Apr 2024 17:01:45 +0000</lastBuildDate>
  19. <language>en-US</language>
  20. <sy:updatePeriod>
  21. hourly </sy:updatePeriod>
  22. <sy:updateFrequency>
  23. 1 </sy:updateFrequency>
  25.  
  26. <image>
  27. <url>https://i0.wp.com/zeldman.com/wp-content/uploads/2014/12/cropped-default-54a3966bv1_site_icon.png?fit=32%2C32&#038;ssl=1</url>
  28. <title>Zeldman on Web and Interaction Design</title>
  29. <link>https://zeldman.com/</link>
  30. <width>32</width>
  31. <height>32</height>
  32. </image>
  33. <site xmlns="com-wordpress:feed-additions:1">227043043</site> <item>
  34. <title>This Web of Ours, Revisited</title>
  35. <link>https://zeldman.com/2024/04/19/this-web-of-ours-revisited/</link>
  36. <comments>https://zeldman.com/2024/04/19/this-web-of-ours-revisited/#respond</comments>
  38. <dc:creator><![CDATA[L. Jeffrey Zeldman]]></dc:creator>
  39. <pubDate>Fri, 19 Apr 2024 16:57:00 +0000</pubDate>
  40. <category><![CDATA[Accessibility]]></category>
  41. <category><![CDATA[Adobe]]></category>
  42. <category><![CDATA[Advocacy]]></category>
  43. <category><![CDATA[AIGA]]></category>
  44. <category><![CDATA[art direction]]></category>
  45. <category><![CDATA[Authoring]]></category>
  46. <category><![CDATA[Bandwidth]]></category>
  47. <category><![CDATA[Best practices]]></category>
  48. <category><![CDATA[Browsers]]></category>
  49. <category><![CDATA[business]]></category>
  50. <category><![CDATA[Career]]></category>
  51. <category><![CDATA[client management]]></category>
  52. <category><![CDATA[Community]]></category>
  53. <category><![CDATA[creativity]]></category>
  54. <category><![CDATA[CSS]]></category>
  55. <category><![CDATA[Design]]></category>
  56. <category><![CDATA[Designers]]></category>
  57. <category><![CDATA[development]]></category>
  58. <category><![CDATA[Digital Preservation]]></category>
  59. <category><![CDATA[Fonts]]></category>
  60. <category><![CDATA[Future-Friendly]]></category>
  61. <category><![CDATA[HTML]]></category>
  62. <category><![CDATA[industry]]></category>
  63. <category><![CDATA[interface]]></category>
  64. <category><![CDATA[maturity]]></category>
  65. <category><![CDATA[Medium]]></category>
  66. <category><![CDATA[My Back Pages]]></category>
  67. <category><![CDATA[Off My Lawn!]]></category>
  68. <category><![CDATA[Performance]]></category>
  69. <category><![CDATA[Photoshop]]></category>
  70. <category><![CDATA[Rants]]></category>
  71. <category><![CDATA[Real type on the web]]></category>
  72. <category><![CDATA[Responsibility]]></category>
  73. <category><![CDATA[Responsive Web Design]]></category>
  74. <category><![CDATA[Site Optimization]]></category>
  75. <category><![CDATA[Standards]]></category>
  76. <category><![CDATA[State of the Web]]></category>
  77. <category><![CDATA[The Essentials]]></category>
  78. <category><![CDATA[The Profession]]></category>
  79. <category><![CDATA[Typography]]></category>
  80. <category><![CDATA[Usability]]></category>
  81. <category><![CDATA[User Experience]]></category>
  82. <category><![CDATA[UX]]></category>
  83. <category><![CDATA[Web Design]]></category>
  84. <category><![CDATA[Web Design History]]></category>
  85. <category><![CDATA[Web Standards]]></category>
  86. <category><![CDATA[Websites]]></category>
  87. <category><![CDATA[webtype]]></category>
  88. <category><![CDATA[work]]></category>
  89. <category><![CDATA[Working]]></category>
  90. <category><![CDATA[writing]]></category>
  91. <category><![CDATA[aesthetics]]></category>
  92. <category><![CDATA[columns]]></category>
  93. <category><![CDATA[constraints]]></category>
  94. <category><![CDATA[designing]]></category>
  95. <category><![CDATA[HTMHell]]></category>
  96. <category><![CDATA[limitations]]></category>
  97. <category><![CDATA[ThatWasThen]]></category>
  98. <guid isPermaLink="false">https://zeldman.com/?p=17967</guid>
  99.  
  100. <description><![CDATA[<p>Why did leading designers in 2000 look down their nose at the web? And are things any better today?</p>
  101. <p>The post <a href="https://zeldman.com/2024/04/19/this-web-of-ours-revisited/">This Web of Ours, Revisited</a> appeared first on <a href="https://zeldman.com">Zeldman on Web and Interaction Design</a>.</p>
  102. ]]></description>
  103. <content:encoded><![CDATA[
  104. <p class="has-large-font-size">ONE MONTH and 24 years ago, in “<a href="https://web.archive.org/web/20000510122107/http://www.adobe.com/web/columns/zeldman/20000320/main.html">Where Have All the Designers Gone?</a>” (my <em>HTMHell</em> design column for Adobe of March 20, 2000), I discussed the deepening rift between aesthetically focused web designers and those primarily concerned with creating good experiences online:</p>
  105.  
  106.  
  107.  
  108. <blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
  109. <p><strong>More and more web designers seem less and less interested in web design.</strong></p>
  110.  
  111.  
  112.  
  113. <p>Over the past 18 months or so, many of the best practitioners in the industry seem to have given up on the notion that a low-bandwidth, less than cutting-edge site is worth making. Much of the stuff they&#8217;ve been making instead has been beautiful and inspiring. But if top designers wash their hands of the rest of the Web, whose hands will build it, and whose minds will guide it? The possibilities are frightening.</p>
  114. </blockquote>
  115.  
  116.  
  117.  
  118. <h2 class="wp-block-heading" id="h-an-imperfect-medium-for-perfectionists">An Imperfect Medium for Perfectionists</h2>
  119.  
  120.  
  121.  
  122. <p>Why were many of the leading graphic designers and studios at the time uninterested in web design?&nbsp;For one thing, designers trained to strive for visual perfection found the web’s unpredictability depressing. The article provided clues to the frustrations of the time:</p>
  123.  
  124.  
  125.  
  126. <blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
  127. <p>Good designers spend hours tweaking typography in Illustrator and Photoshop. Then visitors with slow connections turn off images.</p>
  128. </blockquote>
  129.  
  130.  
  131.  
  132. <p>Of course, where professionals trained in graphic design saw a distressing lack of control, others glimpsed in the infant technology a tremendous potential to help people, pixel-perfection be damned. To reduce the conflict to a cartoon, you might characterize it as <a href="https://www.davidcarsondesign.com/">David Carson</a> versus <a href="https://www.nngroup.com/people/jakob-nielsen/">Jakob Nielsen</a>—though doing so would trivialize the concerns of both men. Designers already charged with creating websites found themselves somewhere in the middle—barking themselves hoarse reminding clients and managers that pixel-perfect rendering was not a thing on the web, while arguing with developers who told designers the exact same thing. </p>
  133.  
  134.  
  135.  
  136. <p>Visually inspiring websites like <a href="https://www.webdesignmuseum.org/gallery/kaliber10000-2003">K10k</a> showed that the web could, if approached carefully and joyfully, provide aesthetic delight. But many designers (along with organizations like AIGA) were unaware of those sites at the time.</p>
  137.  
  138.  
  139.  
  140. <h2 class="wp-block-heading" id="h-us-and-them">Us and Them</h2>
  141.  
  142.  
  143.  
  144. <p>Another source of tension in the medium in 2000 sprang from the discrepancy between the privileged access designers enjoyed—fast connections, up-to-date browsers and operating systems, high-res monitors (at least for the time) offering thousands of colors—versus the slow modems, aging and underpowered computers, outdated browsers, and limited-color monitors through which most people at the time experienced the web. </p>
  145.  
  146.  
  147.  
  148. <p>Which was the <em>real</em> design? The widescreen, multicolor, grid-based experience? Or the 216-color job with pixelated Windows type, a shallow “fold,” and pictures of headline text that took forever to be seen? </p>
  149.  
  150.  
  151.  
  152. <p>To view your masterpiece the way most users experienced it, and at the syrup-slow speed with which they experienced it, was to have an awakening or a nightmare—depending on your empathy quotient. Some designers began to take usability, accessibility, and performance seriously as part of their jobs; others fled for the predictability of more settled media (such as print).</p>
  153.  
  154.  
  155.  
  156. <h2 class="wp-block-heading" id="h-a-new-old-hope">A New (Old) Hope</h2>
  157.  
  158.  
  159.  
  160. <p>My March, 2000 article ended on an upbeat note—and a gentle call to action:</p>
  161.  
  162.  
  163.  
  164. <blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
  165. <p>For content sites to attain the credibility and usefulness of print magazines; for entertainment sites to truly entertain; for commerce sites and Web-based applications to function aesthetically as well as technically, the gifts of talented people are needed. We hope to see you among them.</p>
  166. </blockquote>
  167.  
  168.  
  169.  
  170. <p>That was my hope in 2000, and, all these years later, it remains my vision for this web of ours. For though the browsers, connections, and hardware have changed substantially over the past 24 years, and though the medium and its practitioners have, to a significant extent, grown the Hell up, beneath the surface, in 2024, many of these same attitudes and conflicts persist. We can do better.</p>
  171.  
  172.  
  173.  
  174. <p>Minus the framesets that formerly contained it, you may <a href="https://web.archive.org/web/20000510122107/http://www.adobe.com/web/columns/zeldman/20000320/main.html">read the original text</a> (complete with archaic instructions about 4.0 browsers and JavaScript that broke my heart, but which Adobe’s editors and producers insisted on posting) courtesy of the Wayback Machine. </p>
  175.  
  176.  
  177.  
  178. <p>☞&nbsp; <em><a href="https://twitter.com/andrey_taritsyn/status/1780199397323616722">Hat tip to Andrey Taritsyn</a> for digging up the article, which I had long forgotten.</em></p>
  179. <p>The post <a href="https://zeldman.com/2024/04/19/this-web-of-ours-revisited/">This Web of Ours, Revisited</a> appeared first on <a href="https://zeldman.com">Zeldman on Web and Interaction Design</a>.</p>
  180. ]]></content:encoded>
  182. <wfw:commentRss>https://zeldman.com/2024/04/19/this-web-of-ours-revisited/feed/</wfw:commentRss>
  183. <slash:comments>0</slash:comments>
  186. <post-id xmlns="com-wordpress:feed-additions:1">17967</post-id> </item>
  187. <item>
  188. <title>Don’t bring venture capital to a knife fight</title>
  189. <link>https://zeldman.com/2024/04/18/dont-bring-venture-capital-to-a-knife-fight/</link>
  190. <comments>https://zeldman.com/2024/04/18/dont-bring-venture-capital-to-a-knife-fight/#comments</comments>
  192. <dc:creator><![CDATA[L. Jeffrey Zeldman]]></dc:creator>
  193. <pubDate>Thu, 18 Apr 2024 12:34:15 +0000</pubDate>
  194. <category><![CDATA[Apple]]></category>
  195. <category><![CDATA[business]]></category>
  196. <category><![CDATA[Internet of Things]]></category>
  197. <category><![CDATA[Startups]]></category>
  198. <category><![CDATA[innovation]]></category>
  199. <category><![CDATA[internet of things]]></category>
  200. <category><![CDATA[IOT]]></category>
  201. <category><![CDATA[screens]]></category>
  202. <category><![CDATA[startups]]></category>
  203. <category><![CDATA[VC]]></category>
  204. <category><![CDATA[venture capital]]></category>
  205. <guid isPermaLink="false">https://zeldman.com/?p=17960</guid>
  206.  
  207. <description><![CDATA[<p>Why you can’t build another Apple with VC bucks.</p>
  208. <p>The post <a href="https://zeldman.com/2024/04/18/dont-bring-venture-capital-to-a-knife-fight/">Don’t bring venture capital to a knife fight</a> appeared first on <a href="https://zeldman.com">Zeldman on Web and Interaction Design</a>.</p>
  209. ]]></description>
  210. <content:encoded><![CDATA[
  211. <blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
  212. <p>Contrary to what Imran, Ken, and I’m sure many others at <a href="https://www.theverge.com/24126502/humane-ai-pin-review?ref=sandofsky.com">Humane</a> believe, the iPhone didn’t begin with their work in the 2000’s on Project Purple. It began in 1976 with the Apple computer, and the decades of goodwill it built up in consumers. The project was spearheaded by a guy ready to waste billions in iPod revenue if it helped achieve his vision, and he answered to nobody. It came together at the perfect point in time, when everyone knew the power of the Internet, but there wasn’t a way to carry the whole experience in your pocket. You can’t replicate all these factors in a few years, no matter how much money a VC throws at you.</p>
  213.  
  214.  
  215.  
  216. <p>Benjamin Sandofsky, <a href="https://www.sandofsky.com/humane/">Oh, the Humanity: Why You Can’t Build Apple With Venture Capital</a></p>
  217. </blockquote>
  218. <p>The post <a href="https://zeldman.com/2024/04/18/dont-bring-venture-capital-to-a-knife-fight/">Don’t bring venture capital to a knife fight</a> appeared first on <a href="https://zeldman.com">Zeldman on Web and Interaction Design</a>.</p>
  219. ]]></content:encoded>
  221. <wfw:commentRss>https://zeldman.com/2024/04/18/dont-bring-venture-capital-to-a-knife-fight/feed/</wfw:commentRss>
  222. <slash:comments>1</slash:comments>
  225. <post-id xmlns="com-wordpress:feed-additions:1">17960</post-id> </item>
  226. <item>
  227. <title>Both Sides, No</title>
  228. <link>https://zeldman.com/2024/04/17/both-sides-no/</link>
  229. <comments>https://zeldman.com/2024/04/17/both-sides-no/#respond</comments>
  231. <dc:creator><![CDATA[L. Jeffrey Zeldman]]></dc:creator>
  232. <pubDate>Wed, 17 Apr 2024 21:44:28 +0000</pubDate>
  233. <category><![CDATA[Journalism at its Finest]]></category>
  234. <category><![CDATA[links]]></category>
  235. <category><![CDATA[News]]></category>
  236. <category><![CDATA[Politics]]></category>
  237. <category><![CDATA[Press]]></category>
  238. <category><![CDATA[Publications]]></category>
  239. <category><![CDATA[Reporting]]></category>
  240. <category><![CDATA[Responsibility]]></category>
  241. <category><![CDATA[Standards]]></category>
  242. <category><![CDATA[USA]]></category>
  243. <category><![CDATA[bothsideism]]></category>
  244. <category><![CDATA[bothsides]]></category>
  245. <category><![CDATA[bothsidesing]]></category>
  246. <category><![CDATA[truth in journalism]]></category>
  247. <guid isPermaLink="false">https://zeldman.com/?p=17946</guid>
  248.  
  249. <description><![CDATA[<p>Even when it’s ugly—especially when it’s ugly—journalists owe readers the truth.</p>
  250. <p>The post <a href="https://zeldman.com/2024/04/17/both-sides-no/">Both Sides, No</a> appeared first on <a href="https://zeldman.com">Zeldman on Web and Interaction Design</a>.</p>
  251. ]]></description>
  252. <content:encoded><![CDATA[
  253. <p class="has-normal-font-size">There’s no situation so awful our news media can’t make it worse. In a cowardly, doomed, and deeply misguided effort to appear “balanced” during an emergency that requires plain speaking, our news editors tie headlines into fantastic pretzels of spurious equivalence. In <a href="https://www.washingtonpost.com/opinions/2024/04/17/mailbag-trump-trial/">today’s edition of her subscriber-only newsletter</a>, <em>Washington Post</em> columnist Jennifer Rubin tears into an <a href="https://twitter.com/MarkJacob16/status/1778259512874373485">especially egregious atrocity</a> by the copy wizards of <em>The New York Times</em>:</p>
  254.  
  255.  
  256.  
  257. <blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
  258. <p><strong>Journalism 101</strong></p>
  259.  
  260.  
  261.  
  262. <p>People on social media and other critics justifiably mocked, derided and denounced the New York Times for the headline, “<a href="https://www.nytimes.com/2024/04/10/us/politics/trump-biden-abortion-message.html">Two Imperfect Messengers Take On Abortion</a>.” The sub-headline was nearly as bad: “Neither side of the abortion divide would probably design the exact candidate they have in 2024.” This could be the crown jewel of “both-sidesism,” accomplishing that feat in multiple ways.</p>
  263.  
  264.  
  265.  
  266. <p>For starters, it blurs the distinction between Biden’s clear and unwavering position (to write&nbsp;<em>Roe v. Wade</em>&nbsp;into a federal statute) with&nbsp;<a href="https://www.nbcnews.com/politics/donald-trump/trumps-abortion-stances-republicans-2024-gop-rcna147222">Trump’s</a>&nbsp;<a href="https://twitter.com/IsaacDovere/status/1778145633896939914">well-documented</a>&nbsp;<a href="https://www.washingtonpost.com/politics/2024/04/08/trump-abortion-stances/?itid=lk_inline_manual_33">inconsistencies</a>,&nbsp;<a href="https://www.washingtonpost.com/politics/2024/04/08/trumps-cynical-punt-abortion/?itid=lk_inline_manual_33">deflections</a>&nbsp;and&nbsp;<a href="https://www.nbcnews.com/politics/donald-trump/trumps-many-abortion-positions-timeline-rcna146601">contradictions</a>. These two men simply are&nbsp;<em>not&nbsp;</em>equally deficient communicators. That imbalance in clarity and sincerity actually might determine the campaign’s outcome.</p>
  267.  
  268.  
  269.  
  270. <p>In addition to mischaracterizing the candidates’ relative abilities, this quintessential “process story” diminishes the issue’s moral gravity. You could not imagine a 1942 headline: “Two imperfect messengers take on world war.” Awarding style points, as the story does, trivializes the abortion issue.</p>
  271.  
  272.  
  273.  
  274. <p>Finally, the Times headline amounts to a self-parody of&nbsp;<a href="https://www.cjr.org/the_media_today/debate_trump_biden_chris_wallace.php">gamified</a>&nbsp;political&nbsp;<a href="https://www.pbs.org/newshour/show/how-media-organizations-are-facing-the-task-of-covering-trumps-anti-democratic-rhetoric">coverage</a>: “Neither side of the abortion divide would probably design the exact candidate they have in 2024.” (Well, neither team in the World Series would design the exact lineup they have.) In essence, the Times tells us, “No one’s perfect!”<em>&nbsp;—</em>&nbsp;an empty platitude. Journalists owe readers an accurate depiction of the candidates’ vast differences in consistency, clarity and moral seriousness on abortion. Alas, such precision would demand truth-telling in lieu of feigned “balance.”</p>
  275. </blockquote>
  276.  
  277.  
  278.  
  279. <p>Washington Post subscribers can view the <a href="https://www.washingtonpost.com/opinions/2024/04/17/mailbag-trump-trial/">complete text of today’s newsletter</a> on the paper’s website. You may also <a href="https://www.washingtonpost.com/newsletters/jennifer-rubin/?method=SURL&amp;location=ART&amp;initiative=TOP&amp;itid=lk_inline_manual_2">sign up to get it in your inbox</a> free of charge.</p>
  280. <p>The post <a href="https://zeldman.com/2024/04/17/both-sides-no/">Both Sides, No</a> appeared first on <a href="https://zeldman.com">Zeldman on Web and Interaction Design</a>.</p>
  281. ]]></content:encoded>
  283. <wfw:commentRss>https://zeldman.com/2024/04/17/both-sides-no/feed/</wfw:commentRss>
  284. <slash:comments>0</slash:comments>
  287. <post-id xmlns="com-wordpress:feed-additions:1">17946</post-id> </item>
  288. <item>
  289. <title>For love of pixels</title>
  290. <link>https://zeldman.com/2024/04/13/for-love-of-pixels/</link>
  291. <comments>https://zeldman.com/2024/04/13/for-love-of-pixels/#comments</comments>
  293. <dc:creator><![CDATA[L. Jeffrey Zeldman]]></dc:creator>
  294. <pubDate>Sat, 13 Apr 2024 14:19:59 +0000</pubDate>
  295. <category><![CDATA[apps]]></category>
  296. <category><![CDATA[Archiving]]></category>
  297. <category><![CDATA[art]]></category>
  298. <category><![CDATA[Design]]></category>
  299. <category><![CDATA[Illustration]]></category>
  300. <category><![CDATA[My Back Pages]]></category>
  301. <category><![CDATA[Web Design]]></category>
  302. <category><![CDATA[Web Design History]]></category>
  303. <category><![CDATA[copland]]></category>
  304. <category><![CDATA[iconfactory]]></category>
  305. <category><![CDATA[k10k]]></category>
  306. <category><![CDATA[mozco]]></category>
  307. <category><![CDATA[mozco !garash!]]></category>
  308. <category><![CDATA[susan kare]]></category>
  309. <category><![CDATA[wayback]]></category>
  310. <category><![CDATA[webdesign]]></category>
  311. <guid isPermaLink="false">https://zeldman.com/?p=17923</guid>
  312.  
  313. <description><![CDATA[<p>Stroll with us down memory lane as we celebrate the pearl anniversary of pixel art creation’s primary progenitor, and some of the many artists and design languages it inspired.</p>
  314. <p>The post <a href="https://zeldman.com/2024/04/13/for-love-of-pixels/">For love of pixels</a> appeared first on <a href="https://zeldman.com">Zeldman on Web and Interaction Design</a>.</p>
  315. ]]></description>
  316. <content:encoded><![CDATA[
  317. <p class="has-drop-cap has-normal-font-size">Sure, watches that tell you when you’re walking unsteadily and pocket computer phones that show you the closest pizzeria are swell, but were you around for <a href="https://en.wikipedia.org/wiki/ResEdit">ResEdit</a>? That humble yet supremely capable Macintosh resource editing tool is what we used to design pixel art back in the day. (And what day <em>was</em> that? Come August, it will be 30 years since the final release of ResEdit 2.1.3.) Stroll with us down memory lane as we celebrate the pearl anniversary of pixel art creation’s primary progenitor, and some of the many artists and design languages it inspired. Extra credit: When you finish your stroll, consider posting a Comment sharing your appreciation for this nearly forgotten art form and/or sharing links to additional pixel art icon treasures missing from our list below.</p>
  318.  
  319.  
  320.  
  321. <ul>
  322. <li><a href="https://kare.com/">Susan Kare website</a> (kare.com)&nbsp;| <a href="https://kare.com/apple-icons/">Susan Kare Apple Macintosh icons</a> (kare.com) | <a href="https://en.wikipedia.org/wiki/Susan_Kare">Susan Kare bio</a> (Wikipedia)</li>
  323.  
  324.  
  325.  
  326. <li><a href="https://freeware.iconfactory.com/icons">Iconfactory Freeware icons</a> feat. decades-old works of genius such as this <a href="https://en.wikipedia.org/wiki/Copland_(operating_system)">Copland</a>-inspired <a href="https://freeware.iconfactory.com/preview/apdt">Apple desktop collection</a></li>
  327.  
  328.  
  329.  
  330. <li><a href="http://www.thedeadpixelsociety.net/">The Dead Pixel Society </a>(2014) and <a href="http://www.thedeadpixelsociety.net/founders/">founders</a>: “We honor the humble pixel with icon creations designed under 90&#8217;s era MacOS constraints:&nbsp;256 colors, pixel-by-pixel, on a 32 x 32 canvas.” </li>
  331.  
  332.  
  333.  
  334. <li><a href="https://www.webdesignmuseum.org/gallery/kaliber10000-2003">K10k in 2003</a> (℅ <a href="https://www.webdesignmuseum.org/all-websites">Web Design Museum</a>); mini-bonus: <a href="https://dribbble.com/tags/k10k">K10k tag on Dribbble</a></li>
  335.  
  336.  
  337.  
  338. <li><a href="https://web.archive.org/web/20010104173800/http://www.tcp-ip.or.jp/~s-iga/">MOZCO&nbsp;!GARASH!</a> via Wayback Machine ℅ <a href="https://www.flickr.com/photos/rainsford/3345195030">Flickr post</a> by <a href="http://johnrainsford.com/">John Rainsford</a></li>
  339.  
  340.  
  341.  
  342. <li><a href="https://web.archive.org/web/20021017024953/http://www.iconfactory.com:80/cb_home.asp">Introducing Candybar</a> by <a href="https://panic.com/">Panic</a> and <a href="https://iconfactory.com/">Iconfactory</a> ℅ <a href="https://web.archive.org/">Wayback Machine</a></li>
  343.  
  344.  
  345.  
  346. <li><a href="https://zeldman.com/2014/10/01/dead-pixel-society/">Dead Pixel Society interview post</a> (zeldman.com) and <a href="https://bigwebshow.fireside.fm/121">podcast</a> (<a href="https://bigwebshow.fireside.fm/121">Episode № 121</a> of <a href="https://bigwebshow.fireside.fm/">The Big Web Show</a> featuring <a href="https://bio.link/dauer">Justin Dauer</a> AKA @pseudoroom, creator of the <a href="https://www.pseudoroom.com/portfolio/icons.html">Baby Yoda icon</a> adorning this post).</li>
  347.  
  348.  
  349.  
  350. <li>Still online, albeit with missing files after many server migrations: this very website’s 1995 “<a href="https://zeldman.com/icon1.html">Pardon My Icons</a>” collection.</li>
  351.  
  352.  
  353.  
  354. <li>Semi-related and interesting: “<a href="https://alistapart.com/article/a-pixel-identity-crisis/">A Pixel Identity Crisis</a>” by <a href="https://scottkellum.com/">Scott Kellum</a> in <a href="https://alistapart.com/issue/342/"><em>A List Apart</em> Issue № 342</a>, January 17, 2012</li>
  355. </ul>
  356. <p>The post <a href="https://zeldman.com/2024/04/13/for-love-of-pixels/">For love of pixels</a> appeared first on <a href="https://zeldman.com">Zeldman on Web and Interaction Design</a>.</p>
  357. ]]></content:encoded>
  359. <wfw:commentRss>https://zeldman.com/2024/04/13/for-love-of-pixels/feed/</wfw:commentRss>
  360. <slash:comments>8</slash:comments>
  363. <post-id xmlns="com-wordpress:feed-additions:1">17923</post-id> </item>
  364. <item>
  365. <title>Akismet means never having to say you’re sorry</title>
  366. <link>https://zeldman.com/2024/04/09/akismet-means-never-having-to-say-youre-sorry/</link>
  367. <comments>https://zeldman.com/2024/04/09/akismet-means-never-having-to-say-youre-sorry/#comments</comments>
  369. <dc:creator><![CDATA[L. Jeffrey Zeldman]]></dc:creator>
  370. <pubDate>Tue, 09 Apr 2024 14:11:34 +0000</pubDate>
  371. <category><![CDATA[AI]]></category>
  372. <category><![CDATA[automattic]]></category>
  373. <category><![CDATA[Blogs and Blogging]]></category>
  374. <category><![CDATA[content]]></category>
  375. <category><![CDATA[guestbook spam]]></category>
  376. <category><![CDATA[Indieweb]]></category>
  377. <category><![CDATA[industry]]></category>
  378. <category><![CDATA[Own your content]]></category>
  379. <category><![CDATA[software]]></category>
  380. <category><![CDATA[State of the Web]]></category>
  381. <category><![CDATA[Surviving]]></category>
  382. <category><![CDATA[The Essentials]]></category>
  383. <category><![CDATA[Websites]]></category>
  384. <category><![CDATA[Akismet]]></category>
  385. <category><![CDATA[FightBack]]></category>
  386. <category><![CDATA[spam]]></category>
  387. <guid isPermaLink="false">https://zeldman.com/?p=17906</guid>
  388.  
  389. <description><![CDATA[<p>The bots who shit in your sandbox are bigger, brassier, and better than ever!</p>
  390. <p>The post <a href="https://zeldman.com/2024/04/09/akismet-means-never-having-to-say-youre-sorry/">Akismet means never having to say you’re sorry</a> appeared first on <a href="https://zeldman.com">Zeldman on Web and Interaction Design</a>.</p>
  391. ]]></description>
  392. <content:encoded><![CDATA[
  393. <p class="has-large-font-size">The wizards behind AI have been busy lately providing meaningful employment for digital nonpersons. </p>
  394.  
  395.  
  396.  
  397. <p class="has-normal-font-size">One of the hottest jobs for non-humans is crafting and deploying website guestbook spam. This market’s on fire!</p>
  398.  
  399.  
  400.  
  401. <p>If you thought the guestbook spam of yore was impressive, you ain’t seen nothing yet.&nbsp;The new, AI-assisted comment spam has improved keyword stuffing, fewer grammatical mistakes, and, best of all, there’s tons more of it. Your Comment section was never so useless!</p>
  402.  
  403.  
  404.  
  405. <p>And we’re not just talking quantity, here; we’re talking quality.</p>
  406.  
  407.  
  408.  
  409. <p>Compared to the spammers of yore, the new signal depressors have a bold confidence that proclaims, “Hello, world! I’m here to waste your time and extinguish what’s left of your hard-won reader community. Watch me work!”</p>
  410.  
  411.  
  412.  
  413. <p>Yes, the bots who shit in your sandbox are bigger, brassier, and better than ever at wasting your readers’ time and abusing your content to score points on the Google big board.</p>
  414.  
  415.  
  416.  
  417. <p>What’s that you say? You’re <em>not</em> a comment spam enthusiast? <br><br>In that case, do as I do: use <a href="https://akismet.com/">Akismet</a> to keep cruft where it belongs: off your website. Akismet was strong enough for the comment, form, and text spam of the past, and it’s strong enough for the new junk, too.<br><br>(Full disclosure: I work at Automattic, makers of Akismet, but I penned this post this morning purely as an Akismet <em>customer</em>, after happily reviewing the blocked comment spam on this here WordPress site of mine. Thanks, Akismet!)</p>
  418. <p>The post <a href="https://zeldman.com/2024/04/09/akismet-means-never-having-to-say-youre-sorry/">Akismet means never having to say you’re sorry</a> appeared first on <a href="https://zeldman.com">Zeldman on Web and Interaction Design</a>.</p>
  419. ]]></content:encoded>
  421. <wfw:commentRss>https://zeldman.com/2024/04/09/akismet-means-never-having-to-say-youre-sorry/feed/</wfw:commentRss>
  422. <slash:comments>4</slash:comments>
  425. <post-id xmlns="com-wordpress:feed-additions:1">17906</post-id> </item>
  426. <item>
  427. <title>My Glamorous Life: Roman Holiday</title>
  428. <link>https://zeldman.com/2024/04/06/my-glamorous-life-roman-holiday/</link>
  429. <comments>https://zeldman.com/2024/04/06/my-glamorous-life-roman-holiday/#comments</comments>
  431. <dc:creator><![CDATA[L. Jeffrey Zeldman]]></dc:creator>
  432. <pubDate>Sun, 07 Apr 2024 01:43:24 +0000</pubDate>
  433. <category><![CDATA[Authoring]]></category>
  434. <category><![CDATA[books]]></category>
  435. <category><![CDATA[family]]></category>
  436. <category><![CDATA[glamorous]]></category>
  437. <category><![CDATA[Publishing]]></category>
  438. <category><![CDATA[Travel]]></category>
  439. <guid isPermaLink="false">https://zeldman.com/?p=17895</guid>
  440.  
  441. <description><![CDATA[<p>The ancient amphitheatre was our destination; we had been walking toward it excitedly, with greater and greater speed.</p>
  442. <p>The post <a href="https://zeldman.com/2024/04/06/my-glamorous-life-roman-holiday/">My Glamorous Life: Roman Holiday</a> appeared first on <a href="https://zeldman.com">Zeldman on Web and Interaction Design</a>.</p>
  443. ]]></description>
  444. <content:encoded><![CDATA[
  445. <p class="has-large-font-size">While honeymooning in Rome, we spotted an Italian translation of my second book in the display window of a quaint old shop two blocks from the <a href="https://en.wikipedia.org/wiki/Colosseum">Colosseum</a>. </p>
  446.  
  447.  
  448.  
  449. <p>The ancient amphitheatre was our destination; we had been walking toward it excitedly, with greater and greater speed. But the bizarre sight of <em><a href="https://www.google.com/search?q=designing+with+web+standards&amp;oq=designing+with+web&amp;gs_lcrp=EgZjaHJvbWUqCggAEAAY4wIYgAQyCggAEAAY4wIYgAQyBwgBEC4YgAQyBggCEEUYOTIGCAMQRRhAMggIBBAAGBYYHjIGCAUQRRg8MgYIBhBFGEEyBggHEEUYPKgCALACAQ&amp;sourceid=chrome&amp;ie=UTF-8#ip=1">Designing With Web Standards</a></em> in this strange location halted our progress. </p>
  450.  
  451.  
  452.  
  453. <p>For my book, my name, my face to be here, of all places! What were the chances? For a text about something as new and ephemeral as web design to show up in this timeless and eternal plaza! How crazy was that?</p>
  454.  
  455.  
  456.  
  457. <p>The shop owner, adjusting his window display, shot us a quizzical smile. My companion pointed to my face, and then to the book cover, which bore my photo. The owner shrugged; he did not understand. If life were a movie, I would have whipped a blue beanie out of my coat pocket. But it isn’t, and I had none.</p>
  458.  
  459.  
  460.  
  461. <p>So there I stood. The author, at a loss for words.</p>
  462.  
  463.  
  464.  
  465. <p>And then we smiled, and he smiled, and we continued our passage toward the ancient home of bread and circuses.</p>
  466. <p>The post <a href="https://zeldman.com/2024/04/06/my-glamorous-life-roman-holiday/">My Glamorous Life: Roman Holiday</a> appeared first on <a href="https://zeldman.com">Zeldman on Web and Interaction Design</a>.</p>
  467. ]]></content:encoded>
  469. <wfw:commentRss>https://zeldman.com/2024/04/06/my-glamorous-life-roman-holiday/feed/</wfw:commentRss>
  470. <slash:comments>4</slash:comments>
  473. <post-id xmlns="com-wordpress:feed-additions:1">17895</post-id> </item>
  474. <item>
  475. <title>The More Things Change… (or: What’s in a Job Title?)</title>
  476. <link>https://zeldman.com/2024/04/03/the-more-things-change-or-whats-in-a-job-title/</link>
  477. <comments>https://zeldman.com/2024/04/03/the-more-things-change-or-whats-in-a-job-title/#comments</comments>
  479. <dc:creator><![CDATA[L. Jeffrey Zeldman]]></dc:creator>
  480. <pubDate>Wed, 03 Apr 2024 09:48:47 +0000</pubDate>
  481. <category><![CDATA[Authoring]]></category>
  482. <category><![CDATA[Best practices]]></category>
  483. <category><![CDATA[Blogs and Blogging]]></category>
  484. <category><![CDATA[Code]]></category>
  485. <category><![CDATA[Compatibility]]></category>
  486. <category><![CDATA[CSS]]></category>
  487. <category><![CDATA[Design]]></category>
  488. <category><![CDATA[development]]></category>
  489. <category><![CDATA[Free Advice]]></category>
  490. <category><![CDATA[Future-Friendly]]></category>
  491. <category><![CDATA[HTML]]></category>
  492. <category><![CDATA[industry]]></category>
  493. <category><![CDATA[Layout]]></category>
  494. <category><![CDATA[links]]></category>
  495. <category><![CDATA[maturity]]></category>
  496. <category><![CDATA[Off My Lawn!]]></category>
  497. <category><![CDATA[Platforms]]></category>
  498. <category><![CDATA[Rants]]></category>
  499. <category><![CDATA[Responsibility]]></category>
  500. <category><![CDATA[Standards]]></category>
  501. <category><![CDATA[State of the Web]]></category>
  502. <category><![CDATA[The Profession]]></category>
  503. <category><![CDATA[Web Design]]></category>
  504. <category><![CDATA[Web Design History]]></category>
  505. <category><![CDATA[Web Standards]]></category>
  506. <category><![CDATA[wisdom]]></category>
  507. <category><![CDATA[frontend]]></category>
  508. <category><![CDATA[webdesign]]></category>
  509. <category><![CDATA[webstandards]]></category>
  510. <guid isPermaLink="false">https://zeldman.com/?p=17877</guid>
  511.  
  512. <description><![CDATA[<p>I’m designing for the web. The infinitely flexible web. </p>
  513. <p>The post <a href="https://zeldman.com/2024/04/03/the-more-things-change-or-whats-in-a-job-title/">The More Things Change… (or: What’s in a Job Title?)</a> appeared first on <a href="https://zeldman.com">Zeldman on Web and Interaction Design</a>.</p>
  514. ]]></description>
  515. <content:encoded><![CDATA[
  516. <blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
  517. <p>I’m not a “<a href="https://bradfrost.com/blog/post/full-stack-developers/">[full-stack] developer</a>,” regardless of what my last job title says.</p>
  518.  
  519.  
  520.  
  521. <p>I’m not even a <a href="https://css-tricks.com/the-great-divide/">front-end developer</a>, thanks to the JavaScript–<a href="https://en.wikipedia.org/wiki/Industrial_complex">industrial complex</a>.</p>
  522.  
  523.  
  524.  
  525. <p>I’m a&nbsp;<a href="https://bradfrost.com/blog/post/front-of-the-front-end-and-back-of-the-front-end-web-development/">front-of-the-front-end developer</a>, but that’s too long.</p>
  526.  
  527.  
  528.  
  529. <p>So, I’m a&nbsp;<a href="https://heather-buchel.com/blog/2023/10/why-your-web-design-sucks/">web designer</a>. And I also specialise in accessibility, design systems, and design.</p>
  530.  
  531.  
  532.  
  533. <p>…Why do I think that this is the best title? Here’s why. <br><br>I’m designing for the web. The infinitely flexible web. The web that doesn’t have one screen size, one browser, one operating system, or one device. The web that can be used by anyone, anywhere, on any internet connection, on any device, on any operating system, on any browser, with any screen size. I’m designing with the web. Using the web platform (HTML, CSS, JS, ARIA, etc.), not a bloated harmful abstraction. I have a deep understanding of HTML and its semantics. I love CSS, I know how and when to utilise its many features, and I keep up-to-date as more are added. I have a strong understanding of modern JavaScript and most importantly I know when not to use it.</p>
  534. <cite><a href="https://www.ellyloel.com/blog/front-end-development-s-identity-crisis/#i-m-a-web-designer">Front-end development’s identity crisi</a><a href="https://www.ellyloel.com/blog/front-end-development-s-identity-crisis/">s</a> by <a href="https://www.ellyloel.com/">Elly Loel</a></cite></blockquote>
  535.  
  536.  
  537.  
  538. <p>See also:<br><br><a href="https://alistapart.com/article/the-wax-and-the-wane-of-the-web/">The Wax and the Wane of the Web</a> (2024): Forget death and taxes. The only certainty on the web is change. Ste Grainer takes a brief look at the history of the web and how it has been constantly reinvented. Then he explores where we are now, and how we can shape the future of the web for the better. –&nbsp;<em>A List Apart</em><br><br><a href="https://alistapart.com/article/cult-of-the-complex/">The Cult of the Complex</a> (2018): If we wish to get back to the business of quietly improving people’s lives, one thoughtful interaction at a time, we must rid ourselves of the cult of the complex. Admitting the problem is the first step in solving it. –&nbsp;<em>A List Apart</em><br><br><a href="http://Dear AIGA, where are the web designers?">Dear AIGA, where are the web designers?</a> (2007): For all the brand directors, creative directors, Jungian analysts, and print designers, one rather significant specimen of the profession is missing. –&nbsp;<em>zeldman.com</em><br><br><a href="https://alistapart.com/article/standardization-and-the-open-web/">Standardization and the Open Web</a> (2015): How do web standards become, well, standard? Although they’re often formalized through official standards-making organizations, they can also emerge through popular practice among the developer community. If both sides don’t work together, we risk delaying implementation, stifling creativity, and losing ground to politics and paralysis. Jory Burson sheds light on the historical underpinnings of web standardization processes—and what that means for the future of the open web. –&nbsp;<em>A List Apart</em><br><br><a href="https://zeldman.com/2007/04/25/the-profession-that-dare-not-speak-its-name/">The profession that dare not speak its name</a> (2007): “No one has tried to measure web design because web design has been a hidden profession.” –&nbsp;<em>zeldman.com</em><br><br></p>
  539. <p>The post <a href="https://zeldman.com/2024/04/03/the-more-things-change-or-whats-in-a-job-title/">The More Things Change… (or: What’s in a Job Title?)</a> appeared first on <a href="https://zeldman.com">Zeldman on Web and Interaction Design</a>.</p>
  540. ]]></content:encoded>
  542. <wfw:commentRss>https://zeldman.com/2024/04/03/the-more-things-change-or-whats-in-a-job-title/feed/</wfw:commentRss>
  543. <slash:comments>2</slash:comments>
  546. <post-id xmlns="com-wordpress:feed-additions:1">17877</post-id> </item>
  547. <item>
  548. <title>Our Lady of Perpetual Profit</title>
  549. <link>https://zeldman.com/2024/04/01/our-lady-of-perpetual-profit/</link>
  550. <comments>https://zeldman.com/2024/04/01/our-lady-of-perpetual-profit/#respond</comments>
  552. <dc:creator><![CDATA[L. Jeffrey Zeldman]]></dc:creator>
  553. <pubDate>Mon, 01 Apr 2024 16:13:01 +0000</pubDate>
  554. <category><![CDATA[Advocacy]]></category>
  555. <category><![CDATA[Best practices]]></category>
  556. <category><![CDATA[business]]></category>
  557. <category><![CDATA[Corporatism]]></category>
  558. <category><![CDATA[creativity]]></category>
  559. <category><![CDATA[ethics]]></category>
  560. <category><![CDATA[Ideas]]></category>
  561. <category><![CDATA[industry]]></category>
  562. <category><![CDATA[links]]></category>
  563. <category><![CDATA[Rants]]></category>
  564. <category><![CDATA[State of the Web]]></category>
  565. <category><![CDATA[The Essentials]]></category>
  566. <category><![CDATA[wealth]]></category>
  567. <category><![CDATA[work]]></category>
  568. <guid isPermaLink="false">https://zeldman.com/?p=17866</guid>
  569.  
  570. <description><![CDATA[<p>A business world with deeply misguided priorities—exemplified by horror stories from the worlds of tech, gaming, and entertainment—accounts for much worker unhappiness and customer frustration.</p>
  571. <p>The post <a href="https://zeldman.com/2024/04/01/our-lady-of-perpetual-profit/">Our Lady of Perpetual Profit</a> appeared first on <a href="https://zeldman.com">Zeldman on Web and Interaction Design</a>.</p>
  572. ]]></description>
  573. <content:encoded><![CDATA[
  574. <p class="has-large-font-size">Corporations that take investors make an impossible promise to increase profits forever. Accordingly, they hire MBAs whose role is to juggle numbers to create ongoing, short-term profit. This juggling is frequently labeled “leadership.”</p>
  575.  
  576.  
  577.  
  578. <p>The juggling methods—abusing data, diminishing the primacy of the customer relationship, repeating what worked last year as if the demand for it will never end, and perpetually cutting costs—invariably remove value from the company. This, of course, results in more staff and cost cutting.</p>
  579.  
  580.  
  581.  
  582. <p>People who understand the customer and the product are ignored in favor of the number jugglers; research is disparaged in favor of a dogmatic relationship to data.&nbsp;</p>
  583.  
  584.  
  585.  
  586. <p>The people who wreck the company get the big paychecks. Eventually a bigger company buys the first company, further destroying its value. The wreckers exit with more money, 1980s-corporate-raider-style. Skilled workers are laid off, quality plummets, and the cycle begins again.&nbsp;</p>
  587.  
  588.  
  589.  
  590. <p>This picture of a business world with deeply misguided priorities—exemplified by horror stories from the worlds of tech, gaming, and entertainment—is brought to you by Doc Burford, whose discursive post, “<a href="https://docseuss.medium.com/the-biggest-threat-facing-your-team-whether-youre-a-game-developer-or-a-tech-founder-or-a-ceo-is-8cd1ad359508"><strong>the biggest threat facing your team, whether you’re a game developer or a tech founder or a CEO, is not what you think</strong></a>,” takes a while to get through, but is nonetheless worth reading.<br><br>It is not a picture of <em>every</em> company, to be sure. But it applies to many, and accounts for much of the worker unhappiness plus customer frustration that characterize this time and contribute to our political unrest.</p>
  591.  
  592.  
  593.  
  594. <p>I wrote <em>this</em> post so you’d know to check <em>that</em> one. <a href="https://docseuss.medium.com/the-biggest-threat-facing-your-team-whether-youre-a-game-developer-or-a-tech-founder-or-a-ceo-is-8cd1ad359508">Do it</a>. </p>
  595.  
  596.  
  597.  
  598. <p></p>
  599. <p>The post <a href="https://zeldman.com/2024/04/01/our-lady-of-perpetual-profit/">Our Lady of Perpetual Profit</a> appeared first on <a href="https://zeldman.com">Zeldman on Web and Interaction Design</a>.</p>
  600. ]]></content:encoded>
  602. <wfw:commentRss>https://zeldman.com/2024/04/01/our-lady-of-perpetual-profit/feed/</wfw:commentRss>
  603. <slash:comments>0</slash:comments>
  606. <post-id xmlns="com-wordpress:feed-additions:1">17866</post-id> </item>
  607. <item>
  608. <title>The Valley of Hidden Sorrows</title>
  609. <link>https://zeldman.com/2024/03/25/the-valley-of-hidden-sorrows/</link>
  610. <comments>https://zeldman.com/2024/03/25/the-valley-of-hidden-sorrows/#comments</comments>
  612. <dc:creator><![CDATA[L. Jeffrey Zeldman]]></dc:creator>
  613. <pubDate>Mon, 25 Mar 2024 20:38:42 +0000</pubDate>
  614. <category><![CDATA[family]]></category>
  615. <category><![CDATA[glamorous]]></category>
  616. <category><![CDATA[debt]]></category>
  617. <category><![CDATA[healthcare]]></category>
  618. <category><![CDATA[insurance]]></category>
  619. <category><![CDATA[money]]></category>
  620. <category><![CDATA[My Glamorous Life]]></category>
  621. <guid isPermaLink="false">https://zeldman.com/?p=17846</guid>
  622.  
  623. <description><![CDATA[<p>I have this friend. A mountain of unexpected medical debt buried his family at the start of last year. At the same time, the closing of his business stuck him with six figures of personal debt. Liquidating a retirement account and maxing out credit cards bought him short-term breathing room. Mostly, though, it added interest [&#8230;]</p>
  624. <p>The post <a href="https://zeldman.com/2024/03/25/the-valley-of-hidden-sorrows/">The Valley of Hidden Sorrows</a> appeared first on <a href="https://zeldman.com">Zeldman on Web and Interaction Design</a>.</p>
  625. ]]></description>
  626. <content:encoded><![CDATA[
  627. <p class="has-large-font-size">I have this friend. A mountain of unexpected medical debt buried his family at the start of last year. At the same time, the closing of his business stuck him with six figures of personal debt. Liquidating a retirement account and maxing out credit cards bought him short-term breathing room. Mostly, though, it added interest charges and tax penalties to what he already owed. </p>
  628.  
  629.  
  630.  
  631. <p>A year on, the debts still crush him, and the poor fellow only just manages to keep his family housed, fed, and safe. I should add that he’s a professional who enjoys a great job with a generous salary and terrific benefits. One of the lucky people. Privileged, even. Somebody you’d expect to be quite comfortable. But he wakes in fear each morning.</p>
  632.  
  633.  
  634.  
  635. <p>To all who struggle in these times, be kind to others and gentle with yourself.</p>
  636.  
  637.  
  638.  
  639. <p></p>
  640. <p>The post <a href="https://zeldman.com/2024/03/25/the-valley-of-hidden-sorrows/">The Valley of Hidden Sorrows</a> appeared first on <a href="https://zeldman.com">Zeldman on Web and Interaction Design</a>.</p>
  641. ]]></content:encoded>
  643. <wfw:commentRss>https://zeldman.com/2024/03/25/the-valley-of-hidden-sorrows/feed/</wfw:commentRss>
  644. <slash:comments>1</slash:comments>
  647. <post-id xmlns="com-wordpress:feed-additions:1">17846</post-id> </item>
  648. <item>
  649. <title>AI Roundup: The Bad, the Ugly, and the Pretty Cool</title>
  650. <link>https://zeldman.com/2024/03/24/ai-roundup-the-bad-the-ugly-and-the-pretty-cool/</link>
  651. <comments>https://zeldman.com/2024/03/24/ai-roundup-the-bad-the-ugly-and-the-pretty-cool/#comments</comments>
  653. <dc:creator><![CDATA[L. Jeffrey Zeldman]]></dc:creator>
  654. <pubDate>Sun, 24 Mar 2024 14:24:22 +0000</pubDate>
  655. <category><![CDATA[AI]]></category>
  656. <category><![CDATA[Best practices]]></category>
  657. <category><![CDATA[Education]]></category>
  658. <category><![CDATA[environment]]></category>
  659. <category><![CDATA[ethics]]></category>
  660. <category><![CDATA[planet]]></category>
  661. <category><![CDATA[bubbles]]></category>
  662. <category><![CDATA[capitalism]]></category>
  663. <category><![CDATA[energy]]></category>
  664. <category><![CDATA[fear]]></category>
  665. <category><![CDATA[hype]]></category>
  666. <guid isPermaLink="false">https://zeldman.com/?p=17828</guid>
  667.  
  668. <description><![CDATA[<p>Pieces of the web that make differing and complementary sense of the threat and promise of AI.</p>
  669. <p>The post <a href="https://zeldman.com/2024/03/24/ai-roundup-the-bad-the-ugly-and-the-pretty-cool/">AI Roundup: The Bad, the Ugly, and the Pretty Cool</a> appeared first on <a href="https://zeldman.com">Zeldman on Web and Interaction Design</a>.</p>
  670. ]]></description>
  671. <content:encoded><![CDATA[
  672. <p class="has-large-font-size"><em>Ay, ay, AI!</em> Hype, fear, and strongly voiced opinions—the traditional currency of internet conversation—are unequal to this moment, where the Fate of Everything<img src="https://s.w.org/images/core/emoji/15.0.3/72x72/2122.png" alt="™" class="wp-smiley" style="height: 1em; max-height: 1em;" /> dangles from a single gossamer thread. So here are four useful links to pieces of the web that make differing and complementary sense of the threat and promise of AI.</p>
  673.  
  674.  
  675.  
  676. <blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
  677. <p>Of course AI is a bubble. It has all the hallmarks of a classic tech bubble. Pick up a rental car at SFO and drive in either direction on the 101—north to San Francisco, south to Palo Alto—and every single billboard is advertising some kind of AI company. Every business plan has the word “AI” in it, even if the business itself has no AI in it&#8230;<br><br>Tech bubbles come in two varieties: The ones that leave something behind, and the ones that leave&nbsp;<em>nothing&nbsp;</em>behind. Sometimes, it can be hard to guess what kind of bubble you’re living through until it pops and you find out the hard way&#8230;</p>
  678. <cite><a href="https://locusmag.com/2023/12/commentary-cory-doctorow-what-kind-of-bubble-is-ai/">Cory Doctorow: What Kind of Bubble is AI?</a></cite></blockquote>
  679.  
  680.  
  681.  
  682. <blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
  683. <p>de Vries calculates that by 2027 the AI sector could consume between 85 to 134 terawatt hours each year. That’s about the same as the annual energy demand of de Vries’ home country, the Netherlands.&nbsp;</p>
  684. <cite><a href="https://www.theverge.com/24066646/ai-electricity-energy-watts-generative-consumption">The Verge: How much electricity does AI consume?</a></cite></blockquote>
  685.  
  686.  
  687.  
  688. <blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
  689. <p>The Elements of AI is a series of free online courses created by MinnaLearn and the University of Helsinki. We want to encourage as broad a group of people as possible to learn what AI is, what can (and can’t) be done with AI, and how to start creating AI methods. The courses combine theory with practical exercises and can be completed at your own pace.</p>
  690. <cite><a href="https://www.elementsofai.com/">Elements of AI</a></cite></blockquote>
  691.  
  692.  
  693.  
  694. <blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
  695. <p>We define&nbsp;<em>AI literacy&nbsp;</em>as a set of competencies that enables individuals to critically evaluate AI technologies; communicate and collaborate effectively with AI; and use AI as a tool online, at home, and in the workplace.&nbsp;We conducted an extensive review of literature (see&nbsp;<a href="https://dl.acm.org/doi/abs/10.1145/3313831.3376727">paper</a>) and distilled a set of key AI literacy competencies and considerations for designing AI literacy learning interventions, which can be used to guide future educational initiatives as well as foster discussion and debate in the AI education field. This page lists and describes the competencies and design considerations that we have outlined.</p>
  696. <cite><a href="https://aiunplugged.lmc.gatech.edu/ai-literacy/">AI Unplugged</a></cite></blockquote>
  697. <p>The post <a href="https://zeldman.com/2024/03/24/ai-roundup-the-bad-the-ugly-and-the-pretty-cool/">AI Roundup: The Bad, the Ugly, and the Pretty Cool</a> appeared first on <a href="https://zeldman.com">Zeldman on Web and Interaction Design</a>.</p>
  698. ]]></content:encoded>
  700. <wfw:commentRss>https://zeldman.com/2024/03/24/ai-roundup-the-bad-the-ugly-and-the-pretty-cool/feed/</wfw:commentRss>
  701. <slash:comments>2</slash:comments>
  704. <post-id xmlns="com-wordpress:feed-additions:1">17828</post-id> </item>
  705. <item>
  706. <title>CAPTCHA excludes disabled web users</title>
  707. <link>https://zeldman.com/2024/03/22/captcha-excludes-disabled-web-users/</link>
  708. <comments>https://zeldman.com/2024/03/22/captcha-excludes-disabled-web-users/#respond</comments>
  710. <dc:creator><![CDATA[L. Jeffrey Zeldman]]></dc:creator>
  711. <pubDate>Fri, 22 Mar 2024 11:33:57 +0000</pubDate>
  712. <category><![CDATA[Accessibility]]></category>
  713. <category><![CDATA[Advocacy]]></category>
  714. <category><![CDATA[architecture]]></category>
  715. <category><![CDATA[Authoring]]></category>
  716. <category><![CDATA[Best practices]]></category>
  717. <category><![CDATA[development]]></category>
  718. <category><![CDATA[ethics]]></category>
  719. <category><![CDATA[industry]]></category>
  720. <category><![CDATA[Performance]]></category>
  721. <category><![CDATA[Platforms]]></category>
  722. <category><![CDATA[Responsibility]]></category>
  723. <category><![CDATA[Standards]]></category>
  724. <category><![CDATA[State of the Web]]></category>
  725. <category><![CDATA[Usability]]></category>
  726. <category><![CDATA[User Experience]]></category>
  727. <category><![CDATA[UX]]></category>
  728. <category><![CDATA[W3C]]></category>
  729. <category><![CDATA[Web Standards]]></category>
  730. <category><![CDATA[a11y]]></category>
  731. <category><![CDATA[CAPTCHA]]></category>
  732. <guid isPermaLink="false">https://zeldman.com/?p=17810</guid>
  733.  
  734. <description><![CDATA[<p>The W3C explains how CAPTCHA excludes disabled users, and suggests alternatives that may be kinder and more reliable.</p>
  735. <p>The post <a href="https://zeldman.com/2024/03/22/captcha-excludes-disabled-web-users/">CAPTCHA excludes disabled web users</a> appeared first on <a href="https://zeldman.com">Zeldman on Web and Interaction Design</a>.</p>
  736. ]]></description>
  737. <content:encoded><![CDATA[
  738. <p class="has-large-font-size">What’s widely used, no longer particularly effective, and makes web content inaccessible to many people with disabilities? It’s our old friend CAPTCHA! In a group note dated 16 December 2021, <a href="https://www.w3.org/TR/turingtest/">the W3C explains how CAPTCHA excludes disabled users</a>, and suggests alternatives which may be kinder and more reliable:</p>
  739.  
  740.  
  741.  
  742. <blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
  743. <p>Various approaches have been employed over many years to distinguish human users of web sites from&nbsp;<a href="https://www.w3.org/TR/turingtest/#dfn-robot">robots</a>. The traditional&nbsp;<a href="https://www.w3.org/TR/turingtest/#dfn-captcha">CAPTCHA</a>&nbsp;approach asking users to identify obscured text in an image remains common, but other approaches have emerged. All interactive approaches require users to perform a task believed to be relatively easy for humans but difficult for robots. Unfortunately the very nature of the interactive task inherently excludes many people with disabilities, resulting in a denial of service to these users. Research findings also indicate that many popular CAPTCHA techniques are no longer particularly effective or secure, further complicating the challenge of providing services secured from robotic intrusion yet accessible to people with disabilities. This document examines a number of approaches that allow systems to test for human users and the extent to which these approaches adequately accommodate people with disabilities, including recent non-interactive and tokenized approaches. We have grouped these approaches by two category classifications:&nbsp;<a href="https://www.w3.org/TR/turingtest/#stand-alone-approaches">Stand-Alone Approaches</a>&nbsp;that can be deployed on a web host without engaging the services of unrelated third parties and&nbsp;<a href="https://www.w3.org/TR/turingtest/#multi-party-approaches">Multi-Party Approaches</a>&nbsp;that engage the services of an unrelated third party.</p>
  744. <cite>W3C: <a href="https://www.w3.org/TR/turingtest/">Inaccessibility of CAPTCHA: Alternatives to Visual Turing Tests on the Web</a></cite></blockquote>
  745.  
  746.  
  747.  
  748. <p class="has-large-font-size">We can do better! <br><br>Tell your friends. Tell your boss. Tell your clients. <br><br>Tip o’ the blue beanie to <a href="https://toot.cafe/@aardrian/111953991452184910">Adrian Roselli</a>.</p>
  749.  
  750.  
  751.  
  752. <p></p>
  753. <p>The post <a href="https://zeldman.com/2024/03/22/captcha-excludes-disabled-web-users/">CAPTCHA excludes disabled web users</a> appeared first on <a href="https://zeldman.com">Zeldman on Web and Interaction Design</a>.</p>
  754. ]]></content:encoded>
  756. <wfw:commentRss>https://zeldman.com/2024/03/22/captcha-excludes-disabled-web-users/feed/</wfw:commentRss>
  757. <slash:comments>0</slash:comments>
  760. <post-id xmlns="com-wordpress:feed-additions:1">17810</post-id> </item>
  761. <item>
  762. <title>Heal an ailing web</title>
  763. <link>https://zeldman.com/2024/03/16/heal-an-ailing-web/</link>
  764. <comments>https://zeldman.com/2024/03/16/heal-an-ailing-web/#comments</comments>
  766. <dc:creator><![CDATA[L. Jeffrey Zeldman]]></dc:creator>
  767. <pubDate>Sat, 16 Mar 2024 15:01:19 +0000</pubDate>
  768. <category><![CDATA[State of the Web]]></category>
  769. <category><![CDATA[W3C]]></category>
  770. <category><![CDATA[Web Standards]]></category>
  771. <category><![CDATA[Tim Berners-Lee]]></category>
  772. <category><![CDATA[web history]]></category>
  773. <guid isPermaLink="false">https://zeldman.com/?p=17796</guid>
  774.  
  775. <description><![CDATA[<p>Leadership, hindered by a lack of diversity, has steered away from a tool for public good and one that is instead subject to capitalist forces resulting in monopolisation. Governance, which should correct for this, has failed to do so.</p>
  776. <p>The post <a href="https://zeldman.com/2024/03/16/heal-an-ailing-web/">Heal an ailing web</a> appeared first on <a href="https://zeldman.com">Zeldman on Web and Interaction Design</a>.</p>
  777. ]]></description>
  778. <content:encoded><![CDATA[
  779. <p class="has-large-font-size">On the occasion of the web’s 35th anniversary, <a href="https://webfoundation.org/about/sir-tim-berners-lee/">its inventor</a> <a href="https://webfoundation.org/2024/03/marking-the-webs-35th-birthday-an-open-letter/">had this to say</a>:</p>
  780.  
  781.  
  782.  
  783. <blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
  784. <p>5 years ago, when the web turned 30,&nbsp;<a href="https://webfoundation.org/2019/03/web-birthday-30/" target="_blank" rel="noreferrer noopener">I called out</a>&nbsp;some of the dysfunction caused by the web being dominated by the self-interest of several corporations that have eroded the web’s values and led to breakdown and harm. Now, 5 years on as we arrive at the Web’s 35th Birthday, the rapid advancement of AI has exacerbated these concerns, proving that issues on the web are not isolated but rather deeply intertwined with emerging technologies.&nbsp;</p>
  785.  
  786.  
  787.  
  788. <p>There are two clear, connected issues to address. The first is the extent of power concentration, which contradicts the decentralised spirit I originally envisioned. This has segmented the web, with a fight to keep users hooked on one platform to optimise profit through the passive observation of content. This exploitative business model is particularly grave in this year of elections that could unravel political turmoil. Compounding this issue is the second, the personal data market that has exploited people’s time and data with the creation of deep profiles that allow for targeted advertising and ultimately control over the information people are fed.</p>
  789.  
  790.  
  791.  
  792. <p>How has this happened? Leadership, hindered by a lack of diversity, has steered away from a tool for public good and one that is instead subject to capitalist forces resulting in monopolisation. Governance, which should correct for this, has failed to do so, with regulatory measures being outstripped by the rapid development of innovation, leading to a widening gap between technological advancements and effective oversight.</p>
  793.  
  794.  
  795.  
  796. <p>The future hinges on our ability to both reform the current system and create a new one that genuinely serves the best interests of humanity.&nbsp;</p>
  797. <cite><a href="https://webfoundation.org/2024/03/marking-the-webs-35th-birthday-an-open-letter/">Marking the Web’s 35th Birthday: An Open Letter from Tim Berners-Lee</a></cite></blockquote>
  798. <p>The post <a href="https://zeldman.com/2024/03/16/heal-an-ailing-web/">Heal an ailing web</a> appeared first on <a href="https://zeldman.com">Zeldman on Web and Interaction Design</a>.</p>
  799. ]]></content:encoded>
  801. <wfw:commentRss>https://zeldman.com/2024/03/16/heal-an-ailing-web/feed/</wfw:commentRss>
  802. <slash:comments>1</slash:comments>
  805. <post-id xmlns="com-wordpress:feed-additions:1">17796</post-id> </item>
  806. <item>
  807. <title>Death of a father</title>
  808. <link>https://zeldman.com/2024/03/14/death-of-a-father/</link>
  809. <comments>https://zeldman.com/2024/03/14/death-of-a-father/#respond</comments>
  811. <dc:creator><![CDATA[L. Jeffrey Zeldman]]></dc:creator>
  812. <pubDate>Thu, 14 Mar 2024 14:35:54 +0000</pubDate>
  813. <category><![CDATA[family]]></category>
  814. <category><![CDATA[film]]></category>
  815. <category><![CDATA[My Back Pages]]></category>
  816. <category><![CDATA[187]]></category>
  817. <category><![CDATA[1990s]]></category>
  818. <category><![CDATA[AOL]]></category>
  819. <category><![CDATA[Falling Down]]></category>
  820. <category><![CDATA[Samuel L. Jackson]]></category>
  821. <category><![CDATA[Time Warner]]></category>
  822. <category><![CDATA[trip-hop]]></category>
  823. <category><![CDATA[Warner Bros]]></category>
  824. <guid isPermaLink="false">https://zeldman.com/?p=17782</guid>
  825.  
  826. <description><![CDATA[<p>Today Gerald Levin died. The world will remember him as the architect of the Time Warner AOL merger. But I think of him as a grieving father.</p>
  827. <p>The post <a href="https://zeldman.com/2024/03/14/death-of-a-father/">Death of a father</a> appeared first on <a href="https://zeldman.com">Zeldman on Web and Interaction Design</a>.</p>
  828. ]]></description>
  829. <content:encoded><![CDATA[
  830. <p class="has-large-font-size">“<a href="https://www.imdb.com/title/tt0118531/"><strong>187</strong></a>” is a gorgeously lensed, strongly acted Samuel L. Jackson thriller, notable for its sun-dazzled Los Angeles setting, complex morality, and breakthrough trip-hop soundtrack.&nbsp;It would likely have been widely discussed at the time of its release, and might still be remembered, like the not thematically dissimilar “<a href="https://www.imdb.com/title/tt0118531/">Falling Down</a>”—filmed in the same city and released by the same studio a few years prior—if not for a horrible and tragic event.</p>
  831.  
  832.  
  833.  
  834. <p>187 is the story of a high-minded, humanistic public high school teacher (Jackson) who, after surviving a brutal assault by one of his students (Method Man, in one of his first film appearances!), fights back. </p>
  835.  
  836.  
  837.  
  838. <p>Vigilantism was hardly a fresh plot driver in 1997, but 187’s writer, director, and cast took it to unexpected and rewarding places. 187 challenged expectations. It deserved an audience.</p>
  839.  
  840.  
  841.  
  842. <p>Unfortunately for the film, 187’s release was overshadowed by a horrific real-life event. That year, Jonathan Levin, a public high school teacher, was murdered by one of his former students. <br><br>It was the kind of murder—tragic, senseless—that might have gone unnoticed by the press if not for one thing: Jonathan was the son of newly appointed Time Warner CEO Gerald M. Levin. <br><br>In the aftermath of the new Warner CEO’s son’s murder, there was no way that Warner Bros could promote a film about a high school teacher who kills his students. Warner buried the film by giving it a limited release with zero promotion. </p>
  843.  
  844.  
  845.  
  846. <p>I remember seeing 187 in a semi-private screening room before <a href="https://zeldman.com/15/main.html">interviewing its star</a> for Warner Bros, whose Executive Vice President of Marketing was my client at the time. The film’s moody music and cinematography transported me. I felt deeply engaged by the story, and riveted by Jackson’s performance. And, needless to say, I was also horrified to learn of Jonathan Levin’s murder. <br><br>Today’s <a href="https://deadline.com/2024/03/gerald-levin-dies-former-time-warner-ceo-84-1235858151/https://www.nytimes.com/2024/03/13/obituaries/gerald-m-levin-dead.html?unlocked_article_code=1.ck0.iPvC.Osa_cx1l886F&amp;smid=url-share">d</a><a href="https://deadline.com/2024/03/gerald-levin-dies-former-time-warner-ceo-84-1235858151/">eath notice of Gerald M. Levin</a> brought it all back in a Proustian rush. </p>
  847.  
  848.  
  849.  
  850. <p>Deadline-driven topic-sentence journalists will remember Gerald Levin as the <a href="https://www.hollywoodreporter.com/business/business-news/gerald-levin-dead-architect-aol-time-warner-merger-1235852261/">architect of the ill-fated, oh-so-90s <em>Time Warner AOL</em> merger</a>. But I will always think of him as a grieving father.</p>
  851.  
  852.  
  853.  
  854. <p><em>Rest in peace.</em></p>
  855. <p>The post <a href="https://zeldman.com/2024/03/14/death-of-a-father/">Death of a father</a> appeared first on <a href="https://zeldman.com">Zeldman on Web and Interaction Design</a>.</p>
  856. ]]></content:encoded>
  858. <wfw:commentRss>https://zeldman.com/2024/03/14/death-of-a-father/feed/</wfw:commentRss>
  859. <slash:comments>0</slash:comments>
  862. <post-id xmlns="com-wordpress:feed-additions:1">17782</post-id> </item>
  863. <item>
  864. <title>Open-source moderation</title>
  865. <link>https://zeldman.com/2024/03/13/open-source-moderation/</link>
  866. <comments>https://zeldman.com/2024/03/13/open-source-moderation/#respond</comments>
  868. <dc:creator><![CDATA[L. Jeffrey Zeldman]]></dc:creator>
  869. <pubDate>Wed, 13 Mar 2024 12:43:53 +0000</pubDate>
  870. <category><![CDATA[Open Source]]></category>
  871. <category><![CDATA[social media]]></category>
  872. <category><![CDATA[social networking]]></category>
  873. <category><![CDATA[State of the Web]]></category>
  874. <category><![CDATA[Bluesky]]></category>
  875. <category><![CDATA[Federated]]></category>
  876. <category><![CDATA[moderation]]></category>
  877. <guid isPermaLink="false">https://zeldman.com/?p=17770</guid>
  878.  
  879. <description><![CDATA[<p>“Our online experience doesn’t have to depend on billionaires unilaterally making decisions over what we see.”</p>
  880. <p>The post <a href="https://zeldman.com/2024/03/13/open-source-moderation/">Open-source moderation</a> appeared first on <a href="https://zeldman.com">Zeldman on Web and Interaction Design</a>.</p>
  881. ]]></description>
  882. <content:encoded><![CDATA[
  883. <p class="has-large-font-size"><a href="https://bsky.social/about/blog/03-12-2024-stackable-moderation">Bluesky introduces open-source, collaborative moderation for federated social media websites</a>:</p>
  884.  
  885.  
  886.  
  887. <blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
  888. <p>Bluesky was created to put&nbsp;<a href="https://bsky.social/about/blog/02-22-2024-open-social-web">users and communities in control</a>&nbsp;of their social spaces online. The first generation of social media platforms connected the world, but ended up consolidating power in the hands of a few corporations and their leaders. Our online experience doesn’t have to depend on billionaires unilaterally making decisions over what we see. On an open social network like Bluesky, you can shape your experience for yourself.</p>
  889.  
  890.  
  891.  
  892. <p><strong>Today, we’re excited to announce that we’re&nbsp;<a href="https://github.com/bluesky-social/ozone-ui">open-sourcing Ozone</a>, our collaborative moderation tool. </strong></p>
  893. <cite><a href="https://bsky.social/about/blog/03-12-2024-stackable-moderation">Bluesky’s Stackable Approach to Moderation</a></cite></blockquote>
  894.  
  895.  
  896.  
  897. <p><img src="https://s.w.org/images/core/emoji/15.0.3/72x72/1f4a1.png" alt="💡" class="wp-smiley" style="height: 1em; max-height: 1em;" />  Might it also work for <a href="https://zeldman.com/2024/02/21/in-search-of-a-digital-town-square/">Mastodon and Threads</a>?</p>
  898.  
  899.  
  900.  
  901. <p><br></p>
  902. <p>The post <a href="https://zeldman.com/2024/03/13/open-source-moderation/">Open-source moderation</a> appeared first on <a href="https://zeldman.com">Zeldman on Web and Interaction Design</a>.</p>
  903. ]]></content:encoded>
  905. <wfw:commentRss>https://zeldman.com/2024/03/13/open-source-moderation/feed/</wfw:commentRss>
  906. <slash:comments>0</slash:comments>
  909. <post-id xmlns="com-wordpress:feed-additions:1">17770</post-id> </item>
  910. <item>
  911. <title>New music from the beyond</title>
  912. <link>https://zeldman.com/2024/03/05/new-music-from-the-beyond/</link>
  913. <comments>https://zeldman.com/2024/03/05/new-music-from-the-beyond/#comments</comments>
  915. <dc:creator><![CDATA[L. Jeffrey Zeldman]]></dc:creator>
  916. <pubDate>Tue, 05 Mar 2024 13:54:24 +0000</pubDate>
  917. <category><![CDATA[launches]]></category>
  918. <category><![CDATA[music]]></category>
  919. <category><![CDATA[Pete Zeldman]]></category>
  920. <guid isPermaLink="false">https://zeldman.com/?p=17752</guid>
  921.  
  922. <description><![CDATA[<p>Happy heavenly birthday to my dear, deceased, devil brother Pete Zeldman. Today, 5 March 2024, to celebrate Pete’s life… Lost in Sound Records is releasing an album of solo drums, Enigma, which will keep rhythmic enthusiasts and scholars busy for…well, forever.&#160;And ALSO 2.5D, his crazy interesting NYC rock band… [has released] its first single. —Cindy [&#8230;]</p>
  923. <p>The post <a href="https://zeldman.com/2024/03/05/new-music-from-the-beyond/">New music from the beyond</a> appeared first on <a href="https://zeldman.com">Zeldman on Web and Interaction Design</a>.</p>
  924. ]]></description>
  925. <content:encoded><![CDATA[
  926. <p>Happy heavenly birthday to my dear, deceased, devil brother Pete Zeldman. Today, 5 March 2024, to celebrate Pete’s life…</p>
  927.  
  928.  
  929.  
  930. <blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
  931. <p><a href="https://www.lostinsoundrecords.com/">Lost in Sound Records</a> is releasing an album of solo drums, <a href="https://www.lostinsoundrecords.com/releases-1/enigma">Enigma</a>, which will keep rhythmic enthusiasts and scholars busy for…well, forever.&nbsp;And ALSO <a href="https://www.facebook.com/2.5DMusic?__cft__%5B0%5D=AZWKMNljlCbB5y8v6f2of32tuTljU5-aAnAVnKhMNZ8iJcZXYqkExMOsMZkY8DZrh_wYbwFeuHge04jRJodNqj9CagXDRsvXYBdwrO1Muw4Fez4kSFwDdISrJAVIzQMGDLxT67FiUZP89rQVBDAzEni1ataCqdAHkEe2X-qQLXgjMFmcUW_obGHdfW2RMvk-xvY&amp;__tn__=-%5DK-R">2.5D</a>, his crazy interesting NYC rock band… [has released] its first single.</p>
  932. <cite>—<a href="https://www.facebook.com/cindy.shapiro/posts/pfbid022pp8itY6k9rkQk1irpuekmoZGhq6uAp4ULj6wzeiVoz8fPrQFPpm1PECrLkFDTcul">Cindy Shapiro</a></cite></blockquote>
  933.  
  934.  
  935.  
  936. <p>Hear that single, written by Pete, performed with fire by 2.5D, and released roughly 30 years after the fact:</p>
  937.  
  938.  
  939.  
  940. <ul>
  941. <li><a href="https://open.spotify.com/track/1sbYnHE0BLsaXojdbalnlW?si=7bfbce47472548dd">Stream “I Don’t Wanna Feel” on Spotify</a></li>
  942.  
  943.  
  944.  
  945. <li><a href="https://music.apple.com/us/album/i-dont-wanna-feel-single/1729339191">Stream “I Don’t Wanna Feel” on Apple Music</a></li>
  946.  
  947.  
  948.  
  949. <li><a href="https://music.apple.com/us/album/i-dont-wanna-feel-single/1729339191">Preview and purchase on iTunes Store</a></li>
  950. </ul>
  951.  
  952.  
  953.  
  954. <p><a href="https://www.facebook.com/pete.zeldman">Wish Pete a happy birthday</a> on Facebook. You never know; whatever plane Pete now inhabits, he just might hear you.</p>
  955.  
  956.  
  957.  
  958. <p><em>Related:</em></p>
  959.  
  960.  
  961.  
  962. <figure class="wp-block-embed is-type-wp-embed is-provider-zeldman-on-web-and-interaction-design wp-block-embed-zeldman-on-web-and-interaction-design"><div class="wp-block-embed__wrapper">
  963. <blockquote class="wp-embedded-content" data-secret="EIRfbX7Vge"><a href="https://zeldman.com/2023/01/27/about-pete/">About Pete</a></blockquote><iframe class="wp-embedded-content" sandbox="allow-scripts" security="restricted" title="&#8220;About Pete&#8221; &#8212; Zeldman on Web and Interaction Design" src="https://zeldman.com/2023/01/27/about-pete/embed/#?secret=cCzfewdIEV#?secret=EIRfbX7Vge" data-secret="EIRfbX7Vge" width="580" height="327" frameborder="0" marginwidth="0" marginheight="0" scrolling="no"></iframe>
  964. </div></figure>
  965.  
  966.  
  967.  
  968. <figure class="wp-block-embed is-type-wp-embed is-provider-zeldman-on-web-and-interaction-design wp-block-embed-zeldman-on-web-and-interaction-design"><div class="wp-block-embed__wrapper">
  969. <blockquote class="wp-embedded-content" data-secret="upgjbyFrK1"><a href="https://zeldman.com/2023/03/20/valediction/">Valediction</a></blockquote><iframe class="wp-embedded-content" sandbox="allow-scripts" security="restricted" title="&#8220;Valediction&#8221; &#8212; Zeldman on Web and Interaction Design" src="https://zeldman.com/2023/03/20/valediction/embed/#?secret=Ma2Uzzqi1K#?secret=upgjbyFrK1" data-secret="upgjbyFrK1" width="580" height="327" frameborder="0" marginwidth="0" marginheight="0" scrolling="no"></iframe>
  970. </div></figure>
  971.  
  972.  
  973.  
  974. <figure class="wp-block-embed is-type-wp-embed is-provider-zeldman-on-web-and-interaction-design wp-block-embed-zeldman-on-web-and-interaction-design"><div class="wp-block-embed__wrapper">
  975. <blockquote class="wp-embedded-content" data-secret="E85RX1hVza"><a href="https://zeldman.com/2012/10/23/my-brother-is-a-monster/">My Brother is a Monster</a></blockquote><iframe class="wp-embedded-content" sandbox="allow-scripts" security="restricted" title="&#8220;My Brother is a Monster&#8221; &#8212; Zeldman on Web and Interaction Design" src="https://zeldman.com/2012/10/23/my-brother-is-a-monster/embed/#?secret=wW148AybFe#?secret=E85RX1hVza" data-secret="E85RX1hVza" width="580" height="327" frameborder="0" marginwidth="0" marginheight="0" scrolling="no"></iframe>
  976. </div></figure>
  977. <p>The post <a href="https://zeldman.com/2024/03/05/new-music-from-the-beyond/">New music from the beyond</a> appeared first on <a href="https://zeldman.com">Zeldman on Web and Interaction Design</a>.</p>
  978. ]]></content:encoded>
  980. <wfw:commentRss>https://zeldman.com/2024/03/05/new-music-from-the-beyond/feed/</wfw:commentRss>
  981. <slash:comments>2</slash:comments>
  984. <post-id xmlns="com-wordpress:feed-additions:1">17752</post-id> </item>
  985. <item>
  986. <title>“Where the people are”</title>
  987. <link>https://zeldman.com/2024/03/02/where-the-people-are/</link>
  988. <comments>https://zeldman.com/2024/03/02/where-the-people-are/#comments</comments>
  990. <dc:creator><![CDATA[L. Jeffrey Zeldman]]></dc:creator>
  991. <pubDate>Sat, 02 Mar 2024 14:05:14 +0000</pubDate>
  992. <category><![CDATA[A Book Apart]]></category>
  993. <category><![CDATA[A Feed Apart]]></category>
  994. <category><![CDATA[A List Apart]]></category>
  995. <category><![CDATA[An Event Apart]]></category>
  996. <category><![CDATA[Applications]]></category>
  997. <category><![CDATA[architecture]]></category>
  998. <category><![CDATA[Best practices]]></category>
  999. <category><![CDATA[Career]]></category>
  1000. <category><![CDATA[client services]]></category>
  1001. <category><![CDATA[Community]]></category>
  1002. <category><![CDATA[conferences]]></category>
  1003. <category><![CDATA[creativity]]></category>
  1004. <category><![CDATA[CSS]]></category>
  1005. <category><![CDATA[Design]]></category>
  1006. <category><![CDATA[Designers]]></category>
  1007. <category><![CDATA[Education]]></category>
  1008. <category><![CDATA[eric meyer]]></category>
  1009. <category><![CDATA[experience]]></category>
  1010. <category><![CDATA[Formats]]></category>
  1011. <category><![CDATA[glamorous]]></category>
  1012. <category><![CDATA[Happy Cog™]]></category>
  1013. <category><![CDATA[Ideas]]></category>
  1014. <category><![CDATA[industry]]></category>
  1015. <category><![CDATA[Information architecture]]></category>
  1016. <category><![CDATA[launches]]></category>
  1017. <category><![CDATA[links]]></category>
  1018. <category><![CDATA[maturity]]></category>
  1019. <category><![CDATA[Mentoring]]></category>
  1020. <category><![CDATA[Networks]]></category>
  1021. <category><![CDATA[people]]></category>
  1022. <category><![CDATA[social media]]></category>
  1023. <category><![CDATA[social networking]]></category>
  1024. <category><![CDATA[software]]></category>
  1025. <category><![CDATA[Standards]]></category>
  1026. <category><![CDATA[State of the Web]]></category>
  1027. <category><![CDATA[Stories]]></category>
  1028. <category><![CDATA[Teaching]]></category>
  1029. <category><![CDATA[The Essentials]]></category>
  1030. <category><![CDATA[The Profession]]></category>
  1031. <category><![CDATA[twitter]]></category>
  1032. <category><![CDATA[User Experience]]></category>
  1033. <category><![CDATA[UX]]></category>
  1034. <category><![CDATA[Web Design]]></category>
  1035. <category><![CDATA[Web Design History]]></category>
  1036. <category><![CDATA[wisdom]]></category>
  1037. <category><![CDATA[design principles]]></category>
  1038. <category><![CDATA[principles]]></category>
  1039. <guid isPermaLink="false">https://zeldman.com/?p=17741</guid>
  1040.  
  1041. <description><![CDATA[<p>Fortunately, on that day, I allowed a strong, simple idea to penetrate my big, beautiful wall of assumptions.</p>
  1042. <p>The post <a href="https://zeldman.com/2024/03/02/where-the-people-are/">“Where the people are”</a> appeared first on <a href="https://zeldman.com">Zeldman on Web and Interaction Design</a>.</p>
  1043. ]]></description>
  1044. <content:encoded><![CDATA[
  1045. <p class="has-drop-cap">It’s nearly twenty years ago, now, children. Facebook had only recently burst the bounds of Harvard Yard. Twitter had just slipped the bonds of the digital underground. But web geeks like me still saw “social media” as a continuation of the older digital networks, protocols,&nbsp;<a href="https://www.wikiwand.com/en/LISTSERV">listservs</a>, and discussion forums we’d come up using, and not as the profound disruption that, partnered with smartphones and faster cellular networks, they would soon turn out to be.&nbsp;</p>
  1046.  
  1047.  
  1048.  
  1049. <p>So when world-renowned&nbsp;<a href="https://meyerweb.com/eric/">CSS genius Eric Meyer</a>&nbsp;and I, his plodding Dr Watson, envisioned adding a digital discussion component to&nbsp;<a href="https://aneventapart.com/">our live front-end web design conference events</a>, our first thought had been to create a bespoke one. We had already worked with a partner to adapt a framework he’d built for another client, and were considering whether to continue along that path or forge a new one.</p>
  1050.  
  1051.  
  1052.  
  1053. <p>And then, one day, I was talking to&nbsp;<a href="https://www.wikiwand.com/en/Louis_Rosenfeld">Louis Rosenfeld</a>—the Prometheus of information architecture and&nbsp;<a href="https://rosenfeldmedia.com/people/louis-rosenfeld/">founder of Rosenfeld Media</a>. I told Lou about the quest Eric and I were on, to enhance An Event Apart with a private social network, and shared a roadblock we’d hit. And Lou said something brilliant that day. Something that would never have occurred to me. He said: “Why not use Facebook? It already exists, and that’s where the people are.”</p>
  1054.  
  1055.  
  1056.  
  1057. <h2 class="wp-block-heading" id="h-the-habit-of-building">The habit of building</h2>
  1058.  
  1059.  
  1060.  
  1061. <p>Reader, in all my previous years as a web designer, I had always built from scratch or worked with partners who did so. Perhaps, because I ran a small design agency and my mental framework was client services, the habit of building was ingrained. </p>
  1062.  
  1063.  
  1064.  
  1065. <p>After all, a chief reason clients came to us was because they needed something we could create and they could not. I had a preference for <em>bespoke</em> because it was designed to solve specific problems, which was (and is) the design business model as well as the justification for the profession. </p>
  1066.  
  1067.  
  1068.  
  1069. <p>Our community web design conference had a brand that tied into the brand of&nbsp;<a href="https://alistapart.com/">our community web design magazine</a>&nbsp;(and soon-to-emerge&nbsp;<a href="https://abookapart.com/">community web design book publishing house</a>). All my assumptions and biases were primed for discovery, design, development, and endless ongoing experiments and improvements.</p>
  1070.  
  1071.  
  1072.  
  1073. <p>Use something that was already out there? And not just&nbsp;<em>something</em>, but a clunky walled garden with an embarrassing origin story as a hot-or-not variant cobbled together by an angry, virginal undergraduate? The very idea set off all my self-protective alarms.</p>
  1074.  
  1075.  
  1076.  
  1077. <h2 class="wp-block-heading" id="h-a-lesson-in-humility">A lesson in humility</h2>
  1078.  
  1079.  
  1080.  
  1081. <p>Fortunately, on that day, I allowed a strong, simple idea to penetrate my big, beautiful wall of assumptions.</p>
  1082.  
  1083.  
  1084.  
  1085. <p>Fortunately, I listened to Lou. And brought the idea to Eric, who agreed.</p>
  1086.  
  1087.  
  1088.  
  1089. <p>The story is a bit more complicated than what I’ve just shared. More voices and inputs contributed to the thinking; some development work was done, and a prototype bespoke community was rolled out for our attendees’ pleasure. But ultimately, we followed Lou’s advice, creating a Facebook group because that’s where the people were.&nbsp;</p>
  1090.  
  1091.  
  1092.  
  1093. <p><a href="https://twitter.com/aneventapart">We also used Twitter</a>, during its glory days (which coincided with our conference’s). <a href="https://www.flickr.com/photos/tags/aneventapart/">And Flickr</a>. Because those places are where the people were. </p>
  1094.  
  1095.  
  1096.  
  1097. <p>And when you think about it, if people already know how to use one platform, and have demonstrated a preference for doing so, it can be wasteful of their time (not to mention arrogant) to expect them to learn another platform, simply because that one bears your logo.</p>
  1098.  
  1099.  
  1100.  
  1101. <h2 class="wp-block-heading" id="h-intersecting-planes-of-simple-yet-powerful-ideas">Intersecting planes of simple yet powerful ideas</h2>
  1102.  
  1103.  
  1104.  
  1105. <p>Of course, there are valid reasons not to use corporate social networks. Just as there are valid reasons to only use open source or free software. Or to not eat animals. But those real issues are not the drivers of this particular story.&nbsp;</p>
  1106.  
  1107.  
  1108.  
  1109. <p>This particular story is about a smart friend slicing through a&nbsp;<a href="https://www.wikiwand.com/en/Gordian_Knot">Gordian Knot</a>&nbsp;(aka my convoluted mental model, constructed as a result of, and justification for, how I earned a living), and providing me with a life lesson whose wisdom I continue to hold close.<br><br>It’s a lesson that intersects with other moments of enlightenment, such as “Don’t tell people who they are or how they should feel; listen and believe when&nbsp;<em>they</em>&nbsp;tell&nbsp;<em>you</em>.”&nbsp;<em>Meet people where they are</em>. It’s a fundamental principle of good UX design. Like&nbsp;<em>pave the cowpaths</em>. Which is really the same thing. We take these ideas for granted, now.</p>
  1110.  
  1111.  
  1112.  
  1113. <p>But once, and not so long ago, there was a time. Not&nbsp;<a href="https://youtu.be/Os-jJuwgNkA?si=T7Z4L4tGOmaoTWLP&amp;t=76">one brief shining moment that was known as Camelot</a>. But a time when media was no longer one-to-many, and not yet many-to-many. A time when it was still possible for designers like me to think we knew best.&nbsp;</p>
  1114.  
  1115.  
  1116.  
  1117. <p>I’m glad a friend knew better.</p>
  1118.  
  1119.  
  1120.  
  1121. <h2 class="wp-block-heading" id="h-afterword">Afterword</h2>
  1122.  
  1123.  
  1124.  
  1125. <p>I started telling this story to explain why&nbsp;<a href="https://zeldman.com/2024/02/21/in-search-of-a-digital-town-square/">I find myself posting, sometimes redundantly, to multiple social networks</a>—including one that feels increasingly like Mordor.&nbsp;</p>
  1126.  
  1127.  
  1128.  
  1129. <p>I go to them—even the one that breaks my heart—because, in this moment, they are where the people are.&nbsp;</p>
  1130.  
  1131.  
  1132.  
  1133. <p>Of course, as often happens, when I begin to tell a story that I think is about one thing, I discover that it’s about something else entirely.</p>
  1134. <p>The post <a href="https://zeldman.com/2024/03/02/where-the-people-are/">“Where the people are”</a> appeared first on <a href="https://zeldman.com">Zeldman on Web and Interaction Design</a>.</p>
  1135. ]]></content:encoded>
  1137. <wfw:commentRss>https://zeldman.com/2024/03/02/where-the-people-are/feed/</wfw:commentRss>
  1138. <slash:comments>8</slash:comments>
  1141. <post-id xmlns="com-wordpress:feed-additions:1">17741</post-id> </item>
  1142. <item>
  1143. <title>R.I.Pete</title>
  1144. <link>https://zeldman.com/2024/02/29/r-i-pete/</link>
  1145. <comments>https://zeldman.com/2024/02/29/r-i-pete/#comments</comments>
  1147. <dc:creator><![CDATA[L. Jeffrey Zeldman]]></dc:creator>
  1148. <pubDate>Thu, 29 Feb 2024 13:31:35 +0000</pubDate>
  1149. <category><![CDATA[family]]></category>
  1150. <category><![CDATA[glamorous]]></category>
  1151. <category><![CDATA[Pete Zeldman]]></category>
  1152. <guid isPermaLink="false">https://zeldman.com/?p=17734</guid>
  1153.  
  1154. <description><![CDATA[<p>It’s a year and one day since you died. At times, I feel your presence. I listen to your music every day. I miss you.</p>
  1155. <p>The post <a href="https://zeldman.com/2024/02/29/r-i-pete/">R.I.Pete</a> appeared first on <a href="https://zeldman.com">Zeldman on Web and Interaction Design</a>.</p>
  1156. ]]></description>
  1157. <content:encoded><![CDATA[
  1158. <p>It’s a year and one day since you died. At times, I feel your presence. I listen to your music every day. I miss you. </p>
  1159. <p>The post <a href="https://zeldman.com/2024/02/29/r-i-pete/">R.I.Pete</a> appeared first on <a href="https://zeldman.com">Zeldman on Web and Interaction Design</a>.</p>
  1160. ]]></content:encoded>
  1162. <wfw:commentRss>https://zeldman.com/2024/02/29/r-i-pete/feed/</wfw:commentRss>
  1163. <slash:comments>1</slash:comments>
  1166. <post-id xmlns="com-wordpress:feed-additions:1">17734</post-id> </item>
  1167. <item>
  1168. <title>Just add water.</title>
  1169. <link>https://zeldman.com/2024/02/28/just-add-water/</link>
  1170. <comments>https://zeldman.com/2024/02/28/just-add-water/#respond</comments>
  1172. <dc:creator><![CDATA[L. Jeffrey Zeldman]]></dc:creator>
  1173. <pubDate>Thu, 29 Feb 2024 01:52:27 +0000</pubDate>
  1174. <category><![CDATA["Found Objects"]]></category>
  1175. <category><![CDATA[Acclaim]]></category>
  1176. <category><![CDATA[Adobe]]></category>
  1177. <category><![CDATA[Apple]]></category>
  1178. <category><![CDATA[Applications]]></category>
  1179. <category><![CDATA[apps]]></category>
  1180. <category><![CDATA[art direction]]></category>
  1181. <category><![CDATA[Authoring]]></category>
  1182. <category><![CDATA[content]]></category>
  1183. <category><![CDATA[copyright]]></category>
  1184. <category><![CDATA[creativity]]></category>
  1185. <category><![CDATA[Culture]]></category>
  1186. <category><![CDATA[democracy]]></category>
  1187. <category><![CDATA[Design]]></category>
  1188. <category><![CDATA[Free Advice]]></category>
  1189. <category><![CDATA[Ideas]]></category>
  1190. <category><![CDATA[Nonsense]]></category>
  1191. <category><![CDATA[social media]]></category>
  1192. <category><![CDATA[stealing]]></category>
  1193. <category><![CDATA[theft]]></category>
  1194. <category><![CDATA[type]]></category>
  1195. <category><![CDATA[Typography]]></category>
  1196. <category><![CDATA[confederacy]]></category>
  1197. <category><![CDATA[congress]]></category>
  1198. <category><![CDATA[republicans]]></category>
  1199. <category><![CDATA[succession]]></category>
  1200. <guid isPermaLink="false">https://zeldman.com/?p=17729</guid>
  1201.  
  1202. <description><![CDATA[<p>Quick, before everyone else thinks of it. Set the word “SUCCESSION” in Engravers Gothic and export it to a transparent PNG. Download photos of confederate general Mitch McConnell and Republican Johns Thune (R-S.D.), Cornyn (R-Texas), and Barrasso (R-Wyo.). Grab and burn Nicholas Britell’s main title theme from Succession. Import all files into Final Cut Pro [&#8230;]</p>
  1203. <p>The post <a href="https://zeldman.com/2024/02/28/just-add-water/">Just add water.</a> appeared first on <a href="https://zeldman.com">Zeldman on Web and Interaction Design</a>.</p>
  1204. ]]></description>
  1205. <content:encoded><![CDATA[
  1206. <p>Quick, before everyone else thinks of it. Set the word “<strong>SUCCESSION</strong>” in <a href="https://fontsinuse.com/typefaces/5509/engravers-gothic">Engravers Gothic</a> and export it to a transparent PNG. Download photos of confederate general Mitch McConnell and Republican Johns Thune (R-S.D.), Cornyn (R-Texas), and Barrasso (R-Wyo.). Grab and burn <a href="https://www.nicholasbritell.com/">Nicholas Britell</a>’s <a href="https://open.spotify.com/track/0bSHwuTOZVJUXWT03H9oD2?si=7a22069a26e74163">main title theme from Succession</a>. Import all files into <a href="https://www.apple.com/final-cut-pro/">Final Cut Pro</a> or <a href="https://www.adobe.com/products/aftereffects.html">Adobe After Effects</a>. Add dissolves, fades, and film scratch overlays. Export. Upload to YouTube or Vimeo. Embed and amplify via all 500 social media networks. Sit back, relax, and bask in your 15 seconds of glory.</p>
  1207.  
  1208.  
  1209.  
  1210. <p></p>
  1211.  
  1212.  
  1213.  
  1214. <p class="has-small-font-size">“Succession” is copyright HBO. Mitch McConnell is a wholly owned subsidiary of the NRA.  </p>
  1215. <p>The post <a href="https://zeldman.com/2024/02/28/just-add-water/">Just add water.</a> appeared first on <a href="https://zeldman.com">Zeldman on Web and Interaction Design</a>.</p>
  1216. ]]></content:encoded>
  1218. <wfw:commentRss>https://zeldman.com/2024/02/28/just-add-water/feed/</wfw:commentRss>
  1219. <slash:comments>0</slash:comments>
  1222. <post-id xmlns="com-wordpress:feed-additions:1">17729</post-id> </item>
  1223. <item>
  1224. <title>Get it right.</title>
  1225. <link>https://zeldman.com/2024/02/27/get-it-right/</link>
  1226. <comments>https://zeldman.com/2024/02/27/get-it-right/#comments</comments>
  1228. <dc:creator><![CDATA[L. Jeffrey Zeldman]]></dc:creator>
  1229. <pubDate>Tue, 27 Feb 2024 12:53:08 +0000</pubDate>
  1230. <category><![CDATA[Advocacy]]></category>
  1231. <category><![CDATA[Announcements]]></category>
  1232. <category><![CDATA[arts]]></category>
  1233. <category><![CDATA[Best practices]]></category>
  1234. <category><![CDATA[bugs]]></category>
  1235. <category><![CDATA[content]]></category>
  1236. <category><![CDATA[Content First]]></category>
  1237. <category><![CDATA[editorial]]></category>
  1238. <category><![CDATA[Education]]></category>
  1239. <category><![CDATA[engagement]]></category>
  1240. <category><![CDATA[Ideas]]></category>
  1241. <category><![CDATA[industry]]></category>
  1242. <category><![CDATA[Microblogging]]></category>
  1243. <category><![CDATA[Off My Lawn!]]></category>
  1244. <category><![CDATA[Press]]></category>
  1245. <category><![CDATA[Publications]]></category>
  1246. <category><![CDATA[Publisher's Note]]></category>
  1247. <category><![CDATA[Publishing]]></category>
  1248. <category><![CDATA[reportage]]></category>
  1249. <category><![CDATA[Reporting]]></category>
  1250. <category><![CDATA[Responsibility]]></category>
  1251. <category><![CDATA[Standards]]></category>
  1252. <category><![CDATA[Wit and Wisdom]]></category>
  1253. <category><![CDATA[Working]]></category>
  1254. <category><![CDATA[writing]]></category>
  1255. <guid isPermaLink="false">https://zeldman.com/?p=17713</guid>
  1256.  
  1257. <description><![CDATA[<p>“Led” is the past tense of “lead.” L.E.D. Not L.E.A.D. Example: “Fran, who leads the group, led the meeting.” When professional publications get the small stuff wrong, it makes us less trusting about the big stuff. Trust in media is already at an all-time low. Don’t alienate liberal arts majors and obsessive compulsives. We may [&#8230;]</p>
  1258. <p>The post <a href="https://zeldman.com/2024/02/27/get-it-right/">Get it right.</a> appeared first on <a href="https://zeldman.com">Zeldman on Web and Interaction Design</a>.</p>
  1259. ]]></description>
  1260. <content:encoded><![CDATA[
  1261. <p>“Led” is the past tense of “lead.”</p>
  1262.  
  1263.  
  1264.  
  1265. <p>L.E.D. Not L.E.A.D.</p>
  1266.  
  1267.  
  1268.  
  1269. <p>Example: “Fran, who leads the group, led the meeting.”</p>
  1270.  
  1271.  
  1272.  
  1273. <p>When professional publications get the small stuff wrong, it makes us less trusting about the big stuff. Trust in media is already at an all-time low. Don’t alienate liberal arts majors and obsessive compulsives. We may be the last readers standing.</p>
  1274. <p>The post <a href="https://zeldman.com/2024/02/27/get-it-right/">Get it right.</a> appeared first on <a href="https://zeldman.com">Zeldman on Web and Interaction Design</a>.</p>
  1275. ]]></content:encoded>
  1277. <wfw:commentRss>https://zeldman.com/2024/02/27/get-it-right/feed/</wfw:commentRss>
  1278. <slash:comments>2</slash:comments>
  1281. <post-id xmlns="com-wordpress:feed-additions:1">17713</post-id> </item>
  1282. <item>
  1283. <title>In search of a digital town square</title>
  1284. <link>https://zeldman.com/2024/02/21/in-search-of-a-digital-town-square/</link>
  1285. <comments>https://zeldman.com/2024/02/21/in-search-of-a-digital-town-square/#comments</comments>
  1287. <dc:creator><![CDATA[L. Jeffrey Zeldman]]></dc:creator>
  1288. <pubDate>Wed, 21 Feb 2024 14:18:39 +0000</pubDate>
  1289. <category><![CDATA["Digital Curation"]]></category>
  1290. <category><![CDATA[Advocacy]]></category>
  1291. <category><![CDATA[Applications]]></category>
  1292. <category><![CDATA[apps]]></category>
  1293. <category><![CDATA[automattic]]></category>
  1294. <category><![CDATA[Blogroll]]></category>
  1295. <category><![CDATA[Blogs and Blogging]]></category>
  1296. <category><![CDATA[Brands]]></category>
  1297. <category><![CDATA[Community]]></category>
  1298. <category><![CDATA[content]]></category>
  1299. <category><![CDATA[ethics]]></category>
  1300. <category><![CDATA[glamorous]]></category>
  1301. <category><![CDATA[Ideas]]></category>
  1302. <category><![CDATA[Indieweb]]></category>
  1303. <category><![CDATA[industry]]></category>
  1304. <category><![CDATA[interface]]></category>
  1305. <category><![CDATA[links]]></category>
  1306. <category><![CDATA[Microauthoring]]></category>
  1307. <category><![CDATA[Microblogging]]></category>
  1308. <category><![CDATA[Micropublishing]]></category>
  1309. <category><![CDATA[Networks]]></category>
  1310. <category><![CDATA[Off My Lawn!]]></category>
  1311. <category><![CDATA[Own your content]]></category>
  1312. <category><![CDATA[Platforms]]></category>
  1313. <category><![CDATA[Publications]]></category>
  1314. <category><![CDATA[Publishing]]></category>
  1315. <category><![CDATA[Rants]]></category>
  1316. <category><![CDATA[social media]]></category>
  1317. <category><![CDATA[social networking]]></category>
  1318. <category><![CDATA[software]]></category>
  1319. <category><![CDATA[State of the Web]]></category>
  1320. <category><![CDATA[The Essentials]]></category>
  1321. <category><![CDATA[twitter]]></category>
  1322. <category><![CDATA[Usability]]></category>
  1323. <category><![CDATA[User Experience]]></category>
  1324. <category><![CDATA[UX]]></category>
  1325. <category><![CDATA[Web Design History]]></category>
  1326. <category><![CDATA[Websites]]></category>
  1327. <category><![CDATA[Weird]]></category>
  1328. <category><![CDATA[writing]]></category>
  1329. <guid isPermaLink="false">https://zeldman.com/?p=17685</guid>
  1330.  
  1331. <description><![CDATA[<p>Ever since an infantile fascist billionaire (hereafter, the IFB) decided to turn Twitter over to the racially hostile anti-science set, folks who previously used that network daily to discuss and amplify topics they cared about have either given up on the very premise of a shared digital commons, continued to post to Twitter while holding [&#8230;]</p>
  1332. <p>The post <a href="https://zeldman.com/2024/02/21/in-search-of-a-digital-town-square/">In search of a digital town square</a> appeared first on <a href="https://zeldman.com">Zeldman on Web and Interaction Design</a>.</p>
  1333. ]]></description>
  1334. <content:encoded><![CDATA[
  1335. <p class="has-drop-cap">Ever since an infantile fascist billionaire (hereafter, the IFB) decided to turn Twitter over to the racially hostile anti-science set, folks who previously used that network daily to discuss and amplify topics they cared about have either given up on the very premise of a shared digital commons, continued to post to Twitter while holding their noses, or sought a new digital place to call their own. This post is for the seekers, to compare notes.&nbsp;</p>
  1336.  
  1337.  
  1338.  
  1339. <p>These are my <em>personal</em> observations; your views may differ (and that’s more than okay). In this quick survey, I’m omitting specialty platforms like <a href="https://post.tribel.com/public/posts/1873fc30-69a8-11ed-bb22-b76b5a021845">Tribel</a>, <a href="https://post.news/feed">Post</a>, and <a href="https://substack.com/">Substack</a>. Feel free to comment, if you like.</p>
  1340.  
  1341.  
  1342.  
  1343. <h2 class="wp-block-heading" id="h-the-platforms">The platforms</h2>
  1344.  
  1345.  
  1346.  
  1347. <p><a href="https://bsky.app/profile/zeldman.bsky.social"><strong>BlueSky</strong></a>: The most beautifully elegant web interface. Also the best features (other than omission of hashtags). What Twitter should have become. I joined late—Jack didn’t invite me, likely a sign that I was no longer industrially relevant. I have few followers there, and my posts so far get little traction, but that could change. It’s so pretty (and the few friends that use it matter so much to me) that I keep using it, and I reserve judgement as to its future potential. <a href="https://bsky.app/profile/zeldman.bsky.social">https://bsky.app/profile/zeldman.bsky.social</a></p>
  1348.  
  1349.  
  1350.  
  1351. <p><a href="https://www.threads.net/@zeldman"><strong>Threads</strong></a>: Currently my primary alternative to Twitter, and the only place besides Twitter where my posts get at least some response. Not as visually refined as BlueSky, and with a curiously restricted single-hashtag-only policy. Although this editorial decision helps focus the mind, and likely also cuts down on spam, it interferes with amplifying multidimensional posts. But I digress.</p>
  1352.  
  1353.  
  1354.  
  1355. <p>Rough edges and restrictive tagging aside, Threads feels like the place that’s likeliest to inherit the mantle of default town square—if <em>any</em> social platform can do that in these new times, that is.</p>
  1356.  
  1357.  
  1358.  
  1359. <p>Threads got its huge jump start because, while the IFB was busy finding new ways to make Twitter less useful and more dangerous, Meta leveraged its huge installed Instagram base to give users a more or less instant social network hookup. If it’s easy, and comes with a built-in network of people I already follow, it wins—at least initially. </p>
  1360.  
  1361.  
  1362.  
  1363. <p>Meta may also blow their opportunity if they pursue misguided policies, such as impeding (by algorithmic fiat) “political speech” when democracies hang in the balance, regional wars threaten to become world wars, and the climate crisis is approaching a point of no return. <a href="https://www.threads.net/@zeldman">https://www.threads.net/@zeldman</a></p>
  1364.  
  1365.  
  1366.  
  1367. <p><a href="https://front-end.social/@zeldman"><strong>Mastodon</strong></a>: How do you decentralize a digital town square? Provide universal social connection without locking in participants? Mastodon (and federation generally) are an attempt to do those things. </p>
  1368.  
  1369.  
  1370.  
  1371. <p>These are important and noble goals, but Mastodon (and federation generally) are a long shot at replacing a primary walled garden like Twitter because they require a fair degree of geekery to set up, and the price tag of mass acceptance is ease of setup. (Compare Threads—easy set-up, built-in friends and followers if you already use Instagram—versus the learning curve with Mastodon.) <br><br>If BlueSky is MacOS and Threads is Windows, Mastodon is Linux: a great choice for techies, but likely too steep a hill for Ma and Pa Normie. A techie friend invited me to join, and I write there frequently, but, for whatever it’s worth, my Mastodon posts get very little in the way of responses. It is, nonetheless, a highly effective network for most who use it. <a href="https://front-end.social/@zeldman">https://front-end.social/@zeldman</a></p>
  1372.  
  1373.  
  1374.  
  1375. <p><a href="https://apartness.tumblr.com/"><strong>Tumblr</strong></a>: A bit o’ the OG weird wacky wonderful web, and a special place for nonconformist creative types. By its nature, and the nature of its fiercely loyal users, it is a cult jam. I was an early and enthusiastic Tumblr fan, but it was never my main axe, probably because, since the dawn of time itself, I have had <a href="http://zeldman.com">zeldman.com</a>. <br><br>For a while, when the IFB first started wrecking Twitter, an uptick in Tumblr usage suggested that the funky old network just might take over as the world’s town hall, but this hope was unrealistic, as Tumblr was never about being for everybody, and <em>Tumblristas</em> are mostly happy keeping the platform a home for self-selecting freaks, queers, and creatives. <br><br>I’ll note that Tumblr is part of the <a href="https://automattic.com/">Automattic</a> family, and I work at Automattic (just celebrated my fifth anniversary there!), but my opinions here are mine alone. BTW—in nearly 30 years of blogging, that’s the first time I’ve used that phrase. <a href="https://apartness.tumblr.com">https://apartness.tumblr.com</a></p>
  1376.  
  1377.  
  1378.  
  1379. <p><a href="https://www.linkedin.com/in/zeldman/"><strong>LinkedIn</strong></a>: A comparatively safe social network with a huge network built up over years, hence a great place to share work-related news and ideas. </p>
  1380.  
  1381.  
  1382.  
  1383. <p>Some early Twitter adopters of my acquaintance—especially those who mainly write about work topics like UX—have made LinkedIn their primary social home. For most working folks, it is undoubtedly a place to post and amplify at least some of the content that matters to you. OTOH, it’s not a place where I’d share deep takes on CSS (that’s probably Mastodon), cosplay (Tumblr), or personal true confessions (one’s blog, Threads, Twitter before the IFB took over). <a href="https://www.linkedin.com/in/zeldman">https://www.linkedin.com/in/zeldman</a></p>
  1384.  
  1385.  
  1386.  
  1387. <p><a href="https://twitter.com/zeldman"><strong>Twitter itself</strong></a>: During its heyday, before the IFB, and when it was the only game in town, I loved going there to see what clever things my smartest friends were saying, post my own <em>bon mots</em>, and promote content that mattered to me. <br><br>I’ll limit my comments on Twitter’s current state to noting that I still post there, from stubbornness as well as habit, and primarily in the (increasingly forlorn) hope that the IFB will eventually tire of his toy, or of the ceaseless financial hemorrhage, and go away, leaving the site to rebirth itself as an open source project or under the care of new, non-fascist owners. <br><br>Though the algorithm punishes my posts, and though I’m continually appalled by the MAGA posts, Russian disinformation, racist/ misogynist/ anti-semitic spew, and Trumpian ego of the current owner, I shall, at least for now, continue to defend my tiny turf there.</p>
  1388.  
  1389.  
  1390.  
  1391. <figure class="wp-block-embed is-type-rich is-provider-twitter wp-block-embed-twitter"><div class="wp-block-embed__wrapper">
  1392. <a class="twitter-timeline" data-width="580" data-height="870" data-dnt="true" href="https://twitter.com/zeldman?ref_src=twsrc%5Etfw">Tweets by zeldman</a><script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
  1393. </div></figure>
  1394.  
  1395.  
  1396.  
  1397. <div class="wp-block-comments"><h2 id="comments" class="wp-block-comments-title has-medium-font-size">7 responses to &#8220;In search of a digital town square&#8221;</h2>
  1398.  
  1399. <ol class="wp-block-comment-template"><li id="comment-4" class="comment byuser comment-author-admin bypostauthor even thread-even depth-1">
  1400.  
  1401. <div class="wp-block-columns is-layout-flex wp-container-core-columns-is-layout-1 wp-block-columns-is-layout-flex">
  1402. <div class="wp-block-column is-layout-flow wp-block-column-is-layout-flow" style="flex-basis:40px"><div class="wp-block-avatar"><img alt='L. Jeffrey Zeldman Avatar' src='https://secure.gravatar.com/avatar/350a70e175305fac28923d0622c87080?s=40&#038;d=robohash&#038;r=pg' srcset='https://secure.gravatar.com/avatar/350a70e175305fac28923d0622c87080?s=80&#038;d=robohash&#038;r=pg 2x' class='avatar avatar-40 photo wp-block-avatar__image' height='40' width='40'  style="border-radius:20px;" onerror="this.onerror=null;this.src='https://zeldman.com/wp-content/plugins/webmention/assets/img/mm.jpg';this.srcset='https://zeldman.com/wp-content/plugins/webmention/assets/img/mm.jpg';"/></div></div>
  1403.  
  1404.  
  1405.  
  1406. <div class="wp-block-column is-layout-flow wp-block-column-is-layout-flow"><div class="wp-block-comment-author-name has-small-font-size"><a rel="external nofollow ugc" href="https://zeldman.com/" target="_self" >L. Jeffrey Zeldman</a></div>
  1407.  
  1408.  
  1409. <div class="wp-block-group is-layout-flex wp-block-group-is-layout-flex" style="margin-top:0px;margin-bottom:0px"><div class="wp-block-comment-date has-small-font-size"><time datetime="2024-02-21T11:34:27-05:00"><a href="https://zeldman.com/2024/02/21/in-search-of-a-digital-town-square/comment-page-1/#comment-4">21 February 2024</a></time></div>
  1410.  
  1411. </div>
  1412.  
  1413.  
  1414. <div class="wp-block-comment-content"><p>Psst. Comments are back. This is a test.</p>
  1415. </div>
  1416.  
  1417. <div class="wp-block-comment-reply-link has-small-font-size"><a rel='nofollow' class='do-not-scroll comment-reply-link' href='#comment-4' data-commentid="4" data-postid="17685" data-belowelement="comment-4" data-respondelement="respond" data-replyto="Reply to L. Jeffrey Zeldman" aria-label='Reply to L. Jeffrey Zeldman'>Reply</a></div></div>
  1418. </div>
  1419.  
  1420. </li><li id="comment-8" class="comment odd alt thread-odd thread-alt depth-1">
  1421.  
  1422. <div class="wp-block-columns is-layout-flex wp-container-core-columns-is-layout-2 wp-block-columns-is-layout-flex">
  1423. <div class="wp-block-column is-layout-flow wp-block-column-is-layout-flow" style="flex-basis:40px"><div class="wp-block-avatar"><img alt='dusoft Avatar' src='https://secure.gravatar.com/avatar/37e4db1133d65e5bf5d3b7144eea3894?s=40&#038;d=robohash&#038;r=pg' srcset='https://secure.gravatar.com/avatar/37e4db1133d65e5bf5d3b7144eea3894?s=80&#038;d=robohash&#038;r=pg 2x' class='avatar avatar-40 photo wp-block-avatar__image' height='40' width='40'  style="border-radius:20px;" onerror="this.onerror=null;this.src='https://zeldman.com/wp-content/plugins/webmention/assets/img/mm.jpg';this.srcset='https://zeldman.com/wp-content/plugins/webmention/assets/img/mm.jpg';"/></div></div>
  1424.  
  1425.  
  1426.  
  1427. <div class="wp-block-column is-layout-flow wp-block-column-is-layout-flow"><div class="wp-block-comment-author-name has-small-font-size"><a rel="external nofollow ugc" href="https://ambience.sk/" target="_self" >dusoft</a></div>
  1428.  
  1429.  
  1430. <div class="wp-block-group is-layout-flex wp-block-group-is-layout-flex" style="margin-top:0px;margin-bottom:0px"><div class="wp-block-comment-date has-small-font-size"><time datetime="2024-02-28T04:54:46-05:00"><a href="https://zeldman.com/2024/02/21/in-search-of-a-digital-town-square/comment-page-1/#comment-8">28 February 2024</a></time></div>
  1431.  
  1432. </div>
  1433.  
  1434.  
  1435. <div class="wp-block-comment-content"><p>I follow you on Mastodon and even when usually don&#8217;t respond to bunch of posts, I can still appreciate people being there. Since I use RSS, I get to read your posts that way usually coming to your website.</p>
  1436. </div>
  1437.  
  1438. <div class="wp-block-comment-reply-link has-small-font-size"><a rel='nofollow' class='do-not-scroll comment-reply-link' href='#comment-8' data-commentid="8" data-postid="17685" data-belowelement="comment-8" data-respondelement="respond" data-replyto="Reply to dusoft" aria-label='Reply to dusoft'>Reply</a></div></div>
  1439. </div>
  1440.  
  1441. </li><li id="comment-11" class="mention even thread-even depth-1">
  1442.  
  1443. <div class="wp-block-columns is-layout-flex wp-container-core-columns-is-layout-3 wp-block-columns-is-layout-flex">
  1444. <div class="wp-block-column is-layout-flow wp-block-column-is-layout-flow" style="flex-basis:40px"><div class="wp-block-avatar"><img alt='Zeldman on Web and Interaction Design Avatar' src='https://secure.gravatar.com/avatar/?s=40&#038;d=robohash&#038;r=pg' srcset='https://secure.gravatar.com/avatar/?s=80&#038;d=robohash&#038;r=pg 2x' class='avatar avatar-40 photo avatar-default wp-block-avatar__image' height='40' width='40'  style="border-radius:20px;" onerror="this.onerror=null;this.src='https://zeldman.com/wp-content/plugins/webmention/assets/img/mm.jpg';this.srcset='https://zeldman.com/wp-content/plugins/webmention/assets/img/mm.jpg';"/></div></div>
  1445.  
  1446.  
  1447.  
  1448. <div class="wp-block-column is-layout-flow wp-block-column-is-layout-flow"><div class="wp-block-comment-author-name has-small-font-size"><a rel="external nofollow ugc" href="https://zeldman.com/author/admin/" target="_self" >Zeldman on Web and Interaction Design</a></div>
  1449.  
  1450.  
  1451. <div class="wp-block-group is-layout-flex wp-block-group-is-layout-flex" style="margin-top:0px;margin-bottom:0px"><div class="wp-block-comment-date has-small-font-size"><time datetime="2024-03-02T09:05:14-05:00"><a href="https://zeldman.com/2024/03/02/where-the-people-are/">2 March 2024</a></time></div>
  1452.  
  1453. </div>
  1454.  
  1455.  
  1456. <div class="wp-block-comment-content"><p>It’s nearly twenty years ago, now, children. Facebook had only recently burst the bounds of Harvard Yard. Twitter had just slipped the bonds of the&hellip;</p>
  1457. </div>
  1458.  
  1459. <div class="wp-block-comment-reply-link has-small-font-size"><a rel='nofollow' class='do-not-scroll comment-reply-link' href='#comment-11' data-commentid="11" data-postid="17685" data-belowelement="comment-11" data-respondelement="respond" data-replyto="Reply to Zeldman on Web and Interaction Design" aria-label='Reply to Zeldman on Web and Interaction Design'>Reply</a></div></div>
  1460. </div>
  1461.  
  1462. </li><li id="comment-16" class="pingback odd alt thread-odd thread-alt depth-1">
  1463.  
  1464. <div class="wp-block-columns is-layout-flex wp-container-core-columns-is-layout-4 wp-block-columns-is-layout-flex">
  1465. <div class="wp-block-column is-layout-flow wp-block-column-is-layout-flow" style="flex-basis:40px"><div class="wp-block-avatar">  </div></div>
  1466.  
  1467.  
  1468.  
  1469. <div class="wp-block-column is-layout-flow wp-block-column-is-layout-flow"><div class="wp-block-comment-author-name has-small-font-size"><a rel="external nofollow ugc" href="https://koolinus.net/blog/2024/03/03/letture-suggerite-del-3-marzo-2024/" target="_self" >letture suggerite del 3 marzo 2024 &raquo; kOoLiNuS ☞ il blog</a></div>
  1470.  
  1471.  
  1472. <div class="wp-block-group is-layout-flex wp-block-group-is-layout-flex" style="margin-top:0px;margin-bottom:0px"><div class="wp-block-comment-date has-small-font-size"><time datetime="2024-03-03T10:13:51-05:00"><a href="https://zeldman.com/2024/02/21/in-search-of-a-digital-town-square/comment-page-1/#comment-16">3 March 2024</a></time></div>
  1473.  
  1474. </div>
  1475.  
  1476.  
  1477. <div class="wp-block-comment-content"><p>[&#8230;] In search of a digital town square – L. Jeffrey Zeldman, non l’ultimo dei fessi sul web, cerca di fare il punto sullo stato dell’arte del self publishing oggi; [&#8230;]</p>
  1478. </div>
  1479.  
  1480. <div class="wp-block-comment-reply-link has-small-font-size"><a rel='nofollow' class='do-not-scroll comment-reply-link' href='#comment-16' data-commentid="16" data-postid="17685" data-belowelement="comment-16" data-respondelement="respond" data-replyto="Reply to letture suggerite del 3 marzo 2024 &raquo; kOoLiNuS ☞ il blog" aria-label='Reply to letture suggerite del 3 marzo 2024 &raquo; kOoLiNuS ☞ il blog'>Reply</a></div></div>
  1481. </div>
  1482.  
  1483. </li><li id="comment-17" class="pingback even thread-even depth-1">
  1484.  
  1485. <div class="wp-block-columns is-layout-flex wp-container-core-columns-is-layout-5 wp-block-columns-is-layout-flex">
  1486. <div class="wp-block-column is-layout-flow wp-block-column-is-layout-flow" style="flex-basis:40px"><div class="wp-block-avatar">  </div></div>
  1487.  
  1488.  
  1489.  
  1490. <div class="wp-block-column is-layout-flow wp-block-column-is-layout-flow"><div class="wp-block-comment-author-name has-small-font-size"><a rel="external nofollow ugc" href="https://koolinus.wordpress.com/2024/03/03/suggested-reads-for-march-3-2024/" target="_self" >suggested reads for March 3, 2024 &#8211; /home/kOoLiNuS</a></div>
  1491.  
  1492.  
  1493. <div class="wp-block-group is-layout-flex wp-block-group-is-layout-flex" style="margin-top:0px;margin-bottom:0px"><div class="wp-block-comment-date has-small-font-size"><time datetime="2024-03-03T10:20:08-05:00"><a href="https://zeldman.com/2024/02/21/in-search-of-a-digital-town-square/comment-page-1/#comment-17">3 March 2024</a></time></div>
  1494.  
  1495. </div>
  1496.  
  1497.  
  1498. <div class="wp-block-comment-content"><p>[&#8230;] In search of a digital town square – L. Jeffrey Zeldman, talks about the state of the art on mantaining a presence on the web today, with the available tools. [&#8230;]</p>
  1499. </div>
  1500.  
  1501. <div class="wp-block-comment-reply-link has-small-font-size"><a rel='nofollow' class='do-not-scroll comment-reply-link' href='#comment-17' data-commentid="17" data-postid="17685" data-belowelement="comment-17" data-respondelement="respond" data-replyto="Reply to suggested reads for March 3, 2024 &#8211; /home/kOoLiNuS" aria-label='Reply to suggested reads for March 3, 2024 &#8211; /home/kOoLiNuS'>Reply</a></div></div>
  1502. </div>
  1503.  
  1504. </li><li id="comment-22" class="pingback odd alt thread-odd thread-alt depth-1">
  1505.  
  1506. <div class="wp-block-columns is-layout-flex wp-container-core-columns-is-layout-6 wp-block-columns-is-layout-flex">
  1507. <div class="wp-block-column is-layout-flow wp-block-column-is-layout-flow" style="flex-basis:40px"><div class="wp-block-avatar">  </div></div>
  1508.  
  1509.  
  1510.  
  1511. <div class="wp-block-column is-layout-flow wp-block-column-is-layout-flow"><div class="wp-block-comment-author-name has-small-font-size"><a rel="external nofollow ugc" href="https://ntdln.com/2024/03/04/weekly-links-02-26-03-03/" target="_self" >Weekly Links 02.26–03.03 &#8211; ntdln</a></div>
  1512.  
  1513.  
  1514. <div class="wp-block-group is-layout-flex wp-block-group-is-layout-flex" style="margin-top:0px;margin-bottom:0px"><div class="wp-block-comment-date has-small-font-size"><time datetime="2024-03-04T11:55:50-05:00"><a href="https://zeldman.com/2024/02/21/in-search-of-a-digital-town-square/comment-page-1/#comment-22">4 March 2024</a></time></div>
  1515.  
  1516. </div>
  1517.  
  1518.  
  1519. <div class="wp-block-comment-content"><p>[&#8230;] In search of a digital town square (Jeffrey Zeldman) [&#8230;]</p>
  1520. </div>
  1521.  
  1522. <div class="wp-block-comment-reply-link has-small-font-size"><a rel='nofollow' class='do-not-scroll comment-reply-link' href='#comment-22' data-commentid="22" data-postid="17685" data-belowelement="comment-22" data-respondelement="respond" data-replyto="Reply to Weekly Links 02.26–03.03 &#8211; ntdln" aria-label='Reply to Weekly Links 02.26–03.03 &#8211; ntdln'>Reply</a></div></div>
  1523. </div>
  1524.  
  1525. </li><li id="comment-59" class="mention even thread-even depth-1">
  1526.  
  1527. <div class="wp-block-columns is-layout-flex wp-container-core-columns-is-layout-7 wp-block-columns-is-layout-flex">
  1528. <div class="wp-block-column is-layout-flow wp-block-column-is-layout-flow" style="flex-basis:40px"><div class="wp-block-avatar"><img alt='Zeldman on Web and Interaction Design Avatar' src='https://secure.gravatar.com/avatar/?s=40&#038;d=robohash&#038;r=pg' srcset='https://secure.gravatar.com/avatar/?s=80&#038;d=robohash&#038;r=pg 2x' class='avatar avatar-40 photo avatar-default wp-block-avatar__image' height='40' width='40'  style="border-radius:20px;" onerror="this.onerror=null;this.src='https://zeldman.com/wp-content/plugins/webmention/assets/img/mm.jpg';this.srcset='https://zeldman.com/wp-content/plugins/webmention/assets/img/mm.jpg';"/></div></div>
  1529.  
  1530.  
  1531.  
  1532. <div class="wp-block-column is-layout-flow wp-block-column-is-layout-flow"><div class="wp-block-comment-author-name has-small-font-size"><a rel="external nofollow ugc" href="https://zeldman.com/author/admin/" target="_self" >Zeldman on Web and Interaction Design</a></div>
  1533.  
  1534.  
  1535. <div class="wp-block-group is-layout-flex wp-block-group-is-layout-flex" style="margin-top:0px;margin-bottom:0px"><div class="wp-block-comment-date has-small-font-size"><time datetime="2024-03-13T08:43:53-04:00"><a href="https://zeldman.com/2024/03/13/open-source-moderation/">13 March 2024</a></time></div>
  1536.  
  1537. </div>
  1538.  
  1539.  
  1540. <div class="wp-block-comment-content"><p>Bluesky introduces open-source, collaborative moderation for federated social media websites: Bluesky was created to put users and communities in control of their social spaces online.&hellip;</p>
  1541. </div>
  1542.  
  1543. <div class="wp-block-comment-reply-link has-small-font-size"><a rel='nofollow' class='do-not-scroll comment-reply-link' href='#comment-59' data-commentid="59" data-postid="17685" data-belowelement="comment-59" data-respondelement="respond" data-replyto="Reply to Zeldman on Web and Interaction Design" aria-label='Reply to Zeldman on Web and Interaction Design'>Reply</a></div></div>
  1544. </div>
  1545.  
  1546. </li></ol>
  1547.  
  1548.  
  1549.  
  1550.  
  1551. <div id="respond" class="comment-respond wp-block-post-comments-form">
  1552. <h3 id="reply-title" class="comment-reply-title">Got something to say?<small><a rel="nofollow" id="cancel-comment-reply-link" href="/feed/#respond" style="display:none;">Cancel reply</a></small></h3> <form id="commentform" class="comment-form">
  1553. <iframe
  1554. title="Comment Form"
  1555. src="https://jetpack.wordpress.com/jetpack-comment/?blogid=227043043&#038;postid=17685&#038;comment_registration=0&#038;require_name_email=1&#038;stc_enabled=0&#038;stb_enabled=1&#038;show_avatars=1&#038;avatar_default=robohash&#038;greeting=Got+something+to+say%3F&#038;jetpack_comments_nonce=53a13e0b94&#038;greeting_reply=Leave+a+Reply+to+%25s&#038;color_scheme=light&#038;lang=en_US&#038;jetpack_version=13.4-a.3&#038;show_cookie_consent=10&#038;has_cookie_consent=0&#038;is_current_user_subscribed=0&#038;token_key=%3Bnormal%3B&#038;sig=eb46fea11c00bf8a1a6a42773b368fe6312e2bb7#parent=https%3A%2F%2Fzeldman.com%2Ffeed%2F"
  1556. name="jetpack_remote_comment"
  1557. style="width:100%; height: 430px; border:0;"
  1558. class="jetpack_remote_comment"
  1559. id="jetpack_remote_comment"
  1560. sandbox="allow-same-origin allow-top-navigation allow-scripts allow-forms allow-popups"
  1561. >
  1562. </iframe>
  1563. <!--[if !IE]><!-->
  1564. <script>
  1565. document.addEventListener('DOMContentLoaded', function () {
  1566. var commentForms = document.getElementsByClassName('jetpack_remote_comment');
  1567. for (var i = 0; i < commentForms.length; i++) {
  1568. commentForms[i].allowTransparency = false;
  1569. commentForms[i].scrolling = 'no';
  1570. }
  1571. });
  1572. </script>
  1573. <!--<![endif]-->
  1574. </form>
  1575. </div>
  1576.  
  1578. <input type="hidden" name="comment_parent" id="comment_parent" value="" />
  1579.  
  1580. <form id="webmention-form" action="https://zeldman.com/wp-json/webmention/1.0/endpoint" method="post">
  1581. <p>
  1582. <label for="webmention-source">To respond on your own website, enter the URL of your response which should contain a link to this post's permalink URL. Your response will then appear (possibly after moderation) on this page. Want to update or remove your response? Update or delete your post and re-enter your post's URL again. (<a href="https://indieweb.org/webmention">Learn More</a>)</label>
  1583. </p>
  1584. <p>
  1585. <input id="webmention-source" type="url" autocomplete="url" required pattern="^https?:\/\/(.*)" name="source" placeholder="URL/Permalink of your article" />
  1586. </p>
  1587. <p>
  1588. <input id="webmention-submit" type="submit" name="submit" value="Ping me!" />
  1589. </p>
  1590. <input id="webmention-format" type="hidden" name="format" value="html" />
  1591. <input id="webmention-target" type="hidden" name="target" value="https://zeldman.com/2024/02/21/in-search-of-a-digital-town-square/" />
  1592. </form>
  1593. </div>
  1594. <p>The post <a href="https://zeldman.com/2024/02/21/in-search-of-a-digital-town-square/">In search of a digital town square</a> appeared first on <a href="https://zeldman.com">Zeldman on Web and Interaction Design</a>.</p>
  1595. ]]></content:encoded>
  1597. <wfw:commentRss>https://zeldman.com/2024/02/21/in-search-of-a-digital-town-square/feed/</wfw:commentRss>
  1598. <slash:comments>7</slash:comments>
  1601. <post-id xmlns="com-wordpress:feed-additions:1">17685</post-id> </item>
  1602. </channel>
  1603. </rss>

If you would like to create a banner that links to this page (i.e. this validation result), do the following:

  1. Download the "valid RSS" banner.

  2. Upload the image to your own server. (This step is important. Please do not link directly to the image on this server.)

  3. Add this HTML to your page (change the image src attribute if necessary):

If you would like to create a text link instead, here is the URL you can use:

http://www.feedvalidator.org/check.cgi?url=http%3A//www.zeldman.com/feed/zeldman.xml

Home · About · News · Docs · Terms

 
Copyright © 2002-9 Sam Ruby, Mark Pilgrim, Joseph Walton, and Phil Ringnalda