[Valid Atom 1.0] This is a valid Atom 1.0 feed.


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


  1. <?xml version="1.0" encoding="utf-8"?>
  2. <feed xmlns="">
  3. <title>Daring Fireball</title>
  4. <subtitle>By John Gruber</subtitle>
  5. <link rel="alternate" type="text/html" href="" />
  6. <link rel="self" type="application/atom+xml" href="" />
  7. <id></id>
  10. <updated>2018-06-18T18:54:16Z</updated><rights>Copyright © 2018, John Gruber</rights><entry>
  11. <title>Federico Viticci on Shortcuts in iOS 12</title>
  12. <link rel="alternate" type="text/html" href="" />
  13. <link rel="shorturl" type="text/html" href="" />
  14. <link rel="related" type="text/html" href="" />
  15. <id>,2018:/linked//6.34940</id>
  16. <published>2018-06-18T18:54:15Z</published>
  17. <updated>2018-06-18T18:54:16Z</updated>
  18. <author>
  19. <name>John Gruber</name>
  20. <uri></uri>
  21. </author>
  22. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  23. <p>Federico Viticci:</p>
  25. <blockquote>
  26.  <p>While it&#8217;s still too early to comment on the long-term impact of
  27. Shortcuts, I can at least attempt to understand the potential of
  28. this new technology. In this article, I&#8217;ll try to explain the
  29. differences between Siri shortcuts and the Shortcuts app, as well
  30. as answering some common questions about how much Shortcuts
  31. borrows from the original Workflow app.</p>
  32. </blockquote>
  34. <p>Apple has packed a lot of new features under that one word, <em>shortcuts</em>, in iOS 12.</p>
  36. <div>
  37. <a  title="Permanent link to ‘Federico Viticci on Shortcuts in iOS 12’"  href="">&nbsp;★&nbsp;</a>
  38. </div>
  40. ]]></content>
  41.  </entry><entry>
  42. <title>South Korean Carrier to Sell ‘New’ iPhone 3GS Units</title>
  43. <link rel="alternate" type="text/html" href="" />
  44. <link rel="shorturl" type="text/html" href="" />
  45. <link rel="related" type="text/html" href="" />
  46. <id>,2018:/linked//6.34939</id>
  47. <published>2018-06-18T18:42:58Z</published>
  48. <updated>2018-06-18T18:43:00Z</updated>
  49. <author>
  50. <name>John Gruber</name>
  51. <uri></uri>
  52. </author>
  53. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  54. <p>Gordon Gottsegen, reporting for CNet:</p>
  56. <blockquote>
  57.  <p>Even though the iPhone 3GS will be sold as &#8220;brand new,&#8221; don&#8217;t
  58. expect it to work the same as a recently released iPhone. The
  59. iPhone 3GS was discontinued back in 2012, and it only runs iOS
  60. 6. As a result, many apps (and even iMessages) won&#8217;t work on
  61. the phone.</p>
  63. <p>The iPhone predates Lightning cables, too, so you&#8217;ll be stuck
  64. using an old-school 30-pin connector.</p>
  66. <p>Still, SK Telink is selling the iPhone 3GS for only 44,000 won,
  67. which is equivalent to $40, £30 or AU$55. So this Apple
  68. blast-from-the-past could be yours for pretty cheap &#8212; if you&#8217;re
  69. in Korea.</p>
  70. </blockquote>
  72. <p>On the one hand, the 3GS is crazily outdated. On the other hand: $40!</p>
  74. <div>
  75. <a  title="Permanent link to ‘South Korean Carrier to Sell &#8216;New&#8217; iPhone 3GS Units’"  href="">&nbsp;★&nbsp;</a>
  76. </div>
  78. ]]></content>
  79.  </entry><entry>
  80. <title>Google to Fix Precise Location Data Leak in Google Home, Chromecast</title>
  81. <link rel="alternate" type="text/html" href="" />
  82. <link rel="shorturl" type="text/html" href="" />
  83. <link rel="related" type="text/html" href="" />
  84. <id>,2018:/linked//6.34938</id>
  85. <published>2018-06-18T17:55:43Z</published>
  86. <updated>2018-06-18T18:01:28Z</updated>
  87. <author>
  88. <name>John Gruber</name>
  89. <uri></uri>
  90. </author>
  91. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  92. <p>Brian Krebs:</p>
  94. <blockquote>
  95.  <p>Craig Young, a researcher with security firm Tripwire, said he
  96. discovered an authentication weakness that leaks incredibly
  97. accurate location information about users of both the smart
  98. speaker and home assistant Google Home, and Chromecast, a small
  99. electronic device that makes it simple to stream TV shows, movies
  100. and games to a digital television or monitor.</p>
  102. <p>Young said the attack works by asking the Google device for a list
  103. of nearby wireless networks and then sending that list to Google’s
  104. geolocation lookup services.</p>
  106. <p>“An attacker can be completely remote as long as they can get the
  107. victim to open a link while connected to the same Wi-Fi or wired
  108. network as a Google Chromecast or Home device,” Young told
  109. KrebsOnSecurity. “The only real limitation is that the link needs
  110. to remain open for about a minute before the attacker has a
  111. location. The attack content could be contained within malicious
  112. advertisements or even a tweet.”</p>
  113. </blockquote>
  115. <p>Young is getting location data accurate to within 10 meters from his exploit. All you have to do to be exposed is open a web page and leave it open for a minute. This is the common sense fear of this whole Internet of Things movement: that these devices we&#8217;re putting on our networks aren&#8217;t secure, even the ones from big companies like Google.</p>
  117. <p>(I would also argue that it&#8217;s wrong that JavaScript running on a web page is able to ping devices on your local network without any sort of prompt granting it such access.)</p>
  119. <div>
  120. <a  title="Permanent link to ‘Google to Fix Precise Location Data Leak in Google Home, Chromecast’"  href="">&nbsp;★&nbsp;</a>
  121. </div>
  123. ]]></content>
  124.  </entry><entry>
  125. <title>WhenWorks</title>
  126. <link rel="alternate" type="text/html" href="" />
  127. <link rel="shorturl" type="text/html" href="" />
  128. <link rel="related" type="text/html" href="" />
  129. <id>,2018:/linked//6.34937</id>
  130. <published>2018-06-18T17:37:50Z</published>
  131. <updated>2018-06-18T17:43:19Z</updated>
  132. <author>
  133. <name>John Gruber</name>
  134. <uri></uri>
  135. </author>
  136. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  137. <p>New iOS app and web service that makes it easy for people to book appointments with you. <a href="">From their blog announcement</a>, on what makes WhenWorks unique:</p>
  139. <blockquote>
  140.  <p>There are many competitive services in this space. What they all
  141. have in common is that they are purely web-based solutions. What
  142. makes WhenWorks unique is that it is a mobile app that integrates
  143. directly with the Calendar app on your iOS device, is far easier
  144. to configure and use, more secure, and always with you when you
  145. need it.</p>
  147. <p>WhenWorks supports all of the leading calendar services (iCloud,
  148. Google Calendar, Office 365 and but is particularly
  149. well-suited for those who use iCloud, due to its deep integration
  150. with the built-in Calendar on iOS.</p>
  151. </blockquote>
  153. <p>WhenWorks was founded by John Chaffee, of <a href="">BusyMac</a> and, back in the day, Now Up-to-Date fame, and he&#8217;s put together a really good team. The pricing is outstanding too: 14-day free trial, free-to-use for up to five appointments per month after that, and just $5/month for the pro account with no limits.</p>
  155. <p>It&#8217;s a really great app, and setting it up couldn&#8217;t be easier. Worth checking it out just to examine the UI and on-boarding process, and if you&#8217;re the sort of person who has a busy calendar packed with appointments, you&#8217;re nuts if you don&#8217;t try it.</p>
  157. <div>
  158. <a  title="Permanent link to ‘WhenWorks’"  href="">&nbsp;★&nbsp;</a>
  159. </div>
  161. ]]></content>
  162.  </entry><entry>
  163. <title>How Square Made Its Own iPad Replacement</title>
  164. <link rel="alternate" type="text/html" href="" />
  165. <link rel="shorturl" type="text/html" href="" />
  166. <link rel="related" type="text/html" href="" />
  167. <id>,2018:/linked//6.34936</id>
  168. <published>2018-06-18T17:14:10Z</published>
  169. <updated>2018-06-18T17:14:12Z</updated>
  170. <author>
  171. <name>John Gruber</name>
  172. <uri></uri>
  173. </author>
  174. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  175. <p>Lauren Goode, writing for Wired:</p>
  177. <blockquote>
  178.  <p>If you know the company Square, it&#8217;s probably because you&#8217;ve paid
  179. in a store using a Square “stand”, a dock that supports a tablet,
  180. or you&#8217;ve swiped your card through Square Reader, a smartphone
  181. dongle that processes payments. These products have a soothing,
  182. decidedly Apple-y aesthetic, from the simple dongle to the
  183. all-white stand that typically houses an iPad. But since late last
  184. year, Square has been quietly selling its own custom-made tablet,
  185. the Square Register, a $999, Android-based system. And the company
  186. has taken an obsessive approach to designing the product.</p>
  187. </blockquote>
  189. <p>There&#8217;s a local coffee place I like that has these, and they&#8217;re pretty neat. The two-screen design makes sense for a two-person interaction. Also, Square&#8217;s Apple Pay support is top-notch &#8212; in my experience Square&#8217;s Apple Pay readers are more accurate and work faster than the dinguses from their competition.</p>
  191. <div>
  192. <a  title="Permanent link to ‘How Square Made Its Own iPad Replacement’"  href="">&nbsp;★&nbsp;</a>
  193. </div>
  195. ]]></content>
  196.  </entry><entry>
  197. <link rel="alternate" type="text/html" href=";utm_source=daringfireball&amp;utm_campaign=kit&amp;utm_content=na&amp;utm_term=na" />
  198. <link rel="shorturl" href="" />
  199. <link rel="related" type="text/html" href="" />
  200. <id>,2018:/feeds/sponsors//11.34941</id>
  201. <author><name>Daring Fireball Department of Commerce</name></author>
  202. <published>2018-06-18T16:09:16-04:00</published>
  203. <updated>2018-06-18T16:09:17-04:00</updated>
  204. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  205. <p>Snap Kit lets developers integrate some of Snapchat’s best features like Bitmoji and Stories — and lets your community share their favorite moments from your app with their friends on Snapchat. All of this without compromising any private account data! Visit <a href=""></a> for documentation and more info.</p>
  207. <div>
  208. <a  title="Permanent link to ‘Snap Kit by Snapchat’"  href="">&nbsp;★&nbsp;</a>
  209. </div>
  211. ]]></content>
  212. <title>[Sponsor] Snap Kit by Snapchat</title></entry><entry>
  213. <title>Skillshare</title>
  214. <link rel="alternate" type="text/html" href="" />
  215. <link rel="shorturl" type="text/html" href="" />
  216. <link rel="related" type="text/html" href="" />
  217. <id>,2018:/linked//6.34935</id>
  218. <published>2018-06-17T18:00:17Z</published>
  219. <updated>2018-06-17T18:00:18Z</updated>
  220. <author>
  221. <name>John Gruber</name>
  222. <uri></uri>
  223. </author>
  224. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  225. <p>My thanks to Skillshare for sponsoring last week’s DF RSS feed. With over 4 million members and more than 20,000 classes, Skillshare is basically Netflix for online learning. Interested in web development or data science? How about UX design or SEO? Mobile photography, filmmaking, creative writing, even coffee brewing? Skillshare truly has it all.</p>
  227. <p>Skillshare&#8217;s production values and content quality are <em>so</em> much better than what you typically see on the web. High quality is obviously their first priority. Here&#8217;s a personal recommendation: &#8220;<a href="">Logo Design With Aaron Draplin</a>&#8221;. Yeah, that Aaron Draplin &#8212; cofounder of Field Notes and <a href="">designer/raconteur extraordinaire</a>. He&#8217;s one of my favorite designers in the world, a generous teacher, and fantastically compelling on camera. Get the free demo and watch Draplin&#8217;s course. (Draplin has <a href="">a bunch of great courses on Skillshare</a> already.)</p>
  229. <p>And for this week only, <a href="">Skillshare is offering the first 1,000 Daring Fireball readers <em>two free</em> months of Skillshare Premium</a>.</p>
  231. <div>
  232. <a  title="Permanent link to ‘Skillshare’"  href="">&nbsp;★&nbsp;</a>
  233. </div>
  235. ]]></content>
  236.  </entry><entry>
  237. <title>How Apple Can Fix 3D Touch</title>
  238. <link rel="alternate" type="text/html" href="" />
  239. <link rel="shorturl" type="text/html" href="" />
  240. <link rel="related" type="text/html" href="" />
  241. <id>,2018:/linked//6.34934</id>
  242. <published>2018-06-15T23:29:53Z</published>
  243. <updated>2018-06-15T23:29:54Z</updated>
  244. <author>
  245. <name>John Gruber</name>
  246. <uri></uri>
  247. </author>
  248. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  249. <p>Eliz Kilic:</p>
  251. <blockquote>
  252.  <p>It’s been almost 4 years since its first introduction, yet people
  253. don’t know/use 3D Touch. Why would they? Even tech-savvy users
  254. don’t know which buttons offer 3D touch. Let alone regular users.</p>
  256. <p>What would happen if we decide to make all links same color and
  257. style as the regular text? People would not know what to click on
  258. right? Why is 3D Touch be any different? We rely on our vision to
  259. decide actionability before anything else. If you can’t
  260. distinguish 3D Touchable buttons from those that are not, how are
  261. you supposed to know you can press on them?</p>
  262. </blockquote>
  264. <p>Total agreement from me on this. It&#8217;s baffling that there&#8217;s no visual indication of what can be 3D touched.</p>
  266. <div>
  267. <a  title="Permanent link to ‘How Apple Can Fix 3D Touch’"  href="">&nbsp;★&nbsp;</a>
  268. </div>
  270. ]]></content>
  271.  </entry><entry>
  272. <title>The Talk Show: ‘AirPower, What’s That?’</title>
  273. <link rel="alternate" type="text/html" href="" />
  274. <link rel="shorturl" type="text/html" href="" />
  275. <link rel="related" type="text/html" href="" />
  276. <id>,2018:/linked//6.34933</id>
  277. <published>2018-06-15T22:01:37Z</published>
  278. <updated>2018-06-15T22:01:38Z</updated>
  279. <author>
  280. <name>John Gruber</name>
  281. <uri></uri>
  282. </author>
  283. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  284. <p>Serenity Caldwell returns to the show for a post-WWDC wrap-up discussion. Topics include iOS 12, Memoji, Siri Shortcuts, Screen Time, Apple Books, MacOS 10.14 Mojave, dark mode, UIKit apps on the Mac, and more.</p>
  286. <p>Brought to you by these outstanding sponsors:</p>
  288. <ul>
  289. <li><a href="">Casper</a>: You can be sure of your purchase with Casper’s 100 night risk-free, sleep-on-it trial.</li>
  290. <li><a href="">Squarespace</a>: Make your next move. Visit and enter code <strong>talkshow</strong> for 10% off your first order.</li>
  291. <li><a href="">Tres Pontas</a>: Freshly-roasted coffee from a single farm in Brazil, shipped directly to you. Use code THETALKSHOW at checkout and save an extra 10 percent on any subscription.</li>
  292. </ul>
  294. <div>
  295. <a  title="Permanent link to ‘The Talk Show: &#8216;AirPower, What’s That?&#8217;’"  href="">&nbsp;★&nbsp;</a>
  296. </div>
  298. ]]></content>
  299.  </entry><entry>
  300. <title>Oprah, Apple. Apple, Oprah.</title>
  301. <link rel="alternate" type="text/html" href="" />
  302. <link rel="shorturl" type="text/html" href="" />
  303. <link rel="related" type="text/html" href="" />
  304. <id>,2018:/linked//6.34932</id>
  305. <published>2018-06-15T19:36:26Z</published>
  306. <updated>2018-06-15T21:56:38Z</updated>
  307. <author>
  308. <name>John Gruber</name>
  309. <uri></uri>
  310. </author>
  311. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  312. <p>Apple press release:</p>
  314. <blockquote>
  315.  <p>Apple today announced a unique, multi-year content partnership
  316. with Oprah Winfrey, the esteemed producer, actress, talk show
  317. host, philanthropist and CEO of OWN.</p>
  319. <p>Together, Winfrey and Apple will create original programs that
  320. embrace her incomparable ability to connect with audiences around
  321. the world.</p>
  323. <p>Winfrey’s projects will be released as part of a lineup of
  324. original content from Apple.</p>
  325. </blockquote>
  327. <p>Yet another sign that Apple is dead serious about original content.</p>
  329. <div>
  330. <a  title="Permanent link to ‘Oprah, Apple. Apple, Oprah.’"  href="">&nbsp;★&nbsp;</a>
  331. </div>
  333. ]]></content>
  334.  </entry><entry>
  335. <title>On the Sad State of Macintosh Hardware</title>
  336. <link rel="alternate" type="text/html" href="" />
  337. <link rel="shorturl" type="text/html" href="" />
  338. <link rel="related" type="text/html" href="" />
  339. <id>,2018:/linked//6.34931</id>
  340. <published>2018-06-15T00:20:19Z</published>
  341. <updated>2018-06-15T00:20:21Z</updated>
  342. <author>
  343. <name>John Gruber</name>
  344. <uri></uri>
  345. </author>
  346. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  347. <p>Quentin Carnicelli:</p>
  349. <blockquote>
  350.  <p>At the time of the writing, with the exception of the $5,000 iMac
  351. Pro, no Macintosh has been updated at all in the past year. [&#8230;]</p>
  353. <p>Rather than attempting to wow the world with “innovative” new
  354. designs like the failed Mac Pro, Apple could and should simply
  355. provide updates and speed bumps to the entire lineup on a much
  356. more frequent basis. The much smaller Apple of the mid-2000s
  357. managed this with ease. Their current failure to keep the Mac
  358. lineup fresh, even as they approach a trillion dollar market cap,
  359. is both baffling and frightening to anyone who depends on the
  360. platform for their livelihood.</p>
  361. </blockquote>
  363. <p>Compare and contrast with the iPhone, which is updated not just annually, but predictably. Post-WWDC, I&#8217;ve had a few friends and readers ask whether they should just go ahead and buy a MacBook or MacBook Pro now &#8212; knowing they&#8217;re old, knowing the keyboards are of questionable reliability &#8212; or wait until fall. I have no idea if new MacBooks are coming in the fall though. It certainly seems like they <em>should</em>, but would you really be surprised if we don&#8217;t see new MacBooks (and iMacs) until 2019?</p>
  365. <p>I&#8217;d really love to see Apple get Mac hardware on a roughly annual schedule, even if most years they&#8217;re just speed bumps, like they were a decade ago.</p>
  367. <div>
  368. <a  title="Permanent link to ‘On the Sad State of Macintosh Hardware’"  href="">&nbsp;★&nbsp;</a>
  369. </div>
  371. ]]></content>
  372.  </entry><entry>
  373. <title>A Brief Moment of Honesty</title>
  374. <link rel="alternate" type="text/html" href="" />
  375. <link rel="shorturl" type="text/html" href="" />
  376. <link rel="related" type="text/html" href="" />
  377. <id>,2018:/linked//6.34930</id>
  378. <published>2018-06-14T17:54:48Z</published>
  379. <updated>2018-06-14T17:54:50Z</updated>
  380. <author>
  381. <name>John Gruber</name>
  382. <uri></uri>
  383. </author>
  384. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  385. <p>Donald Trump, in Singapore, asked whether he believes Kim Jong-un will actually destroy a nuclear site and return American POW remains:</p>
  387. <blockquote>
  388.  <p>&#8220;Honestly, I think he’s going to do these things. I may be wrong,
  389. I mean I may stand before you in six months and say, hey, I was
  390. wrong &#8212; I don’t know that I’ll ever admit that, but I’ll find
  391. some kind of an excuse.&#8221;</p>
  392. </blockquote>
  394. <p>That&#8217;s the most honest thing he has said as president.</p>
  396. <div>
  397. <a  title="Permanent link to ‘A Brief Moment of Honesty’"  href="">&nbsp;★&nbsp;</a>
  398. </div>
  400. ]]></content>
  401.  </entry><entry>
  402. <title>Not Only Is the Mac Mini Outdated, It’s No Longer Mini</title>
  403. <link rel="alternate" type="text/html" href="" />
  404. <link rel="shorturl" type="text/html" href="" />
  405. <link rel="related" type="text/html" href="" />
  406. <id>,2018:/linked//6.34929</id>
  407. <published>2018-06-14T17:51:19Z</published>
  408. <updated>2018-06-14T18:11:24Z</updated>
  409. <author>
  410. <name>John Gruber</name>
  411. <uri></uri>
  412. </author>
  413. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  414. <p>Jason Snell, writing at Six Colors back in March:</p>
  416. <blockquote>
  417.  <p>The Mac mini was last updated 1245 days ago, in October of 2014.
  418. (And that was a <a href="">lackluster upgrade</a>.) Taking a cue <a href="">from my
  419. dreams about what a modern Mac mini might be like</a>, I bought a
  420. tiny Intel NUC PC and <a href="">installed macOS on it</a>. My Mac mini was
  421. becoming unreliable and I was hoping to experiment with Intel’s
  422. hardware in advance of a real Mac mini being released.</p>
  424. <p>This was intended to be a temporary experiment. And, in fact, I
  425. hope to replace the NUC with a real Mac mini just as soon as Apple
  426. finally releases that all-new Mac mini that’s hopefully
  427. percolating inside Cupertino. But in the meantime, I have been
  428. running macOS on non-Apple hardware, and it’s been an instructive
  429. experience.</p>
  430. </blockquote>
  432. <p>Cheaper and faster, but a pain in the ass to keep updated software-wise. All of that is to be expected. But the striking thing to me is just how much <em>smaller</em> the Intel NUC is. <a href="">It&#8217;s only a <em>little</em> bit bigger than an Apple TV</a>. Calling the Mac Mini &#8220;mini&#8221; is absurd in 2018.</p>
  434. <p>I wrote about this last September, <a href="">when the Apple TV 4K came out</a>:</p>
  436. <blockquote>
  437.  <p>Apple TV 4K is tiny compared to a Mac Mini, but judging by
  438. Geekbench scores (<a href=";q=mac+mini&amp;sort=score">Mac Mini</a>; <a href=";q=ipad+pro&amp;sort=score">iPad Pro</a>, which uses the
  439. A10X in the Apple TV) it’s a slightly faster computer than even
  440. the maxed-out Mac Mini configuration. Apple TV 4K probably has
  441. better GPU performance too. In addition to all the performance
  442. problems stemming from the fact that the Mac Mini hasn’t been
  443. updated in three years, it’s also inarguable that it’s no longer
  444. even “mini”. You could arrange four Apple TV units in a 2 × 2
  445. square and they’d take up the same volume as one Mac Mini.</p>
  446. </blockquote>
  448. <p>Apple TV proves that Apple can make an amazing compact puck-sized computer. They just seem to have lost any interest in making one that runs MacOS.</p>
  450. <div>
  451. <a  title="Permanent link to ‘Not Only Is the Mac Mini Outdated, It&#8217;s No Longer Mini’"  href="">&nbsp;★&nbsp;</a>
  452. </div>
  454. ]]></content>
  455.  </entry><entry>
  456. <title>Audio of Mets Pitcher Noah Syndergaard and Manager Terry Collins Getting Ejected From a Game Last Year</title>
  457. <link rel="alternate" type="text/html" href="" />
  458. <link rel="shorturl" type="text/html" href="" />
  459. <link rel="related" type="text/html" href="" />
  460. <id>,2018:/linked//6.34928</id>
  461. <published>2018-06-13T23:19:02Z</published>
  462. <updated>2018-06-14T17:38:30Z</updated>
  463. <author>
  464. <name>John Gruber</name>
  465. <uri></uri>
  466. </author>
  467. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  468. <p>I don&#8217;t know why this is only going viral now, because it&#8217;s a game from last year, but this is amazingly entertaining. The backstory: in the 2015 playoffs, Dodgers second baseman Chase Utley slid hard into second base <a href="">and Mets second baseman Ruben Tejada wound up with a broken leg</a>. It was an ugly but legal play and it resulted in MLB changing the rules on how you could slide into bases. This is the first game the Mets played against the Dodgers last year, and pitcher Noah Syndergaard &#8212; one of the hardest throwers in the history of baseball &#8212; threw a pitch at Utley.</p>
  470. <p>The umps ejected Syndergaard and manager Terry Collins from the game. Umpire crew chief Tom Hallion was wearing a mic. The audio is fantastically compelling and profane. If MLB mic&#8217;d every ejection <a href="">their TV ratings would soar</a>. I&#8217;d pay double to MLB for my annual At Bat subscription if I could listen to the audio of ejections.</p>
  472. <p><strong>Update:</strong> I keep changing the URL to one that still works, because MLB&#8217;s copyright lawyers are trying to put the toothpaste back in the tube with takedown demands.</p>
  474. <div>
  475. <a  title="Permanent link to ‘Audio of Mets Pitcher Noah Syndergaard and Manager Terry Collins Getting Ejected From a Game Last Year’"  href="">&nbsp;★&nbsp;</a>
  476. </div>
  478. ]]></content>
  479.  </entry><entry>
  480. <title>What’s the Deal With AirPower?</title>
  481. <link rel="alternate" type="text/html" href="" />
  482. <link rel="shorturl" type="text/html" href="" />
  483. <link rel="related" type="text/html" href="" />
  484. <id>,2018:/linked//6.34927</id>
  485. <published>2018-06-13T19:52:59Z</published>
  486. <updated>2018-06-13T19:53:00Z</updated>
  487. <author>
  488. <name>John Gruber</name>
  489. <uri></uri>
  490. </author>
  491. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  492. <p>9to5Mac, back in February:</p>
  494. <blockquote>
  495.  <p>According to a new report from <a href="">Macotakara</a>, Apple is on
  496. schedule to begin selling AirPower sometime in March through its
  497. own retail stores, as well as resellers such as Best Buy.</p>
  499. <p>The report doesn’t offer a specific release date, with the
  500. blog’s source only saying that the release will occur sometime
  501. next month.</p>
  502. </blockquote>
  504. <p>At this point Apple is under three months away from the one-year anniversary of AirPower&#8217;s announcement. To be clear, Apple said all along it wouldn&#8217;t be shipping until &#8220;2018&#8221;, but it&#8217;s hard not to draw the conclusion that something has gone seriously wrong with this product.</p>
  506. <div>
  507. <a  title="Permanent link to ‘What&#8217;s the Deal With AirPower?’"  href="">&nbsp;★&nbsp;</a>
  508. </div>
  510. ]]></content>
  511.  </entry><entry>
  512. <title>‘Do You Know What Fernet Is? It’s a Terrible Thing.’</title>
  513. <link rel="alternate" type="text/html" href="" />
  514. <link rel="shorturl" type="text/html" href="" />
  515. <link rel="related" type="text/html" href="" />
  516. <id>,2018:/linked//6.34926</id>
  517. <published>2018-06-13T19:31:27Z</published>
  518. <updated>2018-06-13T19:31:29Z</updated>
  519. <author>
  520. <name>John Gruber</name>
  521. <uri></uri>
  522. </author>
  523. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  524. <p>I laughed my way through this interview with my friend Lê, owner of Hop Sing Laundromat, by Philly Mag&#8217;s Victor Fiorillo: </p>
  526. <blockquote>
  527.  <p><em>One spirit I cannot stand…</em> is &#8212; wait a minute. You’re trying to
  528. get me in fucking trouble. I already get enough hate mail.
  529. [Another off-the-record-conversation]. OK. OK. One spirit I cannot
  530. stand is any stupid thing that is praised by a quote-unquote
  531. mixologist. Make sure you put the quote-unquote around that word.
  532. They are fucking idiots. Anybody who calls themselves a mixologist
  533. is a fucking idiot. And any spirit that a “mixologist” likes to
  534. use fucking sucks. Fernet. Fernet. Do you know what Fernet is?
  535. It’s a terrible thing. Fuck that shit. These “mixologists” don’t
  536. even know what it is. They drink it because it’s cool. Anything
  537. that makes people look cool &#8212; or that they think makes them look
  538. cool &#8212; I fucking hate that shit.</p>
  539. </blockquote>
  541. <p>Don&#8217;t get him started on the Rocky statue, either. I say we all go into Hop Sing for the next few weeks and ask Lê if he has anything with Fernet on the menu.</p>
  543. <div>
  544. <a  title="Permanent link to ‘&#8216;Do You Know What Fernet Is? It&#8217;s a Terrible Thing.&#8217;’"  href="">&nbsp;★&nbsp;</a>
  545. </div>
  547. ]]></content>
  548.  </entry><entry>
  549. <title>From the DF Archive: ‘What if the iPad Smart Keyboard Had a Trackpad?’</title>
  550. <link rel="alternate" type="text/html" href="" />
  551. <link rel="shorturl" type="text/html" href="" />
  552. <link rel="related" type="text/html" href="" />
  553. <id>,2018:/linked//6.34925</id>
  554. <published>2018-06-13T18:16:44Z</published>
  555. <updated>2018-06-13T19:38:34Z</updated>
  556. <author>
  557. <name>John Gruber</name>
  558. <uri></uri>
  559. </author>
  560. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  561. <p>Yours truly, a year ago, making the case for trackpad support on iPad keyboards:</p>
  563. <blockquote>
  564.  <p>In short, when you’re using the iPad’s on-screen keyboard, you
  565. have a crummy (or at the very least sub-par) keyboard for typing
  566. but a nice interface for moving the insertion point around. When
  567. you’re using the Smart Keyboard (or any other hardware keyboard)
  568. you have a decent keyboard for typing but no good way to move the
  569. insertion point or select text. Using your finger to touch the
  570. screen is imprecise, and, when an iPad is propped up laptop-style,
  571. ergonomically undesirable.</p>
  572. </blockquote>
  574. <p>Whenever Apple executives are asked about the notion of touchscreen Macs, they argue, correctly in my opinion, that it&#8217;s a bad idea because the ergonomics are bad. It just isn&#8217;t comfortable (or precise) to reach out with your arm. There are several other good arguments against adding touchscreen support to Macs, but ergonomics are a good one to place at the top of the list.</p>
  576. <p>The thing is, every ergonomic argument against touchscreen MacBooks applies exactly to using an iPad in &#8220;laptop mode&#8221; with a hardware keyboard. When using a hardware keyboard, it makes sense to keep your hands flat on the desk/table. If Apple thinks iPads are useful with hardware keyboards &#8212; and I think they could be &#8212; they need to add trackpad support of some kind.</p>
  578. <p>I was in a busy coffee shop yesterday and looked around. At least 20 patrons were using notebook computers, most of them MacBooks of some sort. Old MacBook Airs (or maybe new MacBook Airs &#8212; how can you tell?), MacBook Pros, just-plain MacBooks. Some PC notebooks as well, of course. I didn&#8217;t see one person using an iPad &#8212; despite the fact that iPads outsell all Macs combined by more than 2-to-1 every single quarter. Would trackpad support alone change that? I don&#8217;t know. But it would certainly help, and it&#8217;d move us one step closer to <a href="">an iOS notebook</a>.</p>
  580. <div>
  581. <a  title="Permanent link to ‘From the DF Archive: &#8216;What if the iPad Smart Keyboard Had a Trackpad?&#8217;’"  href="">&nbsp;★&nbsp;</a>
  582. </div>
  584. ]]></content>
  585.  </entry><entry>
  586. <title>Apple Tries to Stop Developers From Sharing Data on Users’ Friends</title>
  587. <link rel="alternate" type="text/html" href="" />
  588. <link rel="shorturl" type="text/html" href="" />
  589. <link rel="related" type="text/html" href="" />
  590. <id>,2018:/linked//6.34924</id>
  591. <published>2018-06-13T16:17:45Z</published>
  592. <updated>2018-06-13T17:37:23Z</updated>
  593. <author>
  594. <name>John Gruber</name>
  595. <uri></uri>
  596. </author>
  597. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  598. <p>Sarah Frier and Mark Gurman, reporting for Bloomberg:</p>
  600. <blockquote>
  601.  <p>As Apple’s annual developer conference got underway on June 4, the
  602. Cupertino, California-based company made many new pronouncements
  603. on stage, including new controls that limit tracking of web
  604. browsing. But the phone maker didn’t publicly mention updated App
  605. Store Review Guidelines that now bar developers from making
  606. databases of address book information they gather from iPhone
  607. users. Sharing and selling that database with third parties is
  608. also now forbidden. And an app can’t get a user’s contact list,
  609. say it’s being used for one thing, and then use it for something
  610. else &#8212; unless the developer gets consent again. Anyone caught
  611. breaking the rules may be banned.</p>
  612. </blockquote>
  614. <p>Hard to disagree with this policy change, but I&#8217;m not sure how Apple can police it. Boobytrap accounts?</p>
  616. <div>
  617. <a  title="Permanent link to ‘Apple Tries to Stop Developers From Sharing Data on Users&#8217; Friends’"  href="">&nbsp;★&nbsp;</a>
  618. </div>
  620. ]]></content>
  621.  </entry><entry>
  622. <title>Fortnite Is Now Available on the Nintendo Switch</title>
  623. <link rel="alternate" type="text/html" href="" />
  624. <link rel="shorturl" type="text/html" href="" />
  625. <link rel="related" type="text/html" href="" />
  626. <id>,2018:/linked//6.34923</id>
  627. <published>2018-06-13T01:15:48Z</published>
  628. <updated>2018-06-13T04:23:14Z</updated>
  629. <author>
  630. <name>John Gruber</name>
  631. <uri></uri>
  632. </author>
  633. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  634. <p>Andrew Webster, reporting for The Verge:</p>
  636. <blockquote>
  637.  <p>The biggest game in the world is coming to the hottest gaming
  638. platform. After a few leaks and rumors, today Epic Games
  639. officially announced that Fortnite is coming the Nintendo Switch.
  640. And it’s coming very soon: it’s available as a free download
  641. today. Unlike other online games such as Rocket League that have
  642. been ported to the platform, it doesn’t appear that Fortnite on
  643. the Switch will include any Nintendo-specific content, so you can
  644. keep dreaming about a Metroid skin or Wario emote. There is also
  645. <a href="">no cross-play with Fortnite players on the PS4</a>.</p>
  646. </blockquote>
  648. <p>I&#8217;ll probably get my ass kicked trying, but <em>Fortnite</em> is the first serious game in years that I&#8217;ve been interested in playing. And there&#8217;s no risk, because it&#8217;s free to play &#8212; which is a big part of what I find fascinating about it.</p>
  650. <p>Sony disallowing cross-platform play kind of sucks &#8212; you <em>can</em> cross-play between Xbox, PC (including Mac), and iOS. It just goes to show the power of being the leading platform. Nintendo is just as lock-in/control-freak minded as Sony, but only Sony is in a position to demand something like this from Epic.</p>
  652. <blockquote>
  653.  <p>The news comes not long after Epic announced that the game would
  654. be coming to Android this summer; it’s currently available on PC,
  655. PS4, Xbox One, and iOS.</p>
  656. </blockquote>
  658. <p>If they&#8217;ve already ported <em>Fortnite</em> to iOS, why haven&#8217;t they ported it to Apple TV? That should be easy. The obvious answer: Apple TV is such a non-entity for gaming that Epic doesn&#8217;t even consider a relatively easy port to be worth their time.</p>
  660. <p><strong>Update:</strong> A few readers have pointed out that the big reason Epic probably doesn&#8217;t think bringing <em>Fortnite</em> to Apple TV would be worth their time is that it would require a gaming controller, and most Apple TV owners don&#8217;t have one. Having played on the Switch for a bit tonight (I once finished 13th out of 100 &#8212; albeit with couch-side coaching from my son, who guided me to a house with a hidden <em>Lost</em>-esque bunker under the basement) there&#8217;s just no way this game could possibly be played using an Apple TV remote. It needs a lot of buttons. Apple&#8217;s blind spot for gaming on Apple TV is just baffling to me, especially given the prowess of their chip team. They&#8217;ve got the hard part down &#8212; CPU/GPU performance and developer support for iOS &#8212; but are completely missing out because they don&#8217;t ship a version of the hardware with a gaming controller.</p>
  662. <div>
  663. <a  title="Permanent link to ‘Fortnite Is Now Available on the Nintendo Switch’"  href="">&nbsp;★&nbsp;</a>
  664. </div>
  666. ]]></content>
  667.  </entry><entry>
  668. <title>Inside the Growing Flat Earth Movement</title>
  669. <link rel="alternate" type="text/html" href="" />
  670. <link rel="shorturl" type="text/html" href="" />
  671. <link rel="related" type="text/html" href="" />
  672. <id>,2018:/linked//6.34921</id>
  673. <published>2018-06-11T20:45:00Z</published>
  674. <updated>2018-06-13T19:43:05Z</updated>
  675. <author>
  676. <name>John Gruber</name>
  677. <uri></uri>
  678. </author>
  679. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  680. <p>Alan Burdick, writing for The New Yorker:</p>
  682. <blockquote>
  683.  <p>The unsettling thing about spending two days at a convention of
  684. people who believe that Earth is flat isn’t the possibility that
  685. you, too, might come to accept their world view, although I did
  686. worry a little about that. Rather, it’s the very real likelihood
  687. that, after sitting through hours of presentations on “scientism,”
  688. lightning angels, and nasa’s many conspiracies &#8212; the moon-landing
  689. hoax, the International Fake Station, so-called satellites &#8212; and
  690. in chatting with I.T. specialists, cops, college students, and
  691. fashionably dressed families with young children, all of them
  692. unfailingly earnest and lovely, you will come to actually
  693. understand why a growing number of people are dead certain that
  694. Earth is flat. Because that truth is unnerving.</p>
  695. </blockquote>
  697. <p>In recent years I&#8217;ve begun to feel conflicted about the internet. On the one hand, it&#8217;s been wonderful in so many ways. I&#8217;ve personally built my entire career on the fact that the internet enables me to publish as a one-person operation. But on the other hand, before the internet, kooks were forced to exist on the fringe. There&#8217;ve always been flat-earther-types denying science and John Birch Society political fringers, but they had no means to amplify their message or bond into large movements.</p>
  699. <div>
  700. <a  title="Permanent link to ‘Inside the Growing Flat Earth Movement’"  href="">&nbsp;★&nbsp;</a>
  701. </div>
  703. ]]></content>
  704.  </entry><entry>
  705. <title>Dominik Wagner: ‘On My Misalignment With Apple’s Love Affair With Swift’</title>
  706. <link rel="alternate" type="text/html" href="" />
  707. <link rel="shorturl" type="text/html" href="" />
  708. <link rel="related" type="text/html" href="" />
  709. <id>,2018:/linked//6.34920</id>
  710. <published>2018-06-11T20:01:24Z</published>
  711. <updated>2018-06-11T20:01:26Z</updated>
  712. <author>
  713. <name>John Gruber</name>
  714. <uri></uri>
  715. </author>
  716. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  717. <p>Dominik Wagner:</p>
  719. <blockquote>
  720.  <ul>
  721. <li><p>It seems to have been driven by the needs of the compiler and
  722. the gaps that needed to be filled for the static analyzer. Those
  723. seem to have been super-charged instead of catering to app
  724. developer&#8217;s actual needs: efficient, hassle free, productive
  725. (iOS) App development.</p></li>
  726. <li><p>It is meant to offer progressive disclosure and be simple, to be
  727. used in playgrounds and learning. At the same time learning and
  728. reading through the Swift book and standard library is more akin
  729. to mastering C++. It is quite unforgiving, harsh, and complex.</p></li>
  730. </ul>
  731. </blockquote>
  733. <p>This is a really thoughtful, measured take against Swift. I know a lot of developers love Swift, but I also know many who share similar misgivings about it, primarily that it isn&#8217;t optimized specifically for writing great apps.</p>
  735. <div>
  736. <a  title="Permanent link to ‘Dominik Wagner: &#8216;On My Misalignment With Apple&#8217;s Love Affair With Swift&#8217;’"  href="">&nbsp;★&nbsp;</a>
  737. </div>
  739. ]]></content>
  740.  </entry><entry>
  741. <title>Five iOS 12 Features Apple Didn’t Announce On-Stage Last Week</title>
  742. <link rel="alternate" type="text/html" href=";v=BIy_yRlh9dA" />
  743. <link rel="shorturl" type="text/html" href="" />
  744. <link rel="related" type="text/html" href="" />
  745. <id>,2018:/linked//6.34919</id>
  746. <published>2018-06-11T19:49:52Z</published>
  747. <updated>2018-06-11T19:49:54Z</updated>
  748. <author>
  749. <name>John Gruber</name>
  750. <uri></uri>
  751. </author>
  752. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  753. <p>Good rundown of some under-the-radar features from Rene Ritchie.</p>
  755. <div>
  756. <a  title="Permanent link to ‘Five iOS 12 Features Apple Didn&#8217;t Announce On-Stage Last Week’"  href="">&nbsp;★&nbsp;</a>
  757. </div>
  759. ]]></content>
  760.  </entry><entry>
  761. <link rel="alternate" type="text/html" href="" />
  762. <link rel="shorturl" href="" />
  763. <link rel="related" type="text/html" href="" />
  764. <id>,2018:/feeds/sponsors//11.34922</id>
  765. <author><name>Daring Fireball Department of Commerce</name></author>
  766. <published>2018-06-11T19:46:22-04:00</published>
  767. <updated>2018-06-11T19:46:23-04:00</updated>
  768. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  769. <p>With over 4 million members and more than 20,000 classes, Skillshare is basically Netflix for online learning. Interested in app development or data science? How about UX design or SEO? Mobile photography, film making, creative writing, even coffee brewing? Skillshare truly has it all.</p>
  771. <p>And for this week only, <a href="">Skillshare is offering the first 1,000 Daring Fireball readers TWO FREE months of Skillshare Premium</a>. Whether you’re looking to gain technical skills, want to unlock your creative potential, or are just learning for learning’s sake, Skillshare’s got you covered. <a href="">Click here to redeem</a>.</p>
  773. <div>
  774. <a  title="Permanent link to ‘Skillshare &#8212; The Best Way to Learn Online’"  href="">&nbsp;★&nbsp;</a>
  775. </div>
  777. ]]></content>
  778. <title>[Sponsor] Skillshare -- The Best Way to Learn Online</title></entry><entry>
  779. <title>The Talk Show Live From WWDC 2018</title>
  780. <link rel="alternate" type="text/html" href="" />
  781. <link rel="shorturl" type="text/html" href="" />
  782. <link rel="related" type="text/html" href="" />
  783. <id>,2018:/linked//6.34917</id>
  784. <published>2018-06-10T18:06:13Z</published>
  785. <updated>2018-06-10T18:06:14Z</updated>
  786. <author>
  787. <name>John Gruber</name>
  788. <uri></uri>
  789. </author>
  790. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  791. <p><iframe width="560" height="315" src="" frameborder="0" allow="autoplay; encrypted-media" allowfullscreen></iframe></p>
  793. <p>Recorded in front of a live audience at The California Theatre in San Jose, John Gruber is joined by Greg Joswiak and Mike Rockwell to discuss the news from WWDC: ARKit 2, the new USDZ file format, iOS 12, MacOS 10.14 “Mojave”, UIKit apps on MacOS, and more.</p>
  795. <p>Sponsored by:</p>
  797. <ul>
  798. <li><a href="">Instabug</a>: In-app feedback and bug reporting for mobile apps.</li>
  799. <li><a href="">MacStadium</a>: Enterprise class hosting for Macs.</li>
  800. <li><a href="">Microsoft</a>: Build intelligent iOS apps that scale.</li>
  801. </ul>
  803. <p>(With an open bar provided by <a href="">Setapp</a>.)</p>
  805. <div>
  806. <a  title="Permanent link to ‘The Talk Show Live From WWDC 2018’"  href="">&nbsp;★&nbsp;</a>
  807. </div>
  809. ]]></content>
  810.  </entry><entry>
  811. <title>Instabug</title>
  812. <link rel="alternate" type="text/html" href=";utm_medium=feed&amp;utm_campaign=newsletter12" />
  813. <link rel="shorturl" type="text/html" href="" />
  814. <link rel="related" type="text/html" href="" />
  815. <id>,2018:/linked//6.34916</id>
  816. <published>2018-06-09T20:43:20Z</published>
  817. <updated>2018-06-09T20:43:22Z</updated>
  818. <author>
  819. <name>John Gruber</name>
  820. <uri></uri>
  821. </author>
  822. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  823. <p>My thanks to Instabug for sponsoring this week&#8217;s DF RSS feed (as well as The Talk Show Live From WWDC 2018). Tens of thousands of companies like Lyft, eBay, and T-Mobile rely on Instabug to iterate faster and enhance their app quality.</p>
  825. <p>With just one line of code, your beta testers and users can now report bugs and submit detailed feedback by just shaking their phones.
  826. Instabug automatically captures a screenshot, screen recordings, all device details and repro-steps with each bug report to be displayed in one organized dashboard, so you and your team can track all bugs, feedback and crashes in one place.</p>
  828. <p>They have a cool <a href="">sample app</a> in the App Store that you can try for free, to experience their reporting interface first hand. Then, you can log into their <a href="">demo dashboard</a> and see what the reports look like from the developers’ end. I tried it out and it looks and works great, on both sides.</p>
  830. <p><a href=";utm_medium=feed&amp;utm_campaign=newsletter12">Try Instabug now for free</a>. Even better, they’re offering special $150 “Instabug Credits” for DF readers. Enter promo code “DF18&#8221; to claim your credits.</p>
  832. <div>
  833. <a  title="Permanent link to ‘Instabug’"  href="">&nbsp;★&nbsp;</a>
  834. </div>
  836. ]]></content>
  837.  </entry><entry>
  838. <title>Facebook Bug Set 14 Million Users’ Sharing Settings to Public</title>
  839. <link rel="alternate" type="text/html" href="" />
  840. <link rel="shorturl" type="text/html" href="" />
  841. <link rel="related" type="text/html" href="" />
  842. <id>,2018:/linked//6.34915</id>
  843. <published>2018-06-08T22:39:33Z</published>
  844. <updated>2018-06-08T22:39:34Z</updated>
  845. <author>
  846. <name>John Gruber</name>
  847. <uri></uri>
  848. </author>
  849. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  850. <p>Heather Kelly, reporting for CNN:</p>
  852. <blockquote>
  853.  <p>For a period of four days in May, about 14 million Facebook users
  854. around the world had their default sharing setting for all new
  855. posts set to public, the company revealed Thursday.</p>
  857. <p>The bug, which affected those users from May 18 to May 22,
  858. occurred while Facebook was testing a new feature.</p>
  859. </blockquote>
  861. <p><a href="">David Frum</a>:</p>
  863. <blockquote>
  864.  <p>It&#8217;s so weird that this never happens the other way around,
  865. settings accidentally changed so that Facebook users inadvertently
  866. get more privacy than they signed up for.</p>
  867. </blockquote>
  869. <p>Yeah, so weird. What are the odds?</p>
  871. <div>
  872. <a  title="Permanent link to ‘Facebook Bug Set 14 Million Users&#8217; Sharing Settings to Public’"  href="">&nbsp;★&nbsp;</a>
  873. </div>
  875. ]]></content>
  876.  </entry><entry>
  877. <title>How the Washington Capitals Partied in Las Vegas With the Stanley Cup</title>
  878. <link rel="alternate" type="text/html" href="" />
  879. <link rel="shorturl" type="text/html" href="" />
  880. <link rel="related" type="text/html" href="" />
  881. <id>,2018:/linked//6.34914</id>
  882. <published>2018-06-08T16:39:09Z</published>
  883. <updated>2018-06-08T16:39:11Z</updated>
  884. <author>
  885. <name>John Gruber</name>
  886. <uri></uri>
  887. </author>
  888. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  889. <p>Adam Kilgore, writing for The Washington Post:</p>
  891. <blockquote>
  892.  <p>First, the Washington Capitals won the National Hockey League
  893. championship Thursday night. And then, as their red-rocking fans
  894. were passing out in a fit of euphoria back East, they took full
  895. advantage of the location in which they claimed the franchise’s
  896. first Stanley Cup. They hit the club, prize in hand, and they
  897. partied.</p>
  899. <p>Some say the sun doesn’t rise in Vegas. The Caps, led by their
  900. captain, were up to the challenge of finding out.</p>
  901. </blockquote>
  903. <p>The whole story is great, but I love this bit so much:</p>
  905. <blockquote>
  906.  <p>The threshold for who could venture on stage started to lower.
  907. Disbelief had yet to dissipate. “How amazing is it you can walk
  908. into a bar and the Stanley Cup is there, 10 yards away?” one
  909. Capitals employee asked, standing by the bar. He then escorted
  910. onto the stage a longtime Caps season-ticket holder who had gained
  911. entry, in part, by buying acceptable clothing off the back of a
  912. man on the street for 20 bucks. (He had previously been denied on
  913. the grounds of wearing sandals and shorts.)</p>
  914. </blockquote>
  916. <div>
  917. <a  title="Permanent link to ‘How the Washington Capitals Partied in Las Vegas With the Stanley Cup’"  href="">&nbsp;★&nbsp;</a>
  918. </div>
  920. ]]></content>
  921.  </entry><entry>
  922. <title>Ersatz Free Trials</title>
  923. <link rel="alternate" type="text/html" href="" />
  924. <link rel="shorturl" type="text/html" href="" />
  925. <link rel="related" type="text/html" href="" />
  926. <id>,2018:/linked//6.34913</id>
  927. <published>2018-06-07T18:52:34Z</published>
  928. <updated>2018-06-07T22:16:13Z</updated>
  929. <author>
  930. <name>John Gruber</name>
  931. <uri></uri>
  932. </author>
  933. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  934. <p>Daniel Jalkut:</p>
  936. <blockquote>
  937.  <p>I think it’s particularly important, in the face of all the celebration this week about Apple’s perceived changes to the App Store, to appreciate all the many ways in which this solution falls short of what many developers still hope for: bona fide support for real free trials in the App Store.</p>
  939. <p>In summary: <em>none of the mechanics of supporting ersatz free trials are substantially supported by the App Store</em>. Every aspect of the solution is bolted on to a system which was not designed for, yet is somewhat admirably being used to simulate real support for free trials. Let me elaborate by listing several shortcomings and how they affect users, and developers, in significant ways.</p>
  940. </blockquote>
  942. <div>
  943. <a  title="Permanent link to ‘Ersatz Free Trials’"  href="">&nbsp;★&nbsp;</a>
  944. </div>
  946. ]]></content>
  947.  </entry><entry>
  948. <title>Kevin Roose: ‘How I Learned to Stop Worrying and Love Electric Scooters’</title>
  949. <link rel="alternate" type="text/html" href="" />
  950. <link rel="shorturl" type="text/html" href="" />
  951. <link rel="related" type="text/html" href="" />
  952. <id>,2018:/linked//6.34912</id>
  953. <published>2018-06-06T23:43:15Z</published>
  954. <updated>2018-06-06T23:54:37Z</updated>
  955. <author>
  956. <name>John Gruber</name>
  957. <uri></uri>
  958. </author>
  959. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  960. <p>Kevin Roose, writing for The New York Times:</p>
  962. <blockquote>
  963.  <p>Tech hubris on wheels &#8212; what’s not to loathe?</p>
  965. <p>But I wanted to experience the scooter craze for myself. So for a week, I used shared e-scooters as my primary mode of transportation. I rode them to meetings, ran errands across town and went for long joy rides on the Venice Beach boardwalk. In all, I took more than a dozen scooter rides, from just a few blocks to several miles.</p>
  967. <p>And here’s my verdict: E-scooters might look and feel kind of dorky, but they aren’t an urban menace or a harbinger of the apocalypse. In fact &#8212; <em>sigh</em> &#8212; they’re pretty great.</p>
  968. </blockquote>
  970. <p>That’s pretty much the consensus here in San Jose from fellow WWDC attendees. We didn’t want to like these scooters but we do. The big problem is parking them — it’s just wrong that people abandon them anywhere and everywhere. The other problem is people who ride them on sidewalks rather than in the street where they belong.</p>
  972. <div>
  973. <a  title="Permanent link to ‘Kevin Roose: ‘How I Learned to Stop Worrying and Love Electric Scooters’’"  href="">&nbsp;★&nbsp;</a>
  974. </div>
  976. ]]></content>
  977.  </entry><entry>
  978. <title>Safari Technology Preview 58 Includes Support for Favicons in Tabs</title>
  979. <link rel="alternate" type="text/html" href="" />
  980. <link rel="shorturl" type="text/html" href="" />
  981. <link rel="related" type="text/html" href="" />
  982. <id>,2018:/linked//6.34911</id>
  983. <published>2018-06-06T23:38:43Z</published>
  984. <updated>2018-06-06T23:41:50Z</updated>
  985. <author>
  986. <name>John Gruber</name>
  987. <uri></uri>
  988. </author>
  989. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  990. <p>Ricky Mondello:</p>
  992. <blockquote>
  993.  <p>This release covers the same revisions of WebKit from Safari Technology Preview 57, but includes new Safari and WebKit features that will be present in Safari 12. The following Safari 12 features are new to Safari Technology Preview 58:</p>
  995. <p>Icons in Tabs. You can enable showing website icons in tabs in Safari’s Tabs preferences.</p>
  996. </blockquote>
  998. <p>This is great. I don’t want to run Mojave betas, but I’ll gladly use Safari Technology Preview builds.</p>
  1000. <div>
  1001. <a  title="Permanent link to ‘Safari Technology Preview 58 Includes Support for Favicons in Tabs’"  href="">&nbsp;★&nbsp;</a>
  1002. </div>
  1004. ]]></content>
  1005.  </entry><entry>
  1006. <title>The Talk Show Live From WWDC 2018</title>
  1007. <link rel="alternate" type="text/html" href="" />
  1008. <link rel="shorturl" type="text/html" href="" />
  1009. <link rel="related" type="text/html" href="" />
  1010. <id>,2018:/linked//6.34910</id>
  1011. <published>2018-06-06T01:40:11Z</published>
  1012. <updated>2018-06-06T01:55:17Z</updated>
  1013. <author>
  1014. <name>John Gruber</name>
  1015. <uri></uri>
  1016. </author>
  1017. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1018. <p>Live streaming video (<a href="">and audio</a>) starting in about 20 minutes.</p>
  1020. <div>
  1021. <a  title="Permanent link to ‘The Talk Show Live From WWDC 2018’"  href="">&nbsp;★&nbsp;</a>
  1022. </div>
  1024. ]]></content>
  1025.  </entry><entry>
  1026. <title>WWDC 2018: Apple’s Software Chief Details How iOS Apps Will Run on Macs | WIRED</title>
  1027. <link rel="alternate" type="text/html" href="" />
  1028. <link rel="shorturl" type="text/html" href="" />
  1029. <link rel="related" type="text/html" href="" />
  1030. <id>,2018:/linked//6.34909</id>
  1031. <published>2018-06-05T20:21:31Z</published>
  1032. <updated>2018-06-05T20:25:51Z</updated>
  1033. <author>
  1034. <name>John Gruber</name>
  1035. <uri></uri>
  1036. </author>
  1037. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1038. <p>Lauren Goode, writing for Wired:</p>
  1040. <blockquote>
  1041.  <p>In an exclusive interview with Wired, Federighi said the frameworks for porting iPhone and iPad apps to the Mac have been in development for two years. He revealed some of the technical details around how this will work, and shared some of the types of iOS apps he believes make sense on the Mac. Federighi was also dismissive of touchscreen laptops &#8212; a product category that would seem like a natural addition to Apple&#8217;s line once laptops begin running touch-first mobile apps.</p>
  1042. </blockquote>
  1044. <p>Still very light on technical details. I get why they announced this a year early — because they wanted to start shipping their own apps built on this — but it’s so unusual for Apple.</p>
  1046. <div>
  1047. <a  title="Permanent link to ‘WWDC 2018: Apple&#8217;s Software Chief Details How iOS Apps Will Run on Macs | WIRED’"  href="">&nbsp;★&nbsp;</a>
  1048. </div>
  1050. ]]></content>
  1051.  </entry><entry>
  1052. <title>Apple Is Testing a Feature That Could Kill Police iPhone Unlockers</title>
  1053. <link rel="alternate" type="text/html" href="" />
  1054. <link rel="shorturl" type="text/html" href="" />
  1055. <link rel="related" type="text/html" href="" />
  1056. <id>,2018:/linked//6.34908</id>
  1057. <published>2018-06-05T00:24:46Z</published>
  1058. <updated>2018-06-05T00:29:42Z</updated>
  1059. <author>
  1060. <name>John Gruber</name>
  1061. <uri></uri>
  1062. </author>
  1063. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1064. <p>Lorenzo Franceschi-Bicchierai, reporting for Motherboard:</p>
  1066. <blockquote>
  1067.  <p>But iOS 12’s killer feature might be something that’s been rumored for a while and wasn’t discussed at Apple’s event. It’s called USB Restricted Mode, and Apple has been including it in some of the iOS beta releases since iOS 11.3.</p>
  1069. <p>The feature essentially forces users to unlock the iPhone with the passcode when connecting it to a USB accessory everytime the phone has not been unlocked for one hour. That includes the iPhone unlocking devices that companies such as Cellebrite or GrayShift make, which police departments all over the world use to hack into seized iPhones.</p>
  1070. </blockquote>
  1072. <p>I love this feature. So clever.</p>
  1074. <div>
  1075. <a  title="Permanent link to ‘Apple Is Testing a Feature That Could Kill Police iPhone Unlockers’"  href="">&nbsp;★&nbsp;</a>
  1076. </div>
  1078. ]]></content>
  1079.  </entry><entry>
  1080. <title>iOS 12 Brings iPhone X Gestures to iPad, Swipe From Top-Right to Open Control Center</title>
  1081. <link rel="alternate" type="text/html" href="" />
  1082. <link rel="shorturl" type="text/html" href="" />
  1083. <link rel="related" type="text/html" href="" />
  1084. <id>,2018:/linked//6.34906</id>
  1085. <published>2018-06-04T21:46:04Z</published>
  1086. <updated>2018-06-04T21:48:11Z</updated>
  1087. <author>
  1088. <name>John Gruber</name>
  1089. <uri></uri>
  1090. </author>
  1091. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1092. <p>I’m not convinced this means the iPad Pro is getting a notch, but either way, I think it’s a good idea for these gestures to match.</p>
  1094. <div>
  1095. <a  title="Permanent link to ‘iOS 12 Brings iPhone X Gestures to iPad, Swipe From Top-Right to Open Control Center’"  href="">&nbsp;★&nbsp;</a>
  1096. </div>
  1098. ]]></content>
  1099.  </entry><entry>
  1100. <title>Jamf Now</title>
  1101. <link rel="alternate" type="text/html" href=";utm_medium=text&amp;utm_campaign=2018-22" />
  1102. <link rel="shorturl" type="text/html" href="" />
  1103. <link rel="related" type="text/html" href="" />
  1104. <id>,2018:/linked//6.34905</id>
  1105. <published>2018-06-02T21:52:49Z</published>
  1106. <updated>2018-06-02T21:52:50Z</updated>
  1107. <author>
  1108. <name>John Gruber</name>
  1109. <uri></uri>
  1110. </author>
  1111. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1112. <p>My thanks to Jamf for sponsoring this week&#8217;s DF RSS feed. Get real-time inventory, configure Wi-Fi and email settings, deploy applications, protect company data, and even lock or wipe a device from anywhere with Jamf Now.</p>
  1114. <p>Jamf Now secures your devices so you can focus on your business. No IT experience needed.</p>
  1116. <p><a href=";utm_medium=text&amp;utm_campaign=2018-22">Daring Fireball readers can create an account and manage three devices for free</a>. Forever. After that, each additional device is just $2 per month. <a href=";utm_medium=text&amp;utm_campaign=2018-22">Create your free account today</a>.</p>
  1118. <div>
  1119. <a  title="Permanent link to ‘Jamf Now’"  href="">&nbsp;★&nbsp;</a>
  1120. </div>
  1122. ]]></content>
  1123.  </entry><entry>
  1124. <title>Android Developers Blog: Insider Attack Resistance</title>
  1125. <link rel="alternate" type="text/html" href="" />
  1126. <link rel="shorturl" type="text/html" href="" />
  1127. <link rel="related" type="text/html" href="" />
  1128. <id>,2018:/linked//6.34904</id>
  1129. <published>2018-06-02T21:51:02Z</published>
  1130. <updated>2018-06-02T21:51:03Z</updated>
  1131. <author>
  1132. <name>John Gruber</name>
  1133. <uri></uri>
  1134. </author>
  1135. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1136. <p>Shawn Willden, software engineer at Google:</p>
  1138. <blockquote>
  1139.  <p>In the past, device makers have focused on safeguarding these keys
  1140. by storing the keys in secure locations and severely restricting
  1141. the number of people who have access to them. That&#8217;s good, but it
  1142. leaves those people open to attack by coercion or social
  1143. engineering. That&#8217;s risky for the employees personally, and we
  1144. believe it creates too much risk for user data.</p>
  1146. <p>To mitigate these risks, Google Pixel 2 devices implement insider
  1147. attack resistance in the tamper-resistant hardware security module
  1148. that guards the encryption keys for user data. This helps prevent
  1149. an attacker who manages to produce properly signed malicious
  1150. firmware from installing it on the security module in a lost or
  1151. stolen device without the user&#8217;s cooperation. Specifically, it is
  1152. not possible to upgrade the firmware that checks the user&#8217;s
  1153. password unless you present the correct user password. There is a
  1154. way to &#8220;force&#8221; an upgrade, for example when a returned device is
  1155. refurbished for resale, but forcing it wipes the secrets used to
  1156. decrypt the user&#8217;s data, effectively destroying it.</p>
  1157. </blockquote>
  1159. <p>This seems like a good idea, and I think the iPhone has been doing this for years. But I&#8217;d love to see someone do a rundown of the low-level security across all popular Android phones.</p>
  1161. <div>
  1162. <a  title="Permanent link to ‘Android Developers Blog: Insider Attack Resistance’"  href="">&nbsp;★&nbsp;</a>
  1163. </div>
  1165. ]]></content>
  1166.  </entry><entry>
  1167. <title>Robinson Meyer: ‘Unfortunately, the Electric Scooters Are Fantastic’</title>
  1168. <link rel="alternate" type="text/html" href=";utm_medium=email" />
  1169. <link rel="shorturl" type="text/html" href="" />
  1170. <link rel="related" type="text/html" href="" />
  1171. <id>,2018:/linked//6.34903</id>
  1172. <published>2018-06-01T19:02:58Z</published>
  1173. <updated>2018-06-01T19:03:00Z</updated>
  1174. <author>
  1175. <name>John Gruber</name>
  1176. <uri></uri>
  1177. </author>
  1178. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1179. <p>Robinson Meyer, writing for The Atlantic:</p>
  1181. <blockquote>
  1182.  <p>When this latest army invaded my village, it seemed no different
  1183. than the rest. I had heard rumor of it for weeks, had feared and
  1184. resented it, had assured friends that its occupation would end as
  1185. soon as all its predecessors. But when its foot soldiers finally
  1186. arrived, I was shocked to find myself charmed. Now, I cannot
  1187. imagine life without them.</p>
  1189. <p>I speak, of course, of the electric scooters.</p>
  1190. </blockquote>
  1192. <div>
  1193. <a  title="Permanent link to ‘Robinson Meyer: &#8216;Unfortunately, the Electric Scooters Are Fantastic&#8217;’"  href="">&nbsp;★&nbsp;</a>
  1194. </div>
  1196. ]]></content>
  1197.  </entry><entry>
  1198. <title>Teetrilogy4</title>
  1199. <link rel="alternate" type="text/html" href="" />
  1200. <link rel="shorturl" type="text/html" href="" />
  1201. <link rel="related" type="text/html" href="" />
  1202. <id>,2018:/linked//6.34902</id>
  1203. <published>2018-06-01T18:56:39Z</published>
  1204. <updated>2018-06-01T18:56:40Z</updated>
  1205. <author>
  1206. <name>John Gruber</name>
  1207. <uri></uri>
  1208. </author>
  1209. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1210. <p>Some new <em>Solo</em>-inspired designs, printed and shipped by Brian Jaramillo, my decade-long partner for DF t-shirts. Great shirts, fun designs, and you get a nice discount if you order three or more.</p>
  1212. <div>
  1213. <a  title="Permanent link to ‘Teetrilogy4’"  href="">&nbsp;★&nbsp;</a>
  1214. </div>
  1216. ]]></content>
  1217.  </entry><entry>
  1218. <title>The Talk Show: ‘Pseudorandom Gibberish’</title>
  1219. <link rel="alternate" type="text/html" href="" />
  1220. <link rel="shorturl" type="text/html" href="" />
  1221. <link rel="related" type="text/html" href="" />
  1222. <id>,2018:/linked//6.34901</id>
  1223. <published>2018-05-31T22:58:46Z</published>
  1224. <updated>2018-05-31T22:58:48Z</updated>
  1225. <author>
  1226. <name>John Gruber</name>
  1227. <uri></uri>
  1228. </author>
  1229. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1230. <p>Rene Ritchie returns to the show. Topics include MacBook keyboard failures, iOS passcode security, Google’s odd Duplex “demo”, Steam Link’s curious rejection from the App Store, AirPlay 2, and, of course, conjecture about next week’s WWDC.</p>
  1232. <p>Brought to you by these fine sponsors:</p>
  1234. <ul>
  1235. <li><a href="">Away</a>: Travel smarter with the suitcase that charges your phone. Save $20 with code <strong>talkshow</strong>.</li>
  1236. <li><a href="">Squarespace</a>: Make your next move. Use code <strong>talkshow</strong> for 10% off your first order.</li>
  1237. <li><a href="">Eero</a>: Finally, Wi-Fi, that works. Free shipping to the U.S. and Canada with code <strong>thetalkshow</strong>.</li>
  1238. </ul>
  1240. <div>
  1241. <a  title="Permanent link to ‘The Talk Show: &#8216;Pseudorandom Gibberish&#8217;’"  href="">&nbsp;★&nbsp;</a>
  1242. </div>
  1244. ]]></content>
  1245.  </entry><entry>
  1247.    <link rel="alternate" type="text/html" href="" />
  1248. <link rel="shorturl" href="" />
  1249. <id>,2018://1.34900</id>
  1250. <published>2018-05-31T22:17:19Z</published>
  1251. <updated>2018-05-31T22:17:21Z</updated>
  1252. <author>
  1253. <name>John Gruber</name>
  1254. <uri></uri>
  1255. </author>
  1256. <summary type="text">iOS’s “Erase all data on this iPhone after 10 failed passcode attempts” feature is far more clever than I realized, and it’s highly unlikely that your kids or jackass drinking buddies could ever trigger it.</summary>
  1257. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1258. <p>For many years now, iOS has offered an option in the Passcode section of the Settings all: &#8220;Erase all data on this iPhone after 10 failed passcode attempts.&#8221;</p>
  1260. <p>I&#8217;ve long been intrigued by this setting, but never turned it on, out of the vague fear that <em>something</em> could happen and I&#8217;d wind up with a wiped iPhone. Say, if a &#8220;friend&#8221; surreptitiously took my phone at a bar and entered 10 wrong passcodes as a prank. Something like that.</p>
  1262. <p><a href="">I asked on Twitter over the weekend how many people use this feature</a>, and over 4,000 people responded to the poll. One-third use the feature, two-thirds don&#8217;t. Among those who don&#8217;t, the most common response, by far, is that they don&#8217;t use it because they&#8217;re the parents of young children, and they fear that their kids will trigger the erasure of their phone.</p>
  1264. <p>I had no idea until I looked into it last weekend, but it turns out this feature is far more clever than I realized, and it&#8217;s highly unlikely that your kids or jackass drinking buddies could ever trigger it. After the 5th failed attempt, iOS requires a 1-minute timeout before you can try again. During this timeout the only thing you can do is place an emergency call to 911. After the 6th attempt, you get a 5-minute timeout. After the 7th, 15 minutes. These timeouts escalate such that it would take over 3 hours to enter 10 incorrect passcodes.</p>
  1266. <p>It seems pretty clear from the responses to my poll that I wasn&#8217;t alone in thinking that this feature was more dangerous than it really is. I&#8217;ve got it turned on now, and I can&#8217;t think of a good reason why anyone <em>wouldn&#8217;t</em> enable this.</p>
  1270.    ]]></content>
  1271.  <title>★ 10 Strikes and You’re Out — the iOS Feature You’re Probably Not Using But Should</title></entry><entry>
  1272. <title>Things 3.6 for iPad</title>
  1273. <link rel="alternate" type="text/html" href="" />
  1274. <link rel="shorturl" type="text/html" href="" />
  1275. <link rel="related" type="text/html" href="" />
  1276. <id>,2018:/linked//6.34899</id>
  1277. <published>2018-05-30T18:35:49Z</published>
  1278. <updated>2018-05-30T18:35:52Z</updated>
  1279. <author>
  1280. <name>John Gruber</name>
  1281. <uri></uri>
  1282. </author>
  1283. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1284. <p>Speaking of task management apps for iOS, Things 3.6 addresses something I complain about every month or so: the way that most iPad apps, including Apple&#8217;s own, treat a hardware keyboard as a second-class citizen. There&#8217;s a lot of stuff going on in this video and they never once touched the screen. Very cool.</p>
  1286. <div>
  1287. <a  title="Permanent link to ‘Things 3.6 for iPad’"  href="">&nbsp;★&nbsp;</a>
  1288. </div>
  1290. ]]></content>
  1291.  </entry><entry>
  1292. <title>OmniFocus 3 Review</title>
  1293. <link rel="alternate" type="text/html" href="" />
  1294. <link rel="shorturl" type="text/html" href="" />
  1295. <link rel="related" type="text/html" href="" />
  1296. <id>,2018:/linked//6.34898</id>
  1297. <published>2018-05-30T18:32:15Z</published>
  1298. <updated>2018-05-31T21:43:53Z</updated>
  1299. <author>
  1300. <name>John Gruber</name>
  1301. <uri></uri>
  1302. </author>
  1303. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1304. <p>Ryan Christoffel, writing for MacStories:</p>
  1306. <blockquote>
  1307.  <p><a href="">OmniFocus 3</a>, released today for iOS (and later coming to the
  1308. Mac), adds even more power and options to the app&#8217;s existing
  1309. toolset, yet rather than growing more complex in the process, it&#8217;s
  1310. surprisingly become more approachable. This improved user
  1311. friendliness is achieved thanks to a new level of flexibility that
  1312. can, upon tweaking your ideal setup, obscure the app&#8217;s complexity
  1313. in everyday use. In more ways than ever before, OmniFocus provides
  1314. the tools to make the app your own.</p>
  1315. </blockquote>
  1317. <p>I&#8217;ve never been an OmniFocus user, but version 3&#8217;s addition of tagging (replacing OmniFocus&#8217;s previous &#8220;contexts&#8221; feature) could get me to try it. As usual for MacStories, Christoffel&#8217;s review is comprehensive and insightful.</p>
  1319. <p><strong>Update:</strong> <a href="">David Sparks&#8217;s review</a> is good too.</p>
  1321. <div>
  1322. <a  title="Permanent link to ‘OmniFocus 3 Review’"  href="">&nbsp;★&nbsp;</a>
  1323. </div>
  1325. ]]></content>
  1326.  </entry><entry>
  1327. <title>Retrobatch 1.0</title>
  1328. <link rel="alternate" type="text/html" href="" />
  1329. <link rel="shorturl" type="text/html" href="" />
  1330. <link rel="related" type="text/html" href="" />
  1331. <id>,2018:/linked//6.34896</id>
  1332. <published>2018-05-29T18:41:15Z</published>
  1333. <updated>2018-05-29T18:41:16Z</updated>
  1334. <author>
  1335. <name>John Gruber</name>
  1336. <uri></uri>
  1337. </author>
  1338. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1339. <p>New app from Flying Meat (makers of Acorn, my go-to image editor): a node-based batch image processor. I&#8217;ve been using it in beta for months, and I&#8217;ve only scratched the surface of what Retrobatch can do. It&#8217;s just a delightfully well-done Mac app.</p>
  1341. <div>
  1342. <a  title="Permanent link to ‘Retrobatch 1.0’"  href="">&nbsp;★&nbsp;</a>
  1343. </div>
  1345. ]]></content>
  1346.  </entry><entry>
  1348.    <link rel="alternate" type="text/html" href="" />
  1349. <link rel="shorturl" href="" />
  1350. <id>,2018://1.34878</id>
  1351. <published>2018-05-22T22:28:47Z</published>
  1352. <updated>2018-05-23T17:51:47Z</updated>
  1353. <author>
  1354. <name>John Gruber</name>
  1355. <uri></uri>
  1356. </author>
  1357. <summary type="text">A recording is *not* a demo.</summary>
  1358. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1359. <p>Let me just reiterate up front that <a href="">my suspicions</a> surrounding Google&#8217;s Duplex recordings are not suspicions regarding the idea of Duplex itself. If I had to bet on who will be the first to create an AI voice system that passes for human, even within the limited constraints of a single well-defined task like booking reservations, it would be Google. If Vegas had a betting line on this, Amazon would probably have decent odds too, but surely Google would be the favorite.</p>
  1361. <p>We can all hear for ourselves how well Google Assistant works today. I&#8217;m not alleging that these recordings are complete fabrications, or betting against Google being further ahead in this effort than anyone else.</p>
  1363. <p>But everything about the way Google announced this &#8212; the <a href="">curious details of the calls</a> released so far, the fact that no one in the media has been allowed to see an actual call happen live &#8212; makes me suspect that for one or more reasons, the <em>current</em> state of Duplex is less than what Sundar Pichai implied on stage. <a href="">His words before the first recording was played</a>: &#8220;What you&#8217;re going to hear is the Google Assistant actually calling a real salon to schedule an appointment for you. Let&#8217;s listen.&#8221; And after the second recording: &#8220;Again, that was a real call.&#8221;</p>
  1365. <p>You can parse those words precisely and argue that Pichai never said they were unscripted or un-coached, or that the recordings are unedited. But that&#8217;s like saying Bill Clinton was technically truthful with his &#8220;I did not have sexual relations with that woman&#8221; statement. The implication of Clinton&#8217;s statement was that he wasn&#8217;t involved sexually with his intern, and that wasn&#8217;t true. The implication of Pichai&#8217;s statement was that right now, today, Google has a version of Duplex in its lab that can call a real restaurant or hair salon and book a reservation and sound truly human while doing so. Not soon, today. Look at the news coverage from the announcement &#8212; <a href="">Mashable</a>, <a href="">The Guardian</a>, <a href="">The Verge</a>, <a href="">The Evening Standard</a> &#8212; all of those reports on Duplex&#8217;s announcement are written in the present tense, as though it&#8217;s something Google has working, as heard, with no or very minimal editing, today.</p>
  1367. <p>If a few months or more from now Google can demonstrate a real Duplex call, live, that wouldn&#8217;t disprove my suspicion that they can&#8217;t do it right now in May 2018 &#8212; even though Sundar Pichai clearly implied last week that they can. If I&#8217;m wrong &#8212; if stories come out in the next week or two from journalists granted behind-the-scenes access to listen to Duplex make live calls (and watch them be parsed correctly, creating calendar events and notifications of the reservation dates and times), and those calls sound every bit as realistically human as the recordings Google has released so far &#8212; my suspicion will be proven false. And I&#8217;d be delighted by that. Part of the reason I&#8217;m so focused on Duplex is that if it really works like it does in these recordings, it&#8217;s one of the most amazing advances in technology in years.</p>
  1369. <p>But Google hasn&#8217;t done that, and the more I think about it, and the longer Google stonewalls on press inquiries about Duplex, the more suspicious I get that they can&#8217;t. Even if Duplex still has a low success rate, it would be amazing if, say, half its calls worked as well and sounded as good as these recordings. That would be perfectly understandable for a technology still in development.</p>
  1371. <p>But Pichai also said &#8220;This will be rolling out in the coming weeks as an experiment.&#8221; On the one hand, that makes me feel like maybe I <em>am</em> off my rocker for being so skeptical. Why in the world would Pichai say that if they weren&#8217;t at a stage in internal testing where Duplex works as the recordings suggest? But on the other hand, if they are that close, why haven&#8217;t they invited anyone from the media to see Duplex in action?</p>
  1373. <p>They did invite Richard Nieva from CNet to a behind-the-scenes preview before I/O, <a href="">but all he got to hear were recordings, too</a>:</p>
  1375. <blockquote>
  1376.  <p>In a building called the Partnerplex on Google&#8217;s sprawling
  1377. campus in Mountain View, California, I&#8217;ve been invited to hear a
  1378. 51-second phone recording of someone making a dinner
  1379. reservation. [&#8230;]</p>
  1381. <p>As I listen to what sounds like a man and a woman talking,
  1382. Google&#8217;s top executives for Assistant, the search giant&#8217;s digital
  1383. helper, watch closely to gauge my reaction. They&#8217;re showing off
  1384. the Assistant&#8217;s new tricks a few days before Google I/O, the
  1385. company&#8217;s annual developer conference that starts Tuesday.</p>
  1387. <p>Turns out this particular trick is pretty wild.</p>
  1389. <p>That&#8217;s because Person 2, the one who sounds like a man, isn&#8217;t a
  1390. person at all. It&#8217;s the Google Assistant.</p>
  1391. </blockquote>
  1393. <p>Why not let Nieva hear it live? Why not let Nieva answer the phone and book the reservation himself, as though he works at the restaurant? If it&#8217;s &#8220;weeks&#8221; away from rolling out in a limited beta to the public, that should be possible.</p>
  1395. <p>The job of journalists is to verify these things, not just to take a company&#8217;s word for it. Here&#8217;s Om Malik, linking to <a href="">Dan Primack&#8217;s Axios story on Google&#8217;s stonewalling</a>:</p>
  1397. <p><a href="">Om Malik</a>:</p>
  1399. <blockquote>
  1400.  <p>&#8220;Google may well have created a lifelike voice assistant&#8230;Or it
  1401. was partially staged. Or something else entirely. We just don&#8217;t
  1402. know, because Google won&#8217;t answer the questions.&#8221; @danprimack
  1403. doing what journalists are supposed to do. Verify and dig deeper!</p>
  1404. </blockquote>
  1406. <p><a href="">Dave Winer, in the same thread</a>:</p>
  1408. <blockquote>
  1409.  <p>Finally journalism starts asking obvious questions of tech.</p>
  1411. <p>Tech journalism has never asked basic questions like &#8220;how did you
  1412. do this?&#8221;</p>
  1414. <p>Apple once used my software to demo their tech, which wasn&#8217;t
  1415. ready.</p>
  1417. <p>Reporters refused to ask about this.</p>
  1418. </blockquote>
  1420. <p>&#8220;How did you do this?&#8221; is a necessary question. But even broader, when you&#8217;re only shown a recording, the question is &#8220;How do we know this is real?&#8221;</p>
  1422. <p>Maybe Duplex, today, works just as well and sounds just as human as these recordings suggest. But maybe it doesn&#8217;t work as well as they claimed, or doesn&#8217;t sound so human,<sup id="fnr1-2018-05-22"><a href="#fn1-2018-05-22">1</a></sup> or takes pauses that were edited out of the clips they&#8217;ve released. We don&#8217;t know, because Google hasn’t allowed anyone to verify anything about it. It’s like a card trick where the magician, rather than an audience member, picks the card and shuffles the deck.</p>
  1424. <p>It’s the difference between, say, watching video of a purported self-driving car versus watching &#8212; or even better, riding as a passenger in &#8212; an actual self-driving car.</p>
  1426. <p>The headlines last week should have been along the lines of &#8220;Google <em>Claims</em> Assistant Can Make Human-Sounding Phone Calls&#8221;, not &#8220;Google Assistant Can Make Human-Sounding Phone Calls&#8221;. There&#8217;s a difference.</p>
  1428. <p>A recording is <em>not</em> a demo. You can demo hardware and software that isn&#8217;t shipping yet &#8212; most companies do, because that&#8217;s when the products are still under wraps and can make for a surprise. But there&#8217;s an obligation to be clear about the current state of the product, and to demo what you currently have working &#8220;for real&#8221;. Showing it privately to select members of the media is another acceptable strategy. Just to cite one famous example from Apple: in January 2007 the original iPhone was six months away from shipping and still needed a <em>lot</em> of work. But what Steve Jobs showed on stage was real &#8212; early stage software running on prototype hardware. Everything demoed was live, not a recording. And then to further prove that, after the keynote, select members of the media, including <a href="">Jason Snell</a>, <a href="">Andy Ihnatko</a>, and <a href="">David Pogue</a>, got up to 45 minutes of actual hands on time with a prototype, even though the software was at such an early stage that some of the default apps <a href="">only showed screenshots of what they were supposed to look like</a>. </p>
  1430. <p>That&#8217;s how you prove to the world that a demo was what you said it was. It is damn curious that Google won&#8217;t do that with Duplex.</p>
  1432. <div class="footnotes">
  1433. <hr />
  1434. <ol>
  1435. <li id="fn1-2018-05-22">
  1436. <p>Google now claims their plan all along has been <a href="">to have Duplex identify itself to humans</a>. I don&#8217;t understand how that squares with the efforts they clearly went through to make Duplex sound convincingly human. It seems clear that they only started thinking about disclosing Duplex as a bot to humans in response to the ethical outcry after the keynote. Ethics aside though, what makes the promise of Duplex so tantalizing as a technology is its seeming humanness.&nbsp;<a href="#fnr1-2018-05-22"  class="footnoteBackLink"  title="Jump back to footnote 1 in the text.">&#x21A9;&#xFE0E;</a></p>
  1437. </li>
  1438. </ol>
  1439. </div>
  1443.    ]]></content>
  1444.  <title>★ Yammering on One More Time Regarding Google’s Duplex Recordings</title></entry><entry>
  1446.    <link rel="alternate" type="text/html" href="" />
  1447. <link rel="shorturl" href="" />
  1448. <id>,2018://1.34858</id>
  1449. <published>2018-05-18T02:36:02Z</published>
  1450. <updated>2018-05-18T18:08:31Z</updated>
  1451. <author>
  1452. <name>John Gruber</name>
  1453. <uri></uri>
  1454. </author>
  1455. <summary type="text">The fact that I had an answer to my question in just 22 minutes shows that having a large follower count on Twitter is a bit of a super power.</summary>
  1456. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1457. <p>At the bottom of Google&#8217;s AI Blog announcement of Duplex (&#8220;<a href="">An AI System for Accomplishing Real World Tasks Over the Phone</a>&#8221;), they included a photo of two Duplex engineers eat a meal, with the following caption:</p>
  1459. <blockquote>
  1460.  <p>Yaniv Leviathan, Google Duplex lead, and Matan Kalman,
  1461. engineering manager on the project, enjoying a meal booked
  1462. through a call from Duplex.</p>
  1463. </blockquote>
  1465. <p>As <a href="">suspicions</a> around this announcement <a href="">deepen</a>, I got to wondering if we could identify this restaurant. If we could identify the restaurant, we could ask them if they had been told in advance they would be speaking to Google Duplex, among other interesting questions.</p>
  1467. <p><a href="">The image</a> is cropped somewhat tightly, but they&#8217;re clearly eating Chinese food, the bench style and wall color are distinctive, and there&#8217;s a large picture hanging over their heads. So, I did the laziest thing I could possibly do: <a href="">I asked my Twitter followers if any of them recognized it</a>.</p>
  1469. <p>22 minutes later, <a href="">we had the answer from DF reader Jay P</a>: Hong&#8217;s Gourmet, in Saratoga, CA. <a href="">This image on Yelp</a> shows the same bench, same wall, and same picture on the wall. Next door to Hong&#8217;s Gourmet is <a href="">Masu Sushi</a>, whose sign is legibly reflected in the glass of the picture behind the Google engineers.<sup id="fnr1-2018-05-17"><a href="#fn1-2018-05-17">1</a></sup></p>
  1471. <p>My thanks to Jay P and everyone else who contributed to the thread on Twitter. Jay deserves the credit for cracking this, by going backwards from the Masu Sushi sign in the reflection.<sup id="fnr2-2018-05-17"><a href="#fn2-2018-05-17">2</a></sup> All I did was ask. The fact that I had an answer to my question in just 22 minutes shows that having a large follower count on Twitter is a bit of a super power. I honestly can’t think of another way to answer this question without Google PR’s help. I suppose, without Twitter, I could have just posted the question on Daring Fireball, and I might have gotten the same answer. But the threaded, public, instant nature of Twitter allowed for multiple people to contribute &#8212; we went from &#8220;<em>this might be the place</em>&#8221; to &#8220;<em>this is definitely the place</em>&#8221; in just a handful of minutes. Remarkable, really.</p>
  1473. <div class="footnotes">
  1474. <hr />
  1475. <ol>
  1476. <li id="fn1-2018-05-17">
  1477. <p>One weird detail is that the image from Google of the engineers <a href="">has been flipped horizontally</a>, so the reflection of the neighboring restaurant&#8217;s sign isn&#8217;t mirrored. My only guess as to why Google flipped this image is that they wanted Leviathan, the project lead, to have his name listed first in the caption.&nbsp;<a href="#fnr1-2018-05-17"  class="footnoteBackLink"  title="Jump back to footnote 1 in the text.">&#x21A9;&#xFE0E;</a></p>
  1478. </li>
  1479. <li id="fn2-2018-05-17">
  1480. <p>Solving this not from the decor of the restaurant but instead from the tiny reflection of the neighboring restaurant&#8217;s sign brings to mind one word: &#8220;<a href="">Enhance</a>.&#8221;&nbsp;<a href="#fnr2-2018-05-17"  class="footnoteBackLink"  title="Jump back to footnote 2 in the text.">&#x21A9;&#xFE0E;︎</a></p>
  1481. </li>
  1483. </ol>
  1484. </div>
  1488.    ]]></content>
  1489.  <title>★ The Restaurant Where Google Claims to Have Booked an Actual Meal Via Duplex</title></entry><entry>
  1491.    <link rel="alternate" type="text/html" href="" />
  1492. <link rel="shorturl" href="" />
  1493. <id>,2018://1.34854</id>
  1494. <published>2018-05-16T22:43:11Z</published>
  1495. <updated>2018-05-17T03:37:22Z</updated>
  1496. <author>
  1497. <name>John Gruber</name>
  1498. <uri></uri>
  1499. </author>
  1500. <summary type="text">Twitter may not care about a native Mac client, but the users of these apps, and the developers who make them, certainly do.</summary>
  1501. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1502. <p><a href="">&#8220;Apps of a Feather&#8221; &#8212; a joint statement from the developers of several top third-party Twitter clients</a>:</p>
  1504. <blockquote>
  1505.  <p><a href="">After August 16th, 2018</a>, “streaming services” at Twitter will
  1506. be removed. This means two things for third-party apps:</p>
  1508. <ol>
  1509. <li>Push notifications will no longer arrive</li>
  1510. <li>Timelines won’t refresh automatically</li>
  1511. </ol>
  1513. <p>If you use an app like <a href="">Talon</a>, <a href="">Tweetbot</a>, <a href="">Tweetings</a>, or
  1514. <a href="">Twitterrific</a>, there is no way for its developer to fix
  1515. these issues.</p>
  1517. <p>We are <em>incredibly eager</em> to update our apps. However, <em>despite
  1518. many requests for clarification and guidance, Twitter has not
  1519. provided a way for us to recreate the lost functionality</em>. We&#8217;ve
  1520. been waiting for <a href="">more than a year</a> and have had <a href="">one reprieve</a>.</p>
  1521. </blockquote>
  1523. <p>This antipathy to third-party clients is especially confounding considering that Twitter recently dropped support for their own native Mac client. As far as I&#8217;m aware, once this comes to pass next month, there will be no way to receive notifications of Twitter DMs on a Mac. None. (Twitter&#8217;s website doesn&#8217;t even support Safari&#8217;s desktop notification feature.) That&#8217;s just wacky.</p>
  1525. <p>Twitter management obviously wants to steer people to their first-party mobile app and desktop website. I get that. But they already have that: the overwhelming number of Twitter users use exactly those products to access the service. What Twitter management seems to be missing is that many of its most influential users &#8212; including yours truly, yes &#8212; have been on the platform a <em>long</em> time and have a high tendency to be among those who not just use, but depend upon third-party clients.</p>
  1527. <p>To me this is like finding out you&#8217;re now required to access email entirely through a web browser. Sure, lots of people already do it that way and either prefer it or think it&#8217;s <em>eh, just fine, who cares</em> &#8212; but a lot of others <em>hate</em> it and find it completely disruptive to longstanding workflows.</p>
  1529. <p>Twitter isn&#8217;t explicitly saying that they&#8217;re shutting down third-party clients, but I don&#8217;t know that it&#8217;s feasible for them to exist if they don&#8217;t have access to these APIs. It&#8217;s like breaking up with someone by being a jerk to them rather than telling them you&#8217;re breaking up.</p>
  1531. <p>I urge Twitter to reconsider this decision. Third-party clients account for a relatively small part of the Twitter ecosystem, but it&#8217;s an important one. Twitter may not care about a native Mac client, but the users of these apps, and the developers who make them, certainly do.</p>
  1535.    ]]></content>
  1536.  <title>★ The End of Third-Party Twitter Clients?</title></entry><entry>
  1538.    <link rel="alternate" type="text/html" href="" />
  1539. <link rel="shorturl" href="" />
  1540. <id>,2018://1.34823</id>
  1541. <published>2018-05-02T23:25:26Z</published>
  1542. <updated>2018-05-02T23:25:27Z</updated>
  1543. <author>
  1544. <name>John Gruber</name>
  1545. <uri></uri>
  1546. </author>
  1547. <summary type="text">Lobe is to CoreML what Illustrator was to PostScript — a profoundly powerful tool that exposes the underlying technology to non-experts through an intuitive visual interface.</summary>
  1548. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1549. <p><a href="">Lobe just launched publicly today</a>:</p>
  1551. <blockquote>
  1552.  <p>Lobe is an easy-to-use visual tool that lets you build custom
  1553. deep learning models, quickly train them, and ship them directly
  1554. in your app without writing any code. Start by dragging in a
  1555. folder of training examples from your desktop. Lobe automatically
  1556. builds you a custom deep learning model and begins training. When
  1557. you’re done, you can export a trained model and ship it directly
  1558. in your app.</p>
  1559. </blockquote>
  1561. <p>It&#8217;s a completely visual tool from designer <a href="">Mike Matas</a> and his co-founders Markus Beissinger and Adam Menges. I am always interested in <a href="">anything Matas does</a>, and Lobe is no exception.</p>
  1563. <p>You build and edit Lobe models through a web interface, and there&#8217;s a cloud API developers can use for finished models in production. But Lobe <em>also</em> exports to <a href="">CoreML</a> (for Apple platforms) and <a href="">TensorFlow</a>. My analogy: writing CoreML by hand is like writing PostScript by hand &#8212; possible, but only by a small number of talented experts. Lobe is to CoreML what Illustrator was to PostScript &#8212; a profoundly powerful tool that exposes the underlying technology to non-experts through an intuitive visual interface. Lobe looks utterly Matas-ian.</p>
  1565. <p>If you have any interest whatsoever in machine learning, drop what you&#8217;re doing right now and <a href="">watch their 13-minute introductory tour</a>. And if you&#8217;re not interested in machine learning, watch the video anyway and you&#8217;ll become interested in machine learning. It looks that amazing.</p>
  1569.    ]]></content>
  1570.  <title>★ Lobe</title></entry><entry>
  1572.    <link rel="alternate" type="text/html" href="" />
  1573. <link rel="shorturl" href="" />
  1574. <id>,2018://1.34814</id>
  1575. <published>2018-05-01T00:53:34Z</published>
  1576. <updated>2018-05-01T03:12:01Z</updated>
  1577. <author>
  1578. <name>John Gruber</name>
  1579. <uri></uri>
  1580. </author>
  1581. <summary type="text">It’s no longer called “Marzipan”, almost certainly isn’t coming this year, and is probably a declarative user interface API.</summary>
  1582. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1583. <p>Back in late December, Mark Gurman published an intriguing report at Bloomberg <a href="">regarding a secret cross-platform project at Apple</a>: </p>
  1585. <blockquote>
  1586.  <p>Starting as early as next year, software developers will be able
  1587. to design a single application that works with a touchscreen or
  1588. mouse and trackpad depending on whether it’s running on the iPhone
  1589. and iPad operating system or on Mac hardware, according to people
  1590. familiar with the matter. [&#8230;]</p>
  1592. <p>Apple is developing the strategy as part of the next major iOS and
  1593. macOS updates, said the people, who requested anonymity to discuss
  1594. an internal matter. Codenamed “Marzipan,” the secret project is
  1595. planned as a multiyear effort that will start rolling out as early
  1596. as next year and may be announced at the company’s annual
  1597. developers conference in the summer. The plans are still fluid,
  1598. the people said, so the implementation could change or the project
  1599. could still be canceled.</p>
  1600. </blockquote>
  1602. <p>I wrote <a href="">an extensive piece speculating on what it might really mean</a>.</p>
  1604. <p>This &#8220;Marzipan&#8221; rumor got a lot of people excited. But Gurman&#8217;s report is so light on technical details that the excitement is based mostly on what developers hope it could mean, not what&#8217;s actually been reported. The less specific the rumor, the easier it is to project your own wishes upon it. And, oddly perhaps, we haven&#8217;t seen any additional rumors or details about this project in the four months since Gurman&#8217;s original report.</p>
  1606. <p>I&#8217;ve heard a few things, from first- and second-hand sources. Mostly second-hand, to be honest, but they&#8217;re all consistent with each other.</p>
  1608. <p><strong>The Name:</strong> There is indeed an active cross-platform UI project at Apple for iOS and MacOS. It may have been codenamed &#8220;Marzipan&#8221; at one point, but if so only in its earliest days. My various little birdies only know of the project under a different name, which <a href="">hasn&#8217;t leaked publicly yet</a>. There are people at Apple who know about this project who first heard the name &#8220;Marzipan&#8221; when Gurman&#8217;s story was published.</p>
  1610. <p><strong>What Is It?</strong> I don&#8217;t have extensive details, but basically it sounds like a declarative control API. The general idea is that rather than writing classic procedural code to, say, make a button, then configure the button, then position the button inside a view, you instead declare the button and its attributes using some other form. HTML is probably the most easily understood example. In HTML you don&#8217;t procedurally create elements like paragraphs, images, and tables &#8212; you declare them with tags and attributes in markup. There&#8217;s an industry-wide trend toward declaration, perhaps best exemplified by <a href="">React</a>, that could be influencing Apple in this direction.</p>
  1612. <p>There&#8217;s nothing inherently cross-platform about a declarative control API. But it makes sense that if Apple believes that (a) iOS and MacOS should have declarative control APIs, and (b) they should address the problem of abstracting the API differences between UIKit (iOS) and AppKit (MacOS), they would tackle them at the same time. Or perhaps the logic is simply that if they&#8217;re going to create a cross-platform UI framework, the basis for that framework should be a declarative user interface.</p>
  1614. <p><strong>When:</strong> I&#8217;m nearly certain this project is not debuting at WWDC 2018 in June, and I doubt that 2018 was on the table in December. It&#8217;s a 2019 thing, for MacOS 10.15 and iOS 13.<sup id="fnr1-2018-04-30"><a href="#fn1-2018-04-30">1</a></sup> I would set your expectations accordingly for this year&#8217;s WWDC.</p>
  1616. <div class="footnotes">
  1617. <hr />
  1618. <ol>
  1619. <li id="fn1-2018-04-30">
  1620. <p>My guess is this is all part of the updated UI for iOS 13 coming next year.&nbsp;<a href="#fnr1-2018-04-30"  class="footnoteBackLink"  title="Jump back to footnote 1 in the text.">&#x21A9;&#xFE0E;</a></p>
  1621. </li>
  1622. </ol>
  1623. </div>
  1627.    ]]></content>
  1628.  <title>★ Scuttlebutt Regarding Apple’s Cross-Platform UI Project</title></entry></feed><!-- THE END -->

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 Atom 1.0" 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:

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