Congratulations!

[Valid RSS] This is a valid RSS feed.

Recommendations

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

Source: http://mjtsai.com/blog/comments/feed/

  1. <?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
  2. xmlns:content="http://purl.org/rss/1.0/modules/content/"
  3. xmlns:dc="http://purl.org/dc/elements/1.1/"
  4. xmlns:atom="http://www.w3.org/2005/Atom"
  5. xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
  6. >
  7. <channel>
  8. <title>
  9. Comments for Michael Tsai </title>
  10. <atom:link href="https://mjtsai.com/blog/comments/feed/" rel="self" type="application/rss+xml" />
  11. <link>https://mjtsai.com/blog</link>
  12. <description></description>
  13. <lastBuildDate>Sun, 28 Apr 2024 17:51:53 +0000</lastBuildDate>
  14. <sy:updatePeriod>
  15. hourly </sy:updatePeriod>
  16. <sy:updateFrequency>
  17. 1 </sy:updateFrequency>
  18. <generator>https://wordpress.org/?v=6.2.2</generator>
  19. <item>
  20. <title>
  21. Comment on macOS 14.4.1 by Mac Folklore Radio </title>
  22. <link>https://mjtsai.com/blog/2024/03/25/macos-14-4-1/#comment-4079756</link>
  23.  
  24. <dc:creator><![CDATA[Mac Folklore Radio]]></dc:creator>
  25. <pubDate>Sun, 28 Apr 2024 17:51:53 +0000</pubDate>
  26. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42631#comment-4079756</guid>
  27.  
  28. <description><![CDATA[Ah, USB-C. I can&#039;t wait for USB-D which will purportedly solve these problems and create even more.
  29.  
  30. Since I&#039;m never updating again until I buy new hardware, let it be known that 14.4.1 still has text drawing bugs. If you write long e-mails (I do) it&#039;s difficult to miss. Whole paragraphs jump around while others disappear. Mac OS X—oh well, it was good while it lasted. :\
  31.  
  32. Even more annoying, I&#039;ve never had my cursor disappear altogether, and so frequently, as I have in 14.4.1. I wanted to blame Electron before it started happening in the Finder, too. Killing the WindowServer and logging back in helps for a while.]]></description>
  33. <content:encoded><![CDATA[<p>Ah, USB-C. I can't wait for USB-D which will purportedly solve these problems and create even more.</p>
  34. <p>Since I'm never updating again until I buy new hardware, let it be known that 14.4.1 still has text drawing bugs. If you write long e-mails (I do) it's difficult to miss. Whole paragraphs jump around while others disappear. Mac OS X—oh well, it was good while it lasted. :\</p>
  35. <p>Even more annoying, I've never had my cursor disappear altogether, and so frequently, as I have in 14.4.1. I wanted to blame Electron before it started happening in the Finder, too. Killing the WindowServer and logging back in helps for a while.</p>
  36. ]]></content:encoded>
  37. </item>
  38. <item>
  39. <title>
  40. Comment on Janky Apple ID Security by Lee Hinde </title>
  41. <link>https://mjtsai.com/blog/2024/04/26/janky-apple-id-security/#comment-4079654</link>
  42.  
  43. <dc:creator><![CDATA[Lee Hinde]]></dc:creator>
  44. <pubDate>Sun, 28 Apr 2024 15:44:00 +0000</pubDate>
  45. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42969#comment-4079654</guid>
  46.  
  47. <description><![CDATA[While all this is going on users were probably getting &quot;you need to log into iCloud&#039; alerts every 30 seconds. So incredibly annoying when you want to do exactly that.
  48.  
  49. Not this but related is the lockout that Chels referred to. My very old mother bricked her iPad because she tried to many times to log in. The best we could do was wipe it with her iCloud id and start over. Maybe 1% of the Apple&#039;s user base needs this level of draconian, paternalistic &quot;protection.&quot;]]></description>
  50. <content:encoded><![CDATA[<p>While all this is going on users were probably getting "you need to log into iCloud' alerts every 30 seconds. So incredibly annoying when you want to do exactly that.</p>
  51. <p>Not this but related is the lockout that Chels referred to. My very old mother bricked her iPad because she tried to many times to log in. The best we could do was wipe it with her iCloud id and start over. Maybe 1% of the Apple's user base needs this level of draconian, paternalistic "protection."</p>
  52. ]]></content:encoded>
  53. </item>
  54. <item>
  55. <title>
  56. Comment on Yet More App Store Search Ads by 504: Too Much Apple in My Apple </title>
  57. <link>https://mjtsai.com/blog/2022/08/02/yet-more-app-store-search-ads/#comment-4079638</link>
  58.  
  59. <dc:creator><![CDATA[504: Too Much Apple in My Apple]]></dc:creator>
  60. <pubDate>Sun, 28 Apr 2024 15:15:02 +0000</pubDate>
  61. <guid isPermaLink="false">https://mjtsai.com/blog/?p=36644#comment-4079638</guid>
  62.  
  63. <description><![CDATA[[&#8230;] MJ Tsai [&#8230;]]]></description>
  64. <content:encoded><![CDATA[<p>[&#8230;] MJ Tsai [&#8230;]</p>
  65. ]]></content:encoded>
  66. </item>
  67. <item>
  68. <title>
  69. Comment on Janky Apple ID Security by Patrick </title>
  70. <link>https://mjtsai.com/blog/2024/04/26/janky-apple-id-security/#comment-4079626</link>
  71.  
  72. <dc:creator><![CDATA[Patrick]]></dc:creator>
  73. <pubDate>Sun, 28 Apr 2024 14:56:50 +0000</pubDate>
  74. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42969#comment-4079626</guid>
  75.  
  76. <description><![CDATA[Today (Sunday April 28), I&#039;m locked out again.
  77.  
  78. I was locked out like everyone else on Friday. Same deal, had to reset my password.  Now I&#039;m going through the same thing except that I apparently need to wait 1 hour due to Stolen Device Protection—which did not happen the first time.]]></description>
  79. <content:encoded><![CDATA[<p>Today (Sunday April 28), I'm locked out again.</p>
  80. <p>I was locked out like everyone else on Friday. Same deal, had to reset my password.  Now I'm going through the same thing except that I apparently need to wait 1 hour due to Stolen Device Protection—which did not happen the first time.</p>
  81. ]]></content:encoded>
  82. </item>
  83. <item>
  84. <title>
  85. Comment on Janky Apple ID Security by MB </title>
  86. <link>https://mjtsai.com/blog/2024/04/26/janky-apple-id-security/#comment-4079527</link>
  87.  
  88. <dc:creator><![CDATA[MB]]></dc:creator>
  89. <pubDate>Sun, 28 Apr 2024 11:45:52 +0000</pubDate>
  90. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42969#comment-4079527</guid>
  91.  
  92. <description><![CDATA[My iPhone showed this today. To confirm identity, it asked me to enter my phone number giving just the ending digits. Then it only allowed me to enter a US number (my AppleID is US-based but my phone number happens to be in EU). So if it persisted, I would have been really screwed. Real confidence builder, that.
  93.  
  94. Luckily, right away I unlocked my iPad with FaceID, and that seems to have pacified the iPhone. I have seen no trace of the account locking since, knock on wood.
  95.  
  96. Interestingly enough, it happened as I was using the phone to try to initialize (for the first time in a month) a HomePod, bricked since 17.3 and plagued by the much-discussed -5320 setup error. So maybe that login attempt triggered it.
  97.  
  98. My significant locations shows Home (twice), and some third place which does not seem significant. It also mentions 127 others but I am not worthy enough to view them.]]></description>
  99. <content:encoded><![CDATA[<p>My iPhone showed this today. To confirm identity, it asked me to enter my phone number giving just the ending digits. Then it only allowed me to enter a US number (my AppleID is US-based but my phone number happens to be in EU). So if it persisted, I would have been really screwed. Real confidence builder, that.</p>
  100. <p>Luckily, right away I unlocked my iPad with FaceID, and that seems to have pacified the iPhone. I have seen no trace of the account locking since, knock on wood.</p>
  101. <p>Interestingly enough, it happened as I was using the phone to try to initialize (for the first time in a month) a HomePod, bricked since 17.3 and plagued by the much-discussed -5320 setup error. So maybe that login attempt triggered it.</p>
  102. <p>My significant locations shows Home (twice), and some third place which does not seem significant. It also mentions 127 others but I am not worthy enough to view them.</p>
  103. ]]></content:encoded>
  104. </item>
  105. <item>
  106. <title>
  107. Comment on Janky Apple ID Security by Mike </title>
  108. <link>https://mjtsai.com/blog/2024/04/26/janky-apple-id-security/#comment-4079283</link>
  109.  
  110. <dc:creator><![CDATA[Mike]]></dc:creator>
  111. <pubDate>Sun, 28 Apr 2024 05:44:59 +0000</pubDate>
  112. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42969#comment-4079283</guid>
  113.  
  114. <description><![CDATA[Same thing here, but this happened while on hotel wifi, so had me in more of a panic than I would&#039;ve been if at home.
  115.  
  116. 30hrs later and back at home; everything is mostly normal, except Watch - won&#039;t accept new password, keeps saying it&#039;s wrong, and gives me this effed-up fail screen.
  117. https://pbs.twimg.com/media/GMOnBILWYAAxLn0.jpg
  118.  
  119. Oh - and my &quot;significant locations&quot;: none. Even though I spend ~20hrs/day at home, at least 300days/yr. If that&#039;s not &quot;significant&quot;....pleaes, Apple, tell me what is.]]></description>
  120. <content:encoded><![CDATA[<p>Same thing here, but this happened while on hotel wifi, so had me in more of a panic than I would've been if at home.</p>
  121. <p>30hrs later and back at home; everything is mostly normal, except Watch - won't accept new password, keeps saying it's wrong, and gives me this effed-up fail screen.<br />
  122. <a href="https://pbs.twimg.com/media/GMOnBILWYAAxLn0.jpg" rel="nofollow ugc">https://pbs.twimg.com/media/GMOnBILWYAAxLn0.jpg</a></p>
  123. <p>Oh - and my "significant locations": none. Even though I spend ~20hrs/day at home, at least 300days/yr. If that's not "significant"....pleaes, Apple, tell me what is.</p>
  124. ]]></content:encoded>
  125. </item>
  126. <item>
  127. <title>
  128. Comment on Janky Apple ID Security by Ranjithkumar Matheswaran </title>
  129. <link>https://mjtsai.com/blog/2024/04/26/janky-apple-id-security/#comment-4079207</link>
  130.  
  131. <dc:creator><![CDATA[Ranjithkumar Matheswaran]]></dc:creator>
  132. <pubDate>Sun, 28 Apr 2024 03:39:18 +0000</pubDate>
  133. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42969#comment-4079207</guid>
  134.  
  135. <description><![CDATA[Somehow I ended up going for Account recovery. Now I have to wait for 24 hours before continuing to reset my password. It&#039;s already been 22 hours passed by. I am waiting 2 more hours for the cooling period to get over.]]></description>
  136. <content:encoded><![CDATA[<p>Somehow I ended up going for Account recovery. Now I have to wait for 24 hours before continuing to reset my password. It's already been 22 hours passed by. I am waiting 2 more hours for the cooling period to get over.</p>
  137. ]]></content:encoded>
  138. </item>
  139. <item>
  140. <title>
  141. Comment on Janky Apple ID Security by Harald Striepe </title>
  142. <link>https://mjtsai.com/blog/2024/04/26/janky-apple-id-security/#comment-4079194</link>
  143.  
  144. <dc:creator><![CDATA[Harald Striepe]]></dc:creator>
  145. <pubDate>Sun, 28 Apr 2024 02:51:29 +0000</pubDate>
  146. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42969#comment-4079194</guid>
  147.  
  148. <description><![CDATA[DITTO! I reset last night and was hit again this AM. Apple Support was unaware.
  149. Apparently, any lingirng device not updated pinging iCloud with an outdated token in its sleep will trigger the problem AGAIN!.
  150.  
  151. I have a lot of devices:  8-10 Macs (a couple haven&#039;t been powered up for a while,) AppleTVs,  eight HomePods, two iPads, two iPhones. Even my Apple Watch was complaining. My curated list of App Specific passwords was wiped and needs to be restored and entered on all devices.
  152.  
  153. Is it time to diversify? First Tesla, now Apple is becoming non-grata!]]></description>
  154. <content:encoded><![CDATA[<p>DITTO! I reset last night and was hit again this AM. Apple Support was unaware.<br />
  155. Apparently, any lingirng device not updated pinging iCloud with an outdated token in its sleep will trigger the problem AGAIN!.</p>
  156. <p>I have a lot of devices:  8-10 Macs (a couple haven't been powered up for a while,) AppleTVs,  eight HomePods, two iPads, two iPhones. Even my Apple Watch was complaining. My curated list of App Specific passwords was wiped and needs to be restored and entered on all devices.</p>
  157. <p>Is it time to diversify? First Tesla, now Apple is becoming non-grata!</p>
  158. ]]></content:encoded>
  159. </item>
  160. <item>
  161. <title>
  162. Comment on Gambling Ads on App Store Product Pages by 511: Moving to Antarctica </title>
  163. <link>https://mjtsai.com/blog/2022/10/31/gambling-ads-on-app-store-product-pages/#comment-4079173</link>
  164.  
  165. <dc:creator><![CDATA[511: Moving to Antarctica]]></dc:creator>
  166. <pubDate>Sun, 28 Apr 2024 02:05:51 +0000</pubDate>
  167. <guid isPermaLink="false">https://mjtsai.com/blog/?p=37505#comment-4079173</guid>
  168.  
  169. <description><![CDATA[[&#8230;] Michael Tsai [&#8230;]]]></description>
  170. <content:encoded><![CDATA[<p>[&#8230;] Michael Tsai [&#8230;]</p>
  171. ]]></content:encoded>
  172. </item>
  173. <item>
  174. <title>
  175. Comment on Janky Apple ID Security by Si </title>
  176. <link>https://mjtsai.com/blog/2024/04/26/janky-apple-id-security/#comment-4079122</link>
  177.  
  178. <dc:creator><![CDATA[Si]]></dc:creator>
  179. <pubDate>Sat, 27 Apr 2024 23:37:08 +0000</pubDate>
  180. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42969#comment-4079122</guid>
  181.  
  182. <description><![CDATA[This is interesting – hasn&#039;t happened to me, but earlier this week I had, all of a sudden, news that an iPhone and an Apple Watch was added to my iMessage – checked and it was my existing devices.  Something&#039;s gone wrong with Apple but nobody for sure knows what.]]></description>
  183. <content:encoded><![CDATA[<p>This is interesting – hasn't happened to me, but earlier this week I had, all of a sudden, news that an iPhone and an Apple Watch was added to my iMessage – checked and it was my existing devices.  Something's gone wrong with Apple but nobody for sure knows what.</p>
  184. ]]></content:encoded>
  185. </item>
  186. <item>
  187. <title>
  188. Comment on Janky Apple ID Security by Bob </title>
  189. <link>https://mjtsai.com/blog/2024/04/26/janky-apple-id-security/#comment-4079091</link>
  190.  
  191. <dc:creator><![CDATA[Bob]]></dc:creator>
  192. <pubDate>Sat, 27 Apr 2024 22:19:17 +0000</pubDate>
  193. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42969#comment-4079091</guid>
  194.  
  195. <description><![CDATA[So glad I don’t use any cloud anything.]]></description>
  196. <content:encoded><![CDATA[<p>So glad I don’t use any cloud anything.</p>
  197. ]]></content:encoded>
  198. </item>
  199. <item>
  200. <title>
  201. Comment on Janky Apple ID Security by Jim T </title>
  202. <link>https://mjtsai.com/blog/2024/04/26/janky-apple-id-security/#comment-4079074</link>
  203.  
  204. <dc:creator><![CDATA[Jim T]]></dc:creator>
  205. <pubDate>Sat, 27 Apr 2024 21:52:25 +0000</pubDate>
  206. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42969#comment-4079074</guid>
  207.  
  208. <description><![CDATA[I got locked out and I called Apple. They didn&#039;t know but walked me through fixing the issue.
  209.  
  210. It was a bit convoluted but the iPhone/iPad are back to normal. (what ever that is)]]></description>
  211. <content:encoded><![CDATA[<p>I got locked out and I called Apple. They didn't know but walked me through fixing the issue.</p>
  212. <p>It was a bit convoluted but the iPhone/iPad are back to normal. (what ever that is)</p>
  213. ]]></content:encoded>
  214. </item>
  215. <item>
  216. <title>
  217. Comment on Janky Apple ID Security by Rob </title>
  218. <link>https://mjtsai.com/blog/2024/04/26/janky-apple-id-security/#comment-4079069</link>
  219.  
  220. <dc:creator><![CDATA[Rob]]></dc:creator>
  221. <pubDate>Sat, 27 Apr 2024 21:41:36 +0000</pubDate>
  222. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42969#comment-4079069</guid>
  223.  
  224. <description><![CDATA[Same here. Especially fun getting the popup on my Apple TV while my wife and I were trying to watch something.]]></description>
  225. <content:encoded><![CDATA[<p>Same here. Especially fun getting the popup on my Apple TV while my wife and I were trying to watch something.</p>
  226. ]]></content:encoded>
  227. </item>
  228. <item>
  229. <title>
  230. Comment on Janky Apple ID Security by Chels </title>
  231. <link>https://mjtsai.com/blog/2024/04/26/janky-apple-id-security/#comment-4079065</link>
  232.  
  233. <dc:creator><![CDATA[Chels]]></dc:creator>
  234. <pubDate>Sat, 27 Apr 2024 21:34:34 +0000</pubDate>
  235. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42969#comment-4079065</guid>
  236.  
  237. <description><![CDATA[I especially love the part where Apple&#039;s got their support staff ignoring the growing press around this, pretending like nothing happened, and actually implying to customers that this was user initiated. I&#039;ve been trying to help out a buddy who kept getting hit with verification server errors when trying to reset his password on his iPhone, and after giving up and trying from a computer, got stuck with a 24-72 hour lock that&#039;s going to hurt him financially due to work files on iCloud being inaccessible.
  238.  
  239. We tried different ways of explaining this to more than one support person, and it&#039;s the same line every time: there&#039;s no escalation path, just wait it out, you wanted this, so we will make sure you keep it. I&#039;ve run technical support teams in the past, and worked in tech for decades. I know better than to blame the support reps themselves (they&#039;re clearly just using the lines they&#039;ve been fed), but I hope the person who decided to put their support personnel and Apple&#039;s customers through this does some self-reflecting. Gaslighting customers when there&#039;s a known issue is not cute.]]></description>
  240. <content:encoded><![CDATA[<p>I especially love the part where Apple's got their support staff ignoring the growing press around this, pretending like nothing happened, and actually implying to customers that this was user initiated. I've been trying to help out a buddy who kept getting hit with verification server errors when trying to reset his password on his iPhone, and after giving up and trying from a computer, got stuck with a 24-72 hour lock that's going to hurt him financially due to work files on iCloud being inaccessible.</p>
  241. <p>We tried different ways of explaining this to more than one support person, and it's the same line every time: there's no escalation path, just wait it out, you wanted this, so we will make sure you keep it. I've run technical support teams in the past, and worked in tech for decades. I know better than to blame the support reps themselves (they're clearly just using the lines they've been fed), but I hope the person who decided to put their support personnel and Apple's customers through this does some self-reflecting. Gaslighting customers when there's a known issue is not cute.</p>
  242. ]]></content:encoded>
  243. </item>
  244. <item>
  245. <title>
  246. Comment on Janky Apple ID Security by Ken </title>
  247. <link>https://mjtsai.com/blog/2024/04/26/janky-apple-id-security/#comment-4079057</link>
  248.  
  249. <dc:creator><![CDATA[Ken]]></dc:creator>
  250. <pubDate>Sat, 27 Apr 2024 21:13:17 +0000</pubDate>
  251. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42969#comment-4079057</guid>
  252.  
  253. <description><![CDATA[I’m relieved to know it’s not just me. My iCloud account has been locking almost daily for a few months now. It doesn’t make me change my passwords, but it does have me go through the unlock process each time. I’ve signed out of and back into all devices, done everything I can think of to no avail. I couldn’t find anything about this issue except that it probably meant someone was repeatedly trying to log into my account. Every day. For weeks. From all I’m seeing here, it’s becoming apparent that the issue is really at Apple’s end.]]></description>
  254. <content:encoded><![CDATA[<p>I’m relieved to know it’s not just me. My iCloud account has been locking almost daily for a few months now. It doesn’t make me change my passwords, but it does have me go through the unlock process each time. I’ve signed out of and back into all devices, done everything I can think of to no avail. I couldn’t find anything about this issue except that it probably meant someone was repeatedly trying to log into my account. Every day. For weeks. From all I’m seeing here, it’s becoming apparent that the issue is really at Apple’s end.</p>
  255. ]]></content:encoded>
  256. </item>
  257. <item>
  258. <title>
  259. Comment on Janky Apple ID Security by Sean </title>
  260. <link>https://mjtsai.com/blog/2024/04/26/janky-apple-id-security/#comment-4079043</link>
  261.  
  262. <dc:creator><![CDATA[Sean]]></dc:creator>
  263. <pubDate>Sat, 27 Apr 2024 20:58:49 +0000</pubDate>
  264. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42969#comment-4079043</guid>
  265.  
  266. <description><![CDATA[Happened to me too. Glad others are reporting. I only have one Apple ID which is a personal email address. I have never enabled Stolen Device Protection. Even still, very disruptive, thought something bad was happening. I contacted Apple Support at 11 AM PST and they were not aware of any widespread issues. It wants me to reset my password. I am resisting. I am hoping this will be nullified by Sunday night. If it is not, I will give in and change my Apple ID password. Very disappointing, I really wonder if this could be related to the rumored Apple ID account system overhaul for iOS 18.]]></description>
  267. <content:encoded><![CDATA[<p>Happened to me too. Glad others are reporting. I only have one Apple ID which is a personal email address. I have never enabled Stolen Device Protection. Even still, very disruptive, thought something bad was happening. I contacted Apple Support at 11 AM PST and they were not aware of any widespread issues. It wants me to reset my password. I am resisting. I am hoping this will be nullified by Sunday night. If it is not, I will give in and change my Apple ID password. Very disappointing, I really wonder if this could be related to the rumored Apple ID account system overhaul for iOS 18.</p>
  268. ]]></content:encoded>
  269. </item>
  270. <item>
  271. <title>
  272. Comment on Janky Apple ID Security by Disappointed MacUser </title>
  273. <link>https://mjtsai.com/blog/2024/04/26/janky-apple-id-security/#comment-4078999</link>
  274.  
  275. <dc:creator><![CDATA[Disappointed MacUser]]></dc:creator>
  276. <pubDate>Sat, 27 Apr 2024 20:15:57 +0000</pubDate>
  277. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42969#comment-4078999</guid>
  278.  
  279. <description><![CDATA[Till Apple doesn&#039;t explain it
  280. A quick summary of what isn&#039;t the cause so far, after reading several articles and messages :
  281.  
  282. No email ending in .me or .Mac because other emails were involved
  283.  
  284. No Stolen Device Protection, many people didn&#039;t even had it ON, but I turned mine OFF because if you are not at home it&#039;s a longer nightmare from what someone wrote
  285.  
  286. No old iCloud password , I reset mine VOLUNTARILY in January.
  287.  
  288.  
  289. It&#039;s happening everywhere, US, Canada, UK, Sweden and Europe in general]]></description>
  290. <content:encoded><![CDATA[<p>Till Apple doesn't explain it<br />
  291. A quick summary of what isn't the cause so far, after reading several articles and messages :</p>
  292. <p>No email ending in .me or .Mac because other emails were involved</p>
  293. <p>No Stolen Device Protection, many people didn't even had it ON, but I turned mine OFF because if you are not at home it's a longer nightmare from what someone wrote</p>
  294. <p>No old iCloud password , I reset mine VOLUNTARILY in January.</p>
  295. <p>It's happening everywhere, US, Canada, UK, Sweden and Europe in general</p>
  296. ]]></content:encoded>
  297. </item>
  298. <item>
  299. <title>
  300. Comment on Janky Apple ID Security by Ben Kennedy </title>
  301. <link>https://mjtsai.com/blog/2024/04/26/janky-apple-id-security/#comment-4078924</link>
  302.  
  303. <dc:creator><![CDATA[Ben Kennedy]]></dc:creator>
  304. <pubDate>Sat, 27 Apr 2024 18:38:08 +0000</pubDate>
  305. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42969#comment-4078924</guid>
  306.  
  307. <description><![CDATA[Fortunately I haven&#039;t been locked out (yet), but I did get a spontaneous alert on my iPhone last night informing me that my phone number had been added to iMessage (which it already was).]]></description>
  308. <content:encoded><![CDATA[<p>Fortunately I haven't been locked out (yet), but I did get a spontaneous alert on my iPhone last night informing me that my phone number had been added to iMessage (which it already was).</p>
  309. ]]></content:encoded>
  310. </item>
  311. <item>
  312. <title>
  313. Comment on Janky Apple ID Security by vintner </title>
  314. <link>https://mjtsai.com/blog/2024/04/26/janky-apple-id-security/#comment-4078855</link>
  315.  
  316. <dc:creator><![CDATA[vintner]]></dc:creator>
  317. <pubDate>Sat, 27 Apr 2024 17:11:46 +0000</pubDate>
  318. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42969#comment-4078855</guid>
  319.  
  320. <description><![CDATA[I didn&#039;t know about that Significant Locations page in Settings, mine similarly only shows a location I went to once weeks ago.
  321.  
  322. I additionally have iPhone Analytics off, so I&#039;m curious why that and other switches were not only enabled in System Services but have purple arrowhead badges indicating recent location access.]]></description>
  323. <content:encoded><![CDATA[<p>I didn't know about that Significant Locations page in Settings, mine similarly only shows a location I went to once weeks ago.</p>
  324. <p>I additionally have iPhone Analytics off, so I'm curious why that and other switches were not only enabled in System Services but have purple arrowhead badges indicating recent location access.</p>
  325. ]]></content:encoded>
  326. </item>
  327. <item>
  328. <title>
  329. Comment on Janky Apple ID Security by Bob Arnold </title>
  330. <link>https://mjtsai.com/blog/2024/04/26/janky-apple-id-security/#comment-4078814</link>
  331.  
  332. <dc:creator><![CDATA[Bob Arnold]]></dc:creator>
  333. <pubDate>Sat, 27 Apr 2024 16:16:49 +0000</pubDate>
  334. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42969#comment-4078814</guid>
  335.  
  336. <description><![CDATA[The same thing happened to me today. And this is a humongous pain as you have to redo all your app-specific passwords, it forks up Apple Music and if you have many computer, they all are messed up.]]></description>
  337. <content:encoded><![CDATA[<p>The same thing happened to me today. And this is a humongous pain as you have to redo all your app-specific passwords, it forks up Apple Music and if you have many computer, they all are messed up.</p>
  338. ]]></content:encoded>
  339. </item>
  340. <item>
  341. <title>
  342. Comment on Janky Apple ID Security by KM </title>
  343. <link>https://mjtsai.com/blog/2024/04/26/janky-apple-id-security/#comment-4078759</link>
  344.  
  345. <dc:creator><![CDATA[KM]]></dc:creator>
  346. <pubDate>Sat, 27 Apr 2024 14:37:43 +0000</pubDate>
  347. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42969#comment-4078759</guid>
  348.  
  349. <description><![CDATA[Same here. Have not been able to get back in since last night. Contacted Apple and they cannot get me in. I can’t change password because it’s linked to my iCloud account. Also cannot create a new iCloud account]]></description>
  350. <content:encoded><![CDATA[<p>Same here. Have not been able to get back in since last night. Contacted Apple and they cannot get me in. I can’t change password because it’s linked to my iCloud account. Also cannot create a new iCloud account</p>
  351. ]]></content:encoded>
  352. </item>
  353. <item>
  354. <title>
  355. Comment on Janky Apple ID Security by Michael J. </title>
  356. <link>https://mjtsai.com/blog/2024/04/26/janky-apple-id-security/#comment-4078754</link>
  357.  
  358. <dc:creator><![CDATA[Michael J.]]></dc:creator>
  359. <pubDate>Sat, 27 Apr 2024 14:29:23 +0000</pubDate>
  360. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42969#comment-4078754</guid>
  361.  
  362. <description><![CDATA[As I&#039;ve come to rely on iCloud more -- Ulysses writing projects, medical records shared between desktop and laptop, snapshot photo archives, among many other uses -- this terrifies me. Getting permanently locked out of my Apple ID would be devastating. I realize this is not exactly what we&#039;re talking about here, but it has happened to people, and the recent shenanigans sort of points to the potential of it. It&#039;s not clear to me that we (i.e. humans) can build and maintain systems of the complexity we&#039;ve unleashed. The pace of &quot;improvement&quot; is greater than the pace of maintenance, IMO. The fact that all this is managed by Eddie Cue, noted happy-go-lucky sports and race car enthusiast, is not encouraging. iCloud shouldn&#039;t be under &quot;Services,&quot; but under some sort of core technology / infrastructure tech lead, more like the profile of Johny Srouji.]]></description>
  363. <content:encoded><![CDATA[<p>As I've come to rely on iCloud more -- Ulysses writing projects, medical records shared between desktop and laptop, snapshot photo archives, among many other uses -- this terrifies me. Getting permanently locked out of my Apple ID would be devastating. I realize this is not exactly what we're talking about here, but it has happened to people, and the recent shenanigans sort of points to the potential of it. It's not clear to me that we (i.e. humans) can build and maintain systems of the complexity we've unleashed. The pace of "improvement" is greater than the pace of maintenance, IMO. The fact that all this is managed by Eddie Cue, noted happy-go-lucky sports and race car enthusiast, is not encouraging. iCloud shouldn't be under "Services," but under some sort of core technology / infrastructure tech lead, more like the profile of Johny Srouji.</p>
  364. ]]></content:encoded>
  365. </item>
  366. <item>
  367. <title>
  368. Comment on Janky Apple ID Security by Warner Crocker </title>
  369. <link>https://mjtsai.com/blog/2024/04/26/janky-apple-id-security/#comment-4078697</link>
  370.  
  371. <dc:creator><![CDATA[Warner Crocker]]></dc:creator>
  372. <pubDate>Sat, 27 Apr 2024 12:45:11 +0000</pubDate>
  373. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42969#comment-4078697</guid>
  374.  
  375. <description><![CDATA[The same thing hit me last night seeing it first while watching Apple TV then all devices. I do not have Stolen Device Protection turned on. Whatever glitch caused this it also wiped out ALL App Specific Passwords I have. Noticing this morning that things like Reminders are syncing slowly if at all.]]></description>
  376. <content:encoded><![CDATA[<p>The same thing hit me last night seeing it first while watching Apple TV then all devices. I do not have Stolen Device Protection turned on. Whatever glitch caused this it also wiped out ALL App Specific Passwords I have. Noticing this morning that things like Reminders are syncing slowly if at all.</p>
  377. ]]></content:encoded>
  378. </item>
  379. <item>
  380. <title>
  381. Comment on TikTok Ban by Plume </title>
  382. <link>https://mjtsai.com/blog/2024/04/24/tiktok-ban/#comment-4078504</link>
  383.  
  384. <dc:creator><![CDATA[Plume]]></dc:creator>
  385. <pubDate>Sat, 27 Apr 2024 08:23:27 +0000</pubDate>
  386. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42914#comment-4078504</guid>
  387.  
  388. <description><![CDATA[It&#039;s still true that China is already doing all of that. Retaliation is not much of a threat if they&#039;re anyway doing it already. As you said, all of this was set into motion a long time ago.]]></description>
  389. <content:encoded><![CDATA[<p>It's still true that China is already doing all of that. Retaliation is not much of a threat if they're anyway doing it already. As you said, all of this was set into motion a long time ago.</p>
  390. ]]></content:encoded>
  391. </item>
  392. <item>
  393. <title>
  394. Comment on Scam Authenticator App Steals QR Codes by 525: The Glory Speakers </title>
  395. <link>https://mjtsai.com/blog/2023/02/21/scam-authenticator-app-steals-qr-codes/#comment-4078478</link>
  396.  
  397. <dc:creator><![CDATA[525: The Glory Speakers]]></dc:creator>
  398. <pubDate>Sat, 27 Apr 2024 07:38:29 +0000</pubDate>
  399. <guid isPermaLink="false">https://mjtsai.com/blog/?p=38550#comment-4078478</guid>
  400.  
  401. <description><![CDATA[[&#8230;] Scam Authenticator App Steals QR Codes <img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f631.png" alt="😱" class="wp-smiley" style="height: 1em; max-height: 1em;" /> [&#8230;]]]></description>
  402. <content:encoded><![CDATA[<p>[&#8230;] Scam Authenticator App Steals QR Codes 😱 [&#8230;]</p>
  403. ]]></content:encoded>
  404. </item>
  405. <item>
  406. <title>
  407. Comment on Janky Apple ID Security by Kirk </title>
  408. <link>https://mjtsai.com/blog/2024/04/26/janky-apple-id-security/#comment-4078464</link>
  409.  
  410. <dc:creator><![CDATA[Kirk]]></dc:creator>
  411. <pubDate>Sat, 27 Apr 2024 07:17:40 +0000</pubDate>
  412. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42969#comment-4078464</guid>
  413.  
  414. <description><![CDATA[This just happened to me when I got up Saturday morning in the UK.  After resetting my Apple ID password on my phone, I have to do it on my watch, my iPad mini, my iPad Pro, my iMac, my MacBook Air, my Mac mini, my Apple TV… i’m not sure if I also have to do it individually on my five HomePods – four of them in two stereo pairs, which might mean just one password reset per pair.  Not to mention apps specific passwords for a couple of apps I use. Thank you Apple for making me waste an hour or two on Saturday morning.]]></description>
  415. <content:encoded><![CDATA[<p>This just happened to me when I got up Saturday morning in the UK.  After resetting my Apple ID password on my phone, I have to do it on my watch, my iPad mini, my iPad Pro, my iMac, my MacBook Air, my Mac mini, my Apple TV… i’m not sure if I also have to do it individually on my five HomePods – four of them in two stereo pairs, which might mean just one password reset per pair.  Not to mention apps specific passwords for a couple of apps I use. Thank you Apple for making me waste an hour or two on Saturday morning.</p>
  416. ]]></content:encoded>
  417. </item>
  418. <item>
  419. <title>
  420. Comment on Janky Apple ID Security by Max Schaefer </title>
  421. <link>https://mjtsai.com/blog/2024/04/26/janky-apple-id-security/#comment-4078445</link>
  422.  
  423. <dc:creator><![CDATA[Max Schaefer]]></dc:creator>
  424. <pubDate>Sat, 27 Apr 2024 06:47:16 +0000</pubDate>
  425. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42969#comment-4078445</guid>
  426.  
  427. <description><![CDATA[Snap, down to it saying I was not at a significant location when I’m at home.]]></description>
  428. <content:encoded><![CDATA[<p>Snap, down to it saying I was not at a significant location when I’m at home.</p>
  429. ]]></content:encoded>
  430. </item>
  431. <item>
  432. <title>
  433. Comment on Janky Apple ID Security by Sebby </title>
  434. <link>https://mjtsai.com/blog/2024/04/26/janky-apple-id-security/#comment-4078412</link>
  435.  
  436. <dc:creator><![CDATA[Sebby]]></dc:creator>
  437. <pubDate>Sat, 27 Apr 2024 05:52:20 +0000</pubDate>
  438. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42969#comment-4078412</guid>
  439.  
  440. <description><![CDATA[Pro tip: most of the app-specific passwords were actually former SMTP credentials, now obsoleted by having a single OpenSMTPD relay set up on the network. So set up a relay, tell all your apps to use that, make sure the one password is correct in the relay configuration. Bonus: errors are even reported when you are offline (you won&#039;t get them till you&#039;re back online and your SMTP server has relayed them to their final destination where you&#039;ll pick them up and read them, unless of course you are running a local mail server).]]></description>
  441. <content:encoded><![CDATA[<p>Pro tip: most of the app-specific passwords were actually former SMTP credentials, now obsoleted by having a single OpenSMTPD relay set up on the network. So set up a relay, tell all your apps to use that, make sure the one password is correct in the relay configuration. Bonus: errors are even reported when you are offline (you won't get them till you're back online and your SMTP server has relayed them to their final destination where you'll pick them up and read them, unless of course you are running a local mail server).</p>
  442. ]]></content:encoded>
  443. </item>
  444. <item>
  445. <title>
  446. Comment on Janky Apple ID Security by Bri </title>
  447. <link>https://mjtsai.com/blog/2024/04/26/janky-apple-id-security/#comment-4078375</link>
  448.  
  449. <dc:creator><![CDATA[Bri]]></dc:creator>
  450. <pubDate>Sat, 27 Apr 2024 05:12:41 +0000</pubDate>
  451. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42969#comment-4078375</guid>
  452.  
  453. <description><![CDATA[Weird inscrutable issues with Apple&#039;s black box services is why I&#039;m trying to transition away from them as much as I can. Unfortunately there&#039;s nothing I can do about having an Apple developer account so long as I&#039;m an Apple developer.]]></description>
  454. <content:encoded><![CDATA[<p>Weird inscrutable issues with Apple's black box services is why I'm trying to transition away from them as much as I can. Unfortunately there's nothing I can do about having an Apple developer account so long as I'm an Apple developer.</p>
  455. ]]></content:encoded>
  456. </item>
  457. <item>
  458. <title>
  459. Comment on Janky Apple ID Security by Jamie </title>
  460. <link>https://mjtsai.com/blog/2024/04/26/janky-apple-id-security/#comment-4078324</link>
  461.  
  462. <dc:creator><![CDATA[Jamie]]></dc:creator>
  463. <pubDate>Sat, 27 Apr 2024 04:33:06 +0000</pubDate>
  464. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42969#comment-4078324</guid>
  465.  
  466. <description><![CDATA[Had this happen and it really bothered me. Phone told me I could verifiy using one of my other devices but all of them were locked as well, but would let me send a code to the phone via SMS, which lead to a password reset. Talked to Apple Support to see if there was any insight as to *why* but they couldn&#039;t tell me.]]></description>
  467. <content:encoded><![CDATA[<p>Had this happen and it really bothered me. Phone told me I could verifiy using one of my other devices but all of them were locked as well, but would let me send a code to the phone via SMS, which lead to a password reset. Talked to Apple Support to see if there was any insight as to *why* but they couldn't tell me.</p>
  468. ]]></content:encoded>
  469. </item>
  470. <item>
  471. <title>
  472. Comment on Janky Apple ID Security by Sebby </title>
  473. <link>https://mjtsai.com/blog/2024/04/26/janky-apple-id-security/#comment-4078279</link>
  474.  
  475. <dc:creator><![CDATA[Sebby]]></dc:creator>
  476. <pubDate>Sat, 27 Apr 2024 04:05:41 +0000</pubDate>
  477. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42969#comment-4078279</guid>
  478.  
  479. <description><![CDATA[Oh thank goodness it wasn&#039;t just me, was drifting to sleep when I got the notification, thought I&#039;d been hacked. Essentially the same symptoms as Michael except I was also asked to find another device (iMac, in other room) to unlock, which was showing both a system dialog saying that FaceTime needed me to sign in again and the notification for my account being locked, which just took me to the iCloud pane, security section, to change my password, which I had no choice but to do, after backing out of that broken password verification sheet, but at least I&#039;d bypassed the stupid stolen device protection delay, which I will probably still not turn off. All very shitty, and I&#039;m now very, very, very glad that my passwords are all locally stored in Strongbox, the vault on my NAS, accessible through a VPN under my control with no Apple bits involved. I checked my iCloud Drive for any text files, made sure none of them were absolutely critical to authentication, also discovering that my app-specific passwords no longer worked (FFS!) and that my AirPods pairing keys had been zapped, even when I restarted everything, and even though they showed up fine in Bluetooth settings and could still be manually connected. Took the opportunity to look through and correct all my passwords to ensure everything was accounted for including my new Apple ID password, which in fairness benefited from a change after many years and probably woke me up to do a task that I would have otherwise put off, found during this process that Strongbox, though not perfect, really is the right choice for me; highly recommend. So all in all just a really great way to be woken back up, not. Now having some tea, listening to an audiobook, and ranting on the Internet. Thank you Apple, your momumental incompetence is truly unmatched. Have one of these Apple stickers.]]></description>
  480. <content:encoded><![CDATA[<p>Oh thank goodness it wasn't just me, was drifting to sleep when I got the notification, thought I'd been hacked. Essentially the same symptoms as Michael except I was also asked to find another device (iMac, in other room) to unlock, which was showing both a system dialog saying that FaceTime needed me to sign in again and the notification for my account being locked, which just took me to the iCloud pane, security section, to change my password, which I had no choice but to do, after backing out of that broken password verification sheet, but at least I'd bypassed the stupid stolen device protection delay, which I will probably still not turn off. All very shitty, and I'm now very, very, very glad that my passwords are all locally stored in Strongbox, the vault on my NAS, accessible through a VPN under my control with no Apple bits involved. I checked my iCloud Drive for any text files, made sure none of them were absolutely critical to authentication, also discovering that my app-specific passwords no longer worked (FFS!) and that my AirPods pairing keys had been zapped, even when I restarted everything, and even though they showed up fine in Bluetooth settings and could still be manually connected. Took the opportunity to look through and correct all my passwords to ensure everything was accounted for including my new Apple ID password, which in fairness benefited from a change after many years and probably woke me up to do a task that I would have otherwise put off, found during this process that Strongbox, though not perfect, really is the right choice for me; highly recommend. So all in all just a really great way to be woken back up, not. Now having some tea, listening to an audiobook, and ranting on the Internet. Thank you Apple, your momumental incompetence is truly unmatched. Have one of these Apple stickers.</p>
  481. ]]></content:encoded>
  482. </item>
  483. <item>
  484. <title>
  485. Comment on Janky Apple ID Security by Kim </title>
  486. <link>https://mjtsai.com/blog/2024/04/26/janky-apple-id-security/#comment-4078261</link>
  487.  
  488. <dc:creator><![CDATA[Kim]]></dc:creator>
  489. <pubDate>Sat, 27 Apr 2024 03:49:46 +0000</pubDate>
  490. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42969#comment-4078261</guid>
  491.  
  492. <description><![CDATA[This is driving me crazy, can you please layout how to do it without having to use your phone number? It’s not recognizing it, my Mac.com account stopped getting emails at 4:10pm this afternoon. I get to the part about having to unlock my account by verifying and changing my password, but here comes the phone number option and it’s not working. This includes doing it on the web. My devices aren’t recognizing each other- ugh this sucks]]></description>
  493. <content:encoded><![CDATA[<p>This is driving me crazy, can you please layout how to do it without having to use your phone number? It’s not recognizing it, my Mac.com account stopped getting emails at 4:10pm this afternoon. I get to the part about having to unlock my account by verifying and changing my password, but here comes the phone number option and it’s not working. This includes doing it on the web. My devices aren’t recognizing each other- ugh this sucks</p>
  494. ]]></content:encoded>
  495. </item>
  496. <item>
  497. <title>
  498. Comment on Janky Apple ID Security by Marc </title>
  499. <link>https://mjtsai.com/blog/2024/04/26/janky-apple-id-security/#comment-4078246</link>
  500.  
  501. <dc:creator><![CDATA[Marc]]></dc:creator>
  502. <pubDate>Sat, 27 Apr 2024 03:32:40 +0000</pubDate>
  503. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42969#comment-4078246</guid>
  504.  
  505. <description><![CDATA[More reports:
  506.  
  507. https://9to5mac.com/2024/04/26/signed-out-of-apple-id-account-problem-password/]]></description>
  508. <content:encoded><![CDATA[<p>More reports:</p>
  509. <p><a href="https://9to5mac.com/2024/04/26/signed-out-of-apple-id-account-problem-password/" rel="nofollow ugc">https://9to5mac.com/2024/04/26/signed-out-of-apple-id-account-problem-password/</a></p>
  510. ]]></content:encoded>
  511. </item>
  512. <item>
  513. <title>
  514. Comment on Janky Apple ID Security by Anonymous </title>
  515. <link>https://mjtsai.com/blog/2024/04/26/janky-apple-id-security/#comment-4078243</link>
  516.  
  517. <dc:creator><![CDATA[Anonymous]]></dc:creator>
  518. <pubDate>Sat, 27 Apr 2024 03:29:46 +0000</pubDate>
  519. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42969#comment-4078243</guid>
  520.  
  521. <description><![CDATA[I had the same thing happen on April 4th with an account only used with one computer. I was able to unlock it without any problems and changed the password. A couple days later I kept getting a dialog telling me that it couldn&#039;t log into iMessage because of a problem with the account, which was weird since I&#039;ve never used iMessage with this account/computer. A Google search suggested an error, and restarting the computer made it stop.
  522.  
  523. Concerned, I tried to look for account activity, but couldn&#039;t find it anywhere. (This might be because I&#039;ve turned off most analytics and logging though.) A search suggests that there isn&#039;t one beyond a list of devices associated with the account. I requested a download of my Apple ID data, but it didn&#039;t show anything useful. Both Google and Microsoft will show account activity, and Microsoft will even show unsuccessful login attempts.
  524.  
  525. I&#039;m a bit relieved that I&#039;m not the only one this has happened to, but now I&#039;m wondering if something is happening at Apple. A failure or intrusion?]]></description>
  526. <content:encoded><![CDATA[<p>I had the same thing happen on April 4th with an account only used with one computer. I was able to unlock it without any problems and changed the password. A couple days later I kept getting a dialog telling me that it couldn't log into iMessage because of a problem with the account, which was weird since I've never used iMessage with this account/computer. A Google search suggested an error, and restarting the computer made it stop.</p>
  527. <p>Concerned, I tried to look for account activity, but couldn't find it anywhere. (This might be because I've turned off most analytics and logging though.) A search suggests that there isn't one beyond a list of devices associated with the account. I requested a download of my Apple ID data, but it didn't show anything useful. Both Google and Microsoft will show account activity, and Microsoft will even show unsuccessful login attempts.</p>
  528. <p>I'm a bit relieved that I'm not the only one this has happened to, but now I'm wondering if something is happening at Apple. A failure or intrusion?</p>
  529. ]]></content:encoded>
  530. </item>
  531. <item>
  532. <title>
  533. Comment on Janky Apple ID Security by David J. Whelan </title>
  534. <link>https://mjtsai.com/blog/2024/04/26/janky-apple-id-security/#comment-4078239</link>
  535.  
  536. <dc:creator><![CDATA[David J. Whelan]]></dc:creator>
  537. <pubDate>Sat, 27 Apr 2024 03:25:56 +0000</pubDate>
  538. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42969#comment-4078239</guid>
  539.  
  540. <description><![CDATA[So happy (and unhappy) that I read this today, a couple of hours after the same thing happened to me. I did a Messages chat with Apple Support to resolve this, which eventually involved resetting my iCloud password and now reconnecting on all of my personal devices. And our Apple TVs. And probably something else. So annoying. But sort of glad I am not alone.]]></description>
  541. <content:encoded><![CDATA[<p>So happy (and unhappy) that I read this today, a couple of hours after the same thing happened to me. I did a Messages chat with Apple Support to resolve this, which eventually involved resetting my iCloud password and now reconnecting on all of my personal devices. And our Apple TVs. And probably something else. So annoying. But sort of glad I am not alone.</p>
  542. ]]></content:encoded>
  543. </item>
  544. <item>
  545. <title>
  546. Comment on Janky Apple ID Security by Kevin Schumacher </title>
  547. <link>https://mjtsai.com/blog/2024/04/26/janky-apple-id-security/#comment-4078235</link>
  548.  
  549. <dc:creator><![CDATA[Kevin Schumacher]]></dc:creator>
  550. <pubDate>Sat, 27 Apr 2024 03:13:38 +0000</pubDate>
  551. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42969#comment-4078235</guid>
  552.  
  553. <description><![CDATA[Earlier tonight it popped up on all three devices I was actively using (Watch, TV, iPhone) and demanded my Apple ID password be reentered in Settings. I just tapped Not Now until it went away, which took 5 or 6 taps, then it would go away for 5 or 10 minutes and come back. It did that for three or four cycles and then stopped entirely. I just assume that something failed to renew a token due to a server being down or glitching. I’ve seen it do this a few times in the past and it usually clears itself up.
  554.  
  555. I don’t have the security delay enabled, FWIW.]]></description>
  556. <content:encoded><![CDATA[<p>Earlier tonight it popped up on all three devices I was actively using (Watch, TV, iPhone) and demanded my Apple ID password be reentered in Settings. I just tapped Not Now until it went away, which took 5 or 6 taps, then it would go away for 5 or 10 minutes and come back. It did that for three or four cycles and then stopped entirely. I just assume that something failed to renew a token due to a server being down or glitching. I’ve seen it do this a few times in the past and it usually clears itself up.</p>
  557. <p>I don’t have the security delay enabled, FWIW.</p>
  558. ]]></content:encoded>
  559. </item>
  560. <item>
  561. <title>
  562. Comment on Janky Apple ID Security by Michael Tsai </title>
  563. <link>https://mjtsai.com/blog/2024/04/26/janky-apple-id-security/#comment-4078231</link>
  564.  
  565. <dc:creator><![CDATA[Michael Tsai]]></dc:creator>
  566. <pubDate>Sat, 27 Apr 2024 02:57:02 +0000</pubDate>
  567. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42969#comment-4078231</guid>
  568.  
  569. <description><![CDATA[@Anonymous In theory, it should be usable, though semi-offline, for that hour, but it’s really annoying to have it keep popping up alerts asking me to log in, and I have low confidence that the system and apps are well tested in that state. I figured it would mess up the movie we were about to watch on Apple TV. Also, the brokenness makes me worried that there are other problems with this feature. Like maybe it will escalate to a longer delay than what it’s supposed to or require another device to unlock. The feature sounds good, but I no longer trust it and would prefer something simpler and more reliable. I’m careful about entering my passcode in public.]]></description>
  570. <content:encoded><![CDATA[<p>@Anonymous In theory, it should be usable, though semi-offline, for that hour, but it’s really annoying to have it keep popping up alerts asking me to log in, and I have low confidence that the system and apps are well tested in that state. I figured it would mess up the movie we were about to watch on Apple TV. Also, the brokenness makes me worried that there are other problems with this feature. Like maybe it will escalate to a longer delay than what it’s supposed to or require another device to unlock. The feature sounds good, but I no longer trust it and would prefer something simpler and more reliable. I’m careful about entering my passcode in public.</p>
  571. ]]></content:encoded>
  572. </item>
  573. <item>
  574. <title>
  575. Comment on Janky Apple ID Security by Anonymous </title>
  576. <link>https://mjtsai.com/blog/2024/04/26/janky-apple-id-security/#comment-4078227</link>
  577.  
  578. <dc:creator><![CDATA[Anonymous]]></dc:creator>
  579. <pubDate>Sat, 27 Apr 2024 02:48:36 +0000</pubDate>
  580. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42969#comment-4078227</guid>
  581.  
  582. <description><![CDATA[I have the security delay set for &quot;always&quot; instead of at familiar locations. Is there a reason an hour delay is infeasible? Its not like your data is gone for an hour, it just cant sync, right? That seems better than a stolen phone and account...]]></description>
  583. <content:encoded><![CDATA[<p>I have the security delay set for "always" instead of at familiar locations. Is there a reason an hour delay is infeasible? Its not like your data is gone for an hour, it just cant sync, right? That seems better than a stolen phone and account...</p>
  584. ]]></content:encoded>
  585. </item>
  586. <item>
  587. <title>
  588. Comment on Janky Apple ID Security by Andrew </title>
  589. <link>https://mjtsai.com/blog/2024/04/26/janky-apple-id-security/#comment-4078226</link>
  590.  
  591. <dc:creator><![CDATA[Andrew]]></dc:creator>
  592. <pubDate>Sat, 27 Apr 2024 02:44:02 +0000</pubDate>
  593. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42969#comment-4078226</guid>
  594.  
  595. <description><![CDATA[The EXACT same thing just happened to me. Was convinced someone was trying to hack me, and it didn&#039;t seem like I was going to be able to get back into my account.
  596.  
  597. Apple seriously needs to get this sorted - It&#039;s discouraging me from ever trusting them again.]]></description>
  598. <content:encoded><![CDATA[<p>The EXACT same thing just happened to me. Was convinced someone was trying to hack me, and it didn't seem like I was going to be able to get back into my account. </p>
  599. <p>Apple seriously needs to get this sorted - It's discouraging me from ever trusting them again.</p>
  600. ]]></content:encoded>
  601. </item>
  602. <item>
  603. <title>
  604. Comment on Janky Apple ID Security by Neil </title>
  605. <link>https://mjtsai.com/blog/2024/04/26/janky-apple-id-security/#comment-4078225</link>
  606.  
  607. <dc:creator><![CDATA[Neil]]></dc:creator>
  608. <pubDate>Sat, 27 Apr 2024 02:42:36 +0000</pubDate>
  609. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42969#comment-4078225</guid>
  610.  
  611. <description><![CDATA[I have been plagued with this for months. My iCloud account locks every 1-2 days and I have to unlock it. Sometimes I can unlock it without a password, other times I need to change it. I’ve phone Apple support and they’ve been mostly unhelpful.]]></description>
  612. <content:encoded><![CDATA[<p>I have been plagued with this for months. My iCloud account locks every 1-2 days and I have to unlock it. Sometimes I can unlock it without a password, other times I need to change it. I’ve phone Apple support and they’ve been mostly unhelpful.</p>
  613. ]]></content:encoded>
  614. </item>
  615. <item>
  616. <title>
  617. Comment on Janky Apple ID Security by Marc </title>
  618. <link>https://mjtsai.com/blog/2024/04/26/janky-apple-id-security/#comment-4078216</link>
  619.  
  620. <dc:creator><![CDATA[Marc]]></dc:creator>
  621. <pubDate>Sat, 27 Apr 2024 02:25:13 +0000</pubDate>
  622. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42969#comment-4078216</guid>
  623.  
  624. <description><![CDATA[Same things here, and it also wiped out my application specific passwords which caused problems with several apps.
  625.  
  626. Had to create new passwords for each of them.
  627.  
  628. Took a while to get everything reconfigured and synched on my MacBook Pro and iPhone.]]></description>
  629. <content:encoded><![CDATA[<p>Same things here, and it also wiped out my application specific passwords which caused problems with several apps.</p>
  630. <p>Had to create new passwords for each of them.</p>
  631. <p>Took a while to get everything reconfigured and synched on my MacBook Pro and iPhone.</p>
  632. ]]></content:encoded>
  633. </item>
  634. <item>
  635. <title>
  636. Comment on Janky Apple ID Security by JJ </title>
  637. <link>https://mjtsai.com/blog/2024/04/26/janky-apple-id-security/#comment-4078212</link>
  638.  
  639. <dc:creator><![CDATA[JJ]]></dc:creator>
  640. <pubDate>Sat, 27 Apr 2024 02:18:39 +0000</pubDate>
  641. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42969#comment-4078212</guid>
  642.  
  643. <description><![CDATA[Same thing for me.  I’m turning off Stolen Device Protection.  What a disaster if this happens while traveling or anywhere but home]]></description>
  644. <content:encoded><![CDATA[<p>Same thing for me.  I’m turning off Stolen Device Protection.  What a disaster if this happens while traveling or anywhere but home</p>
  645. ]]></content:encoded>
  646. </item>
  647. <item>
  648. <title>
  649. Comment on Janky Apple ID Security by G </title>
  650. <link>https://mjtsai.com/blog/2024/04/26/janky-apple-id-security/#comment-4078205</link>
  651.  
  652. <dc:creator><![CDATA[G]]></dc:creator>
  653. <pubDate>Sat, 27 Apr 2024 01:53:51 +0000</pubDate>
  654. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42969#comment-4078205</guid>
  655.  
  656. <description><![CDATA[Same thing happened to me tonight. Just a terrible and confusing experience.]]></description>
  657. <content:encoded><![CDATA[<p>Same thing happened to me tonight. Just a terrible and confusing experience.</p>
  658. ]]></content:encoded>
  659. </item>
  660. <item>
  661. <title>
  662. Comment on Janky Apple ID Security by VerticalBlank </title>
  663. <link>https://mjtsai.com/blog/2024/04/26/janky-apple-id-security/#comment-4078204</link>
  664.  
  665. <dc:creator><![CDATA[VerticalBlank]]></dc:creator>
  666. <pubDate>Sat, 27 Apr 2024 01:52:46 +0000</pubDate>
  667. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42969#comment-4078204</guid>
  668.  
  669. <description><![CDATA[This is why I have my AppleID protected by a YubiKey (well three of them actually).]]></description>
  670. <content:encoded><![CDATA[<p>This is why I have my AppleID protected by a YubiKey (well three of them actually).</p>
  671. ]]></content:encoded>
  672. </item>
  673. <item>
  674. <title>
  675. Comment on Janky Apple ID Security by Scott W Hill </title>
  676. <link>https://mjtsai.com/blog/2024/04/26/janky-apple-id-security/#comment-4078203</link>
  677.  
  678. <dc:creator><![CDATA[Scott W Hill]]></dc:creator>
  679. <pubDate>Sat, 27 Apr 2024 01:50:18 +0000</pubDate>
  680. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42969#comment-4078203</guid>
  681.  
  682. <description><![CDATA[Hmm, I just had my Apple ID get mysteriously locked too. That process is pretty sketchy feeling, and I&#039;m at home, with all my devices at hand.]]></description>
  683. <content:encoded><![CDATA[<p>Hmm, I just had my Apple ID get mysteriously locked too. That process is pretty sketchy feeling, and I'm at home, with all my devices at hand.</p>
  684. ]]></content:encoded>
  685. </item>
  686. <item>
  687. <title>
  688. Comment on TikTok Ban by Old Unix Geek </title>
  689. <link>https://mjtsai.com/blog/2024/04/24/tiktok-ban/#comment-4078100</link>
  690.  
  691. <dc:creator><![CDATA[Old Unix Geek]]></dc:creator>
  692. <pubDate>Fri, 26 Apr 2024 21:02:56 +0000</pubDate>
  693. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42914#comment-4078100</guid>
  694.  
  695. <description><![CDATA[@Plume: We fuck around, and then when it&#039;s time to find out, we blame someone else.
  696.  
  697. Who outsourced to China to save a cent here and there?
  698. Oh, yes, our &quot;best and brightest&quot; did.
  699. Who&#039;s upset the Chinese learned from us and are now competing against us?
  700. Oh, yes, that&#039;s also our &quot;best and brightest&quot;.
  701.  
  702. As the Chinese used to say, a capitalist will sell you the rope you&#039;re buying to hang him.
  703.  
  704. As to Comac, not really. It&#039;s only a regional aircraft and it still has many Western components (made by companies like Nexcelle, Thales, Honeywell, Rockwell Collins, Pratt &#038; Whitney, GE). Air China still uses Boeings and Airbuses. Comac only hopes to get 1/5 of the Chinese market by 2035.
  705.  
  706. My understanding is that the only people who eliminated all Western components from their aircraft are the Russians, but they&#039;ve always had a big aircraft industry. Sanctions provided a them with spur to finish the job.
  707.  
  708. A similar story applies to our electronics -- it&#039;s a lot easier to want to get rid of x86/Nvidia than it is to actually do it. Still, if we provide the impetus, they will do so, and that will be our loss. Once bitten, twice shy, so they would be unlikely to reopen their market afterwards.
  709.  
  710. China is still a big market for us, but only if our politicians don&#039;t continue fucking it up. Indeed, it was even a pretty big market for our agricultural products, but now China is diversifying by boosting imports from Russia (27 fold).
  711.  
  712. Our &quot;best and brightest&quot; should remember that &quot;Pride cometh before a fall&quot;.]]></description>
  713. <content:encoded><![CDATA[<p>@Plume: We fuck around, and then when it's time to find out, we blame someone else.</p>
  714. <p>Who outsourced to China to save a cent here and there?<br />
  715. Oh, yes, our "best and brightest" did.<br />
  716. Who's upset the Chinese learned from us and are now competing against us?<br />
  717. Oh, yes, that's also our "best and brightest".</p>
  718. <p>As the Chinese used to say, a capitalist will sell you the rope you're buying to hang him.</p>
  719. <p>As to Comac, not really. It's only a regional aircraft and it still has many Western components (made by companies like Nexcelle, Thales, Honeywell, Rockwell Collins, Pratt &amp; Whitney, GE). Air China still uses Boeings and Airbuses. Comac only hopes to get 1/5 of the Chinese market by 2035.</p>
  720. <p>My understanding is that the only people who eliminated all Western components from their aircraft are the Russians, but they've always had a big aircraft industry. Sanctions provided a them with spur to finish the job.</p>
  721. <p>A similar story applies to our electronics -- it's a lot easier to want to get rid of x86/Nvidia than it is to actually do it. Still, if we provide the impetus, they will do so, and that will be our loss. Once bitten, twice shy, so they would be unlikely to reopen their market afterwards.</p>
  722. <p>China is still a big market for us, but only if our politicians don't continue fucking it up. Indeed, it was even a pretty big market for our agricultural products, but now China is diversifying by boosting imports from Russia (27 fold).</p>
  723. <p>Our "best and brightest" should remember that "Pride cometh before a fall".</p>
  724. ]]></content:encoded>
  725. </item>
  726. <item>
  727. <title>
  728. Comment on FTC Bans Noncompetes by Gord L. </title>
  729. <link>https://mjtsai.com/blog/2024/04/25/ftc-bans-noncompetes/#comment-4078095</link>
  730.  
  731. <dc:creator><![CDATA[Gord L.]]></dc:creator>
  732. <pubDate>Fri, 26 Apr 2024 20:49:23 +0000</pubDate>
  733. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42942#comment-4078095</guid>
  734.  
  735. <description><![CDATA[Don’t worry Sebby, the Supreme Court will nuke this in a few months, when they overturn the Chevron doctrine, nullifying the ability of all regulatory agencies to make policy decisions.]]></description>
  736. <content:encoded><![CDATA[<p>Don’t worry Sebby, the Supreme Court will nuke this in a few months, when they overturn the Chevron doctrine, nullifying the ability of all regulatory agencies to make policy decisions.</p>
  737. ]]></content:encoded>
  738. </item>
  739. <item>
  740. <title>
  741. Comment on TikTok Ban by Plume </title>
  742. <link>https://mjtsai.com/blog/2024/04/24/tiktok-ban/#comment-4078058</link>
  743.  
  744. <dc:creator><![CDATA[Plume]]></dc:creator>
  745. <pubDate>Fri, 26 Apr 2024 19:50:31 +0000</pubDate>
  746. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42914#comment-4078058</guid>
  747.  
  748. <description><![CDATA[&quot;Let&#039;s see who China could retaliate against because they are involved in &quot;critical&quot; Chinese infrastructure... Tesla, Apple, Microsoft, Intel, AMD, ARM, Google, Cisco, Oracle, Boeing... oh well.&quot;
  749.  
  750. China is already doing all of that.
  751.  
  752. They&#039;re actively agitating against Western companies in national media, which is a primary reason why Apple&#039;s market share in China is falling quickly. They&#039;ve banned all the Western social media already. There is effectively no Google in China anymore. They&#039;re actively helping Huawei get their chip design and production up so they can get rid of Intel and AMD. They stole trade secrets from Boing subcontractors, and the Comac C919 is now flying.]]></description>
  753. <content:encoded><![CDATA[<p>"Let's see who China could retaliate against because they are involved in "critical" Chinese infrastructure... Tesla, Apple, Microsoft, Intel, AMD, ARM, Google, Cisco, Oracle, Boeing... oh well."</p>
  754. <p>China is already doing all of that.</p>
  755. <p>They're actively agitating against Western companies in national media, which is a primary reason why Apple's market share in China is falling quickly. They've banned all the Western social media already. There is effectively no Google in China anymore. They're actively helping Huawei get their chip design and production up so they can get rid of Intel and AMD. They stole trade secrets from Boing subcontractors, and the Comac C919 is now flying.</p>
  756. ]]></content:encoded>
  757. </item>
  758. <item>
  759. <title>
  760. Comment on TikTok Ban by Old Unix Geek </title>
  761. <link>https://mjtsai.com/blog/2024/04/24/tiktok-ban/#comment-4078024</link>
  762.  
  763. <dc:creator><![CDATA[Old Unix Geek]]></dc:creator>
  764. <pubDate>Fri, 26 Apr 2024 18:13:32 +0000</pubDate>
  765. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42914#comment-4078024</guid>
  766.  
  767. <description><![CDATA[Same people also want to ban DJI for &quot;security&quot; reasons: https://archive.is/QSbjw
  768.  
  769. Let&#039;s see who China could retaliate against because they are involved in &quot;critical&quot; Chinese infrastructure... Tesla, Apple, Microsoft, Intel, AMD, ARM, Google, Cisco, Oracle, Boeing... oh well.
  770.  
  771. Pissing off most of the US population is a very odd strategy for staying in power if the population&#039;s votes count.]]></description>
  772. <content:encoded><![CDATA[<p>Same people also want to ban DJI for "security" reasons: <a href="https://archive.is/QSbjw" rel="nofollow ugc">https://archive.is/QSbjw</a></p>
  773. <p>Let's see who China could retaliate against because they are involved in "critical" Chinese infrastructure... Tesla, Apple, Microsoft, Intel, AMD, ARM, Google, Cisco, Oracle, Boeing... oh well.</p>
  774. <p>Pissing off most of the US population is a very odd strategy for staying in power if the population's votes count.</p>
  775. ]]></content:encoded>
  776. </item>
  777. <item>
  778. <title>
  779. Comment on TikTok Ban by Plume </title>
  780. <link>https://mjtsai.com/blog/2024/04/24/tiktok-ban/#comment-4078002</link>
  781.  
  782. <dc:creator><![CDATA[Plume]]></dc:creator>
  783. <pubDate>Fri, 26 Apr 2024 16:51:24 +0000</pubDate>
  784. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42914#comment-4078002</guid>
  785.  
  786. <description><![CDATA[&quot;I think it’s more that westerners are inclined believe it’s true but wonder why if it’s so obvious no one can be bothered to actually demonstrate it.&quot;
  787.  
  788. There is at least one ByteDance executive who claimed that the Chinese government had access to TikTok&#039;s data, but I&#039;m not actually sure what exactly people expect to see. The way this usually works isn&#039;t that the government sends ByteDance an official letter telling them to sow distrust in the US and promote divisive content, and to send them a hard drive with all of the data from all of their US users.
  789.  
  790. It&#039;s that they message what they want to happen in the media, and then people do it, because if they don&#039;t, they get the Jack Ma treatment if they&#039;re lucky, and the Xu Ming treatment if they&#039;re not.
  791.  
  792. That&#039;s how it works in China, every shop has its laoban who knows a guy from the government, and if they&#039;re on good terms, everything goes well, and if they&#039;re not, things don&#039;t go so well.
  793.  
  794.  
  795. &quot;The issue here is that &quot;Liberal Democracy&quot; really is increasingly indistinguishable, in many respects, from authoritarian autocracy&quot;
  796.  
  797. Honestly, I have a lot of sympathy for your general points, but if you say stuff like that, you just look like somebody who has lost the plot. We can criticize Western democracies without pretending that they&#039;re indistinguishable from China, North Korea, or Russia.
  798.  
  799. The idea that these countries really aren&#039;t all that different from a free democracy is exactly the message they are trying to push. So let&#039;s not be apologists for murderous dictatorships that enslave their own people.]]></description>
  800. <content:encoded><![CDATA[<p>"I think it’s more that westerners are inclined believe it’s true but wonder why if it’s so obvious no one can be bothered to actually demonstrate it."</p>
  801. <p>There is at least one ByteDance executive who claimed that the Chinese government had access to TikTok's data, but I'm not actually sure what exactly people expect to see. The way this usually works isn't that the government sends ByteDance an official letter telling them to sow distrust in the US and promote divisive content, and to send them a hard drive with all of the data from all of their US users.</p>
  802. <p>It's that they message what they want to happen in the media, and then people do it, because if they don't, they get the Jack Ma treatment if they're lucky, and the Xu Ming treatment if they're not.</p>
  803. <p>That's how it works in China, every shop has its laoban who knows a guy from the government, and if they're on good terms, everything goes well, and if they're not, things don't go so well.</p>
  804. <p>"The issue here is that "Liberal Democracy" really is increasingly indistinguishable, in many respects, from authoritarian autocracy"</p>
  805. <p>Honestly, I have a lot of sympathy for your general points, but if you say stuff like that, you just look like somebody who has lost the plot. We can criticize Western democracies without pretending that they're indistinguishable from China, North Korea, or Russia.</p>
  806. <p>The idea that these countries really aren't all that different from a free democracy is exactly the message they are trying to push. So let's not be apologists for murderous dictatorships that enslave their own people.</p>
  807. ]]></content:encoded>
  808. </item>
  809. <item>
  810. <title>
  811. Comment on Fairphone Fairbuds by Sebby </title>
  812. <link>https://mjtsai.com/blog/2024/04/23/fairphone-fairbuds/#comment-4077973</link>
  813.  
  814. <dc:creator><![CDATA[Sebby]]></dc:creator>
  815. <pubDate>Fri, 26 Apr 2024 16:08:47 +0000</pubDate>
  816. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42905#comment-4077973</guid>
  817.  
  818. <description><![CDATA[Microchip Kleer, for use at home.
  819.  
  820. Or, if you can stand the latency, there&#039;s always AirPlay, of course. Open implementations are available.]]></description>
  821. <content:encoded><![CDATA[<p>Microchip Kleer, for use at home.</p>
  822. <p>Or, if you can stand the latency, there's always AirPlay, of course. Open implementations are available.</p>
  823. ]]></content:encoded>
  824. </item>
  825. <item>
  826. <title>
  827. Comment on Charles Edge, RIP by Sebby </title>
  828. <link>https://mjtsai.com/blog/2024/04/23/charles-edge-rip/#comment-4077967</link>
  829.  
  830. <dc:creator><![CDATA[Sebby]]></dc:creator>
  831. <pubDate>Fri, 26 Apr 2024 16:03:46 +0000</pubDate>
  832. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42907#comment-4077967</guid>
  833.  
  834. <description><![CDATA[Yep, he was a legend. Never met him but really enjoyed his blog and other writings. A real devotee of both Mac and UNIX, in that regard very much after my own heart. RIP, man.]]></description>
  835. <content:encoded><![CDATA[<p>Yep, he was a legend. Never met him but really enjoyed his blog and other writings. A real devotee of both Mac and UNIX, in that regard very much after my own heart. RIP, man.</p>
  836. ]]></content:encoded>
  837. </item>
  838. <item>
  839. <title>
  840. Comment on TikTok Ban by Sebby </title>
  841. <link>https://mjtsai.com/blog/2024/04/24/tiktok-ban/#comment-4077942</link>
  842.  
  843. <dc:creator><![CDATA[Sebby]]></dc:creator>
  844. <pubDate>Fri, 26 Apr 2024 15:15:52 +0000</pubDate>
  845. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42914#comment-4077942</guid>
  846.  
  847. <description><![CDATA[@OUG Yes, basically. Really can&#039;t add much to that. Particularly the last paragraph, bang on. Hypocrisy stinks to high heaven.
  848.  
  849. @Plume No, I don&#039;t think that&#039;s the problem—or at least, not the whole problem.
  850.  
  851. The issue here is that &quot;Liberal Democracy&quot; really is increasingly indistinguishable, in many respects, from authoritarian autocracy. While it might be a great aspiration (and, FTR, one I generally feel inclined toward), the fact that there is a huge power imbalance between the governed and the governing, and that there is a close and symbiotic financial interest between government and capital, means that it&#039;s just not possible to look at this as anything other than protectionism, undergirded by hypocrisy. (Protectionism, to be clear, is not necessarily the problem, in itself. Honestly, a little more interventionism, particularly in the arenas of public research and development, would be awesome, as would favouring those who respected universal rights where realistically feasible.) Human rights include the fundamental right to privacy; they also, of course, include the right to life, including for the people of Gaza. Westerners (and those they support with aid) should enjoy them regardless of the entities (and their geopolitical allies) that they interact with, and that should be the basis of domestic regulation. In that case, it&#039;s obvious that the US and other western powers, but especially the laissez-faire Anglosphere, don&#039;t qualify. And, frankly, I think it&#039;s very difficult to argue that the US (or UK ...) government isn&#039;t directly involved in the affairs of companies, anyway: national security letters, (dis)info psy-ops and &quot;consensus&quot;-making, cooperative mass surveillance operations, government reliance on data brokers, large friendly contracts for government purposes, ... at what point is it reasonable to argue that it is a conspiracy of government, versus the very natural consequence of a triumphant private market? And, indeed, if capitalism is so very wonderful, why aren&#039;t we jumping for joy at the success of Byte Dance, which is drinking mightily from the well of prosperity afforded by the private market outside its home jurisdiction? Sigh.
  852.  
  853. &#062; “But what they have seen, beyond even this bill, is Congress’ failure to enact meaningful consumer protections on big tech, and may cynically view this as a diversion, or worse, a concession to U.S. social media platforms,” Warner continued.
  854.  
  855. Well, no shit, Senator. And do you think it&#039;s just possible that they might be right? Because, honestly, that&#039;s what it looks like to me. And it&#039;s no use your waving the &quot;National Security&quot; banner if you can&#039;t provide clear evidence of why. Otherwise it just looks like what it is, blatant protectionism. If there &lt;i&gt;is&lt;/i&gt; a legitimate basis for concern, then it&#039;s a basis for regulating big tech, which is the industry that TikTok most closely resembles. So unless you&#039;re worried that the intelligence community knows something you&#039;d rather they didn&#039;t, start regulating!]]></description>
  856. <content:encoded><![CDATA[<p>@OUG Yes, basically. Really can't add much to that. Particularly the last paragraph, bang on. Hypocrisy stinks to high heaven.</p>
  857. <p>@Plume No, I don't think that's the problem—or at least, not the whole problem.</p>
  858. <p>The issue here is that "Liberal Democracy" really is increasingly indistinguishable, in many respects, from authoritarian autocracy. While it might be a great aspiration (and, FTR, one I generally feel inclined toward), the fact that there is a huge power imbalance between the governed and the governing, and that there is a close and symbiotic financial interest between government and capital, means that it's just not possible to look at this as anything other than protectionism, undergirded by hypocrisy. (Protectionism, to be clear, is not necessarily the problem, in itself. Honestly, a little more interventionism, particularly in the arenas of public research and development, would be awesome, as would favouring those who respected universal rights where realistically feasible.) Human rights include the fundamental right to privacy; they also, of course, include the right to life, including for the people of Gaza. Westerners (and those they support with aid) should enjoy them regardless of the entities (and their geopolitical allies) that they interact with, and that should be the basis of domestic regulation. In that case, it's obvious that the US and other western powers, but especially the laissez-faire Anglosphere, don't qualify. And, frankly, I think it's very difficult to argue that the US (or UK ...) government isn't directly involved in the affairs of companies, anyway: national security letters, (dis)info psy-ops and "consensus"-making, cooperative mass surveillance operations, government reliance on data brokers, large friendly contracts for government purposes, ... at what point is it reasonable to argue that it is a conspiracy of government, versus the very natural consequence of a triumphant private market? And, indeed, if capitalism is so very wonderful, why aren't we jumping for joy at the success of Byte Dance, which is drinking mightily from the well of prosperity afforded by the private market outside its home jurisdiction? Sigh.</p>
  859. <p>&gt; “But what they have seen, beyond even this bill, is Congress’ failure to enact meaningful consumer protections on big tech, and may cynically view this as a diversion, or worse, a concession to U.S. social media platforms,” Warner continued.</p>
  860. <p>Well, no shit, Senator. And do you think it's just possible that they might be right? Because, honestly, that's what it looks like to me. And it's no use your waving the "National Security" banner if you can't provide clear evidence of why. Otherwise it just looks like what it is, blatant protectionism. If there <i>is</i> a legitimate basis for concern, then it's a basis for regulating big tech, which is the industry that TikTok most closely resembles. So unless you're worried that the intelligence community knows something you'd rather they didn't, start regulating!</p>
  861. ]]></content:encoded>
  862. </item>
  863. <item>
  864. <title>
  865. Comment on TikTok Ban by Michael Tsai </title>
  866. <link>https://mjtsai.com/blog/2024/04/24/tiktok-ban/#comment-4077927</link>
  867.  
  868. <dc:creator><![CDATA[Michael Tsai]]></dc:creator>
  869. <pubDate>Fri, 26 Apr 2024 14:12:13 +0000</pubDate>
  870. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42914#comment-4077927</guid>
  871.  
  872. <description><![CDATA[@Plume I think it’s more that westerners are inclined believe it’s true but wonder why if it’s so obvious no one can be bothered to actually demonstrate it.]]></description>
  873. <content:encoded><![CDATA[<p>@Plume I think it’s more that westerners are inclined believe it’s true but wonder why if it’s so obvious no one can be bothered to actually demonstrate it.</p>
  874. ]]></content:encoded>
  875. </item>
  876. <item>
  877. <title>
  878. Comment on FTC Bans Noncompetes by Sebby </title>
  879. <link>https://mjtsai.com/blog/2024/04/25/ftc-bans-noncompetes/#comment-4077887</link>
  880.  
  881. <dc:creator><![CDATA[Sebby]]></dc:creator>
  882. <pubDate>Fri, 26 Apr 2024 12:06:13 +0000</pubDate>
  883. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42942#comment-4077887</guid>
  884.  
  885. <description><![CDATA[It&#039;s the end of life in America as we know it
  886.  
  887. Business will simply not operate there, will invest elsewhere.
  888.  
  889. Capital will fly. Talent, too. Only desperate migrants will remain.
  890.  
  891. And so on.
  892.  
  893. Sorry, someone had to make the case from the opposing side ... :)]]></description>
  894. <content:encoded><![CDATA[<p>It's the end of life in America as we know it</p>
  895. <p>Business will simply not operate there, will invest elsewhere.</p>
  896. <p>Capital will fly. Talent, too. Only desperate migrants will remain.</p>
  897. <p>And so on.</p>
  898. <p>Sorry, someone had to make the case from the opposing side ... :)</p>
  899. ]]></content:encoded>
  900. </item>
  901. <item>
  902. <title>
  903. Comment on FTC Bans Noncompetes by Kristoffer </title>
  904. <link>https://mjtsai.com/blog/2024/04/25/ftc-bans-noncompetes/#comment-4077851</link>
  905.  
  906. <dc:creator><![CDATA[Kristoffer]]></dc:creator>
  907. <pubDate>Fri, 26 Apr 2024 09:15:58 +0000</pubDate>
  908. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42942#comment-4077851</guid>
  909.  
  910. <description><![CDATA[Good stuff!
  911. Fight the power]]></description>
  912. <content:encoded><![CDATA[<p>Good stuff!<br />
  913. Fight the power</p>
  914. ]]></content:encoded>
  915. </item>
  916. <item>
  917. <title>
  918. Comment on TikTok Ban by Plume </title>
  919. <link>https://mjtsai.com/blog/2024/04/24/tiktok-ban/#comment-4077796</link>
  920.  
  921. <dc:creator><![CDATA[Plume]]></dc:creator>
  922. <pubDate>Fri, 26 Apr 2024 06:59:53 +0000</pubDate>
  923. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42914#comment-4077796</guid>
  924.  
  925. <description><![CDATA[&quot;the government hasn’t provided clear-cut data for this, only vibes and fear-mongering&quot;
  926.  
  927. I think this is a huge cultural misunderstanding, where Westerners think &quot;oh, it&#039;s a private company, it has nothing to do with the Chinese government&quot;, whereas anyone living in China knows that there is no such thing as a private company in China, particularly not one that makes money, is used by Chinese people for communication, or has any sort of foreign soft power.
  928.  
  929. I think this ban is a terrible precedent, and I think going after data brokers and after algorithm-driven social media would be a better approach, but if you think for one second that the Chinese government has no influence on what kinds of things Tik Tok recommends because you saw a critical clip about Xinjiang on the app, you&#039;re misinformed.]]></description>
  930. <content:encoded><![CDATA[<p>"the government hasn’t provided clear-cut data for this, only vibes and fear-mongering"</p>
  931. <p>I think this is a huge cultural misunderstanding, where Westerners think "oh, it's a private company, it has nothing to do with the Chinese government", whereas anyone living in China knows that there is no such thing as a private company in China, particularly not one that makes money, is used by Chinese people for communication, or has any sort of foreign soft power.</p>
  932. <p>I think this ban is a terrible precedent, and I think going after data brokers and after algorithm-driven social media would be a better approach, but if you think for one second that the Chinese government has no influence on what kinds of things Tik Tok recommends because you saw a critical clip about Xinjiang on the app, you're misinformed.</p>
  933. ]]></content:encoded>
  934. </item>
  935. <item>
  936. <title>
  937. Comment on TikTok Ban by Old Unix Geek </title>
  938. <link>https://mjtsai.com/blog/2024/04/24/tiktok-ban/#comment-4077777</link>
  939.  
  940. <dc:creator><![CDATA[Old Unix Geek]]></dc:creator>
  941. <pubDate>Fri, 26 Apr 2024 06:13:45 +0000</pubDate>
  942. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42914#comment-4077777</guid>
  943.  
  944. <description><![CDATA[In case anyone is under the misapprehension that banning TikTok was purely a matter of principle without any other motives:
  945.  
  946. https://twitter.com/WallStreetApes/status/1783604715064029233#m]]></description>
  947. <content:encoded><![CDATA[<p>In case anyone is under the misapprehension that banning TikTok was purely a matter of principle without any other motives:</p>
  948. <p><a href="https://twitter.com/WallStreetApes/status/1783604715064029233#m" rel="nofollow ugc">https://twitter.com/WallStreetApes/status/1783604715064029233#m</a></p>
  949. ]]></content:encoded>
  950. </item>
  951. <item>
  952. <title>
  953. Comment on TikTok Ban by chris brandow </title>
  954. <link>https://mjtsai.com/blog/2024/04/24/tiktok-ban/#comment-4077694</link>
  955.  
  956. <dc:creator><![CDATA[chris brandow]]></dc:creator>
  957. <pubDate>Fri, 26 Apr 2024 01:26:30 +0000</pubDate>
  958. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42914#comment-4077694</guid>
  959.  
  960. <description><![CDATA[Good catch. I&#039;m not sure it&#039;s still that inconsistent with our current policy in this area, but this is useful context for me.]]></description>
  961. <content:encoded><![CDATA[<p>Good catch. I'm not sure it's still that inconsistent with our current policy in this area, but this is useful context for me.</p>
  962. ]]></content:encoded>
  963. </item>
  964. <item>
  965. <title>
  966. Comment on FTC Bans Noncompetes by Old Unix Geek </title>
  967. <link>https://mjtsai.com/blog/2024/04/25/ftc-bans-noncompetes/#comment-4077679</link>
  968.  
  969. <dc:creator><![CDATA[Old Unix Geek]]></dc:creator>
  970. <pubDate>Fri, 26 Apr 2024 00:37:51 +0000</pubDate>
  971. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42942#comment-4077679</guid>
  972.  
  973. <description><![CDATA[I&#039;m very glad about this. Non competes are a form of legalized slavery as far as I&#039;m concerned.]]></description>
  974. <content:encoded><![CDATA[<p>I'm very glad about this. Non competes are a form of legalized slavery as far as I'm concerned.</p>
  975. ]]></content:encoded>
  976. </item>
  977. <item>
  978. <title>
  979. Comment on TikTok Ban by Old Unix Geek </title>
  980. <link>https://mjtsai.com/blog/2024/04/24/tiktok-ban/#comment-4077678</link>
  981.  
  982. <dc:creator><![CDATA[Old Unix Geek]]></dc:creator>
  983. <pubDate>Fri, 26 Apr 2024 00:36:17 +0000</pubDate>
  984. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42914#comment-4077678</guid>
  985.  
  986. <description><![CDATA[@chris
  987.  
  988. It isn&#039;t competing for a limited resource (radio waves or wires). Also, the rule you cite isn&#039;t being enforced: https://www.broadcastlawblog.com/2017/02/articles/fcc-approves-for-the-first-time-100-foreign-ownership-of-us-broadcast-stations/]]></description>
  989. <content:encoded><![CDATA[<p>@chris</p>
  990. <p>It isn't competing for a limited resource (radio waves or wires). Also, the rule you cite isn't being enforced: <a href="https://www.broadcastlawblog.com/2017/02/articles/fcc-approves-for-the-first-time-100-foreign-ownership-of-us-broadcast-stations/" rel="nofollow ugc">https://www.broadcastlawblog.com/2017/02/articles/fcc-approves-for-the-first-time-100-foreign-ownership-of-us-broadcast-stations/</a></p>
  991. ]]></content:encoded>
  992. </item>
  993. <item>
  994. <title>
  995. Comment on TikTok Ban by chris brandow </title>
  996. <link>https://mjtsai.com/blog/2024/04/24/tiktok-ban/#comment-4077660</link>
  997.  
  998. <dc:creator><![CDATA[chris brandow]]></dc:creator>
  999. <pubDate>Thu, 25 Apr 2024 23:22:35 +0000</pubDate>
  1000. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42914#comment-4077660</guid>
  1001.  
  1002. <description><![CDATA[I don&#039;t understand why this is so much more of a travesty than existing FCC regulations we have regarding foreign ownership of broadcast tv, radio, common carriers, etc. Just because TikTok wasn&#039;t already covered by that, it certainly fits the intent of those rules.]]></description>
  1003. <content:encoded><![CDATA[<p>I don't understand why this is so much more of a travesty than existing FCC regulations we have regarding foreign ownership of broadcast tv, radio, common carriers, etc. Just because TikTok wasn't already covered by that, it certainly fits the intent of those rules.</p>
  1004. ]]></content:encoded>
  1005. </item>
  1006. <item>
  1007. <title>
  1008. Comment on TikTok Ban by Kristoffer </title>
  1009. <link>https://mjtsai.com/blog/2024/04/24/tiktok-ban/#comment-4077110</link>
  1010.  
  1011. <dc:creator><![CDATA[Kristoffer]]></dc:creator>
  1012. <pubDate>Thu, 25 Apr 2024 06:30:19 +0000</pubDate>
  1013. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42914#comment-4077110</guid>
  1014.  
  1015. <description><![CDATA[I think this is great news. I hope the US set a precedent and that the EU will start banning all social media apps that report back to their governments.
  1016.  
  1017. Begin with the big names, TikTok, Instagram, Facebook.]]></description>
  1018. <content:encoded><![CDATA[<p>I think this is great news. I hope the US set a precedent and that the EU will start banning all social media apps that report back to their governments. </p>
  1019. <p>Begin with the big names, TikTok, Instagram, Facebook.</p>
  1020. ]]></content:encoded>
  1021. </item>
  1022. <item>
  1023. <title>
  1024. Comment on TikTok Ban by Old Unix Geek </title>
  1025. <link>https://mjtsai.com/blog/2024/04/24/tiktok-ban/#comment-4077003</link>
  1026.  
  1027. <dc:creator><![CDATA[Old Unix Geek]]></dc:creator>
  1028. <pubDate>Thu, 25 Apr 2024 03:47:38 +0000</pubDate>
  1029. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42914#comment-4077003</guid>
  1030.  
  1031. <description><![CDATA[This is BS. It&#039;s about the idiots in power who just expanded FISA, violating the 4th amendment, having their panties in a twist because they can&#039;t censor TikTok as much as they&#039;d like and the young&#039;uns are not swallowing their kool-aid that Israel can do no wrong. If TikTok were American owned they&#039;d have more leverage. These are the same people who were elected to represent their constituents, but instead &quot;think they did the right thing having prayed and asked God and the CIA&quot;. They are the hypocrites who defend their own right to say whatever they want, but then advocate punishment for others when they speak.
  1032.  
  1033. If the US can force TikTok to divest inside the US, then others can force Google, Twitter, Apple, Microsoft, Meta, Amazon, Netflix, etc to divest from US ownership in their countries. It&#039;s not as if everyone on the planet appreciates being force-fed Western &quot;values&quot;. But I can already hear the screams of outrage in Washington if that were to happen.
  1034.  
  1035. And these people care so much about election interference, that they worry about __potential__ influence by some, but not about demonstrated election influence by others (AIPAC, censorship, military adjacent psy-ops like Cambridge Analytica or psy-group.com).
  1036.  
  1037. I guess I&#039;m really spitting fire today, to quote Nathan, but if there&#039;s one thing I truly despise, it is hypocrisy.]]></description>
  1038. <content:encoded><![CDATA[<p>This is BS. It's about the idiots in power who just expanded FISA, violating the 4th amendment, having their panties in a twist because they can't censor TikTok as much as they'd like and the young'uns are not swallowing their kool-aid that Israel can do no wrong. If TikTok were American owned they'd have more leverage. These are the same people who were elected to represent their constituents, but instead "think they did the right thing having prayed and asked God and the CIA". They are the hypocrites who defend their own right to say whatever they want, but then advocate punishment for others when they speak.</p>
  1039. <p>If the US can force TikTok to divest inside the US, then others can force Google, Twitter, Apple, Microsoft, Meta, Amazon, Netflix, etc to divest from US ownership in their countries. It's not as if everyone on the planet appreciates being force-fed Western "values". But I can already hear the screams of outrage in Washington if that were to happen.</p>
  1040. <p>And these people care so much about election interference, that they worry about __potential__ influence by some, but not about demonstrated election influence by others (AIPAC, censorship, military adjacent psy-ops like Cambridge Analytica or psy-group.com).</p>
  1041. <p>I guess I'm really spitting fire today, to quote Nathan, but if there's one thing I truly despise, it is hypocrisy.</p>
  1042. ]]></content:encoded>
  1043. </item>
  1044. <item>
  1045. <title>
  1046. Comment on TikTok Ban by Michael Tsai </title>
  1047. <link>https://mjtsai.com/blog/2024/04/24/tiktok-ban/#comment-4076780</link>
  1048.  
  1049. <dc:creator><![CDATA[Michael Tsai]]></dc:creator>
  1050. <pubDate>Wed, 24 Apr 2024 20:34:24 +0000</pubDate>
  1051. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42914#comment-4076780</guid>
  1052.  
  1053. <description><![CDATA[@Nathan My understanding is that the proof was presented &lt;em&gt;to&lt;/em&gt; Congress, and that the public doesn’t have access to it.]]></description>
  1054. <content:encoded><![CDATA[<p>@Nathan My understanding is that the proof was presented <em>to</em> Congress, and that the public doesn’t have access to it.</p>
  1055. ]]></content:encoded>
  1056. </item>
  1057. <item>
  1058. <title>
  1059. Comment on TikTok Ban by Nathan </title>
  1060. <link>https://mjtsai.com/blog/2024/04/24/tiktok-ban/#comment-4076775</link>
  1061.  
  1062. <dc:creator><![CDATA[Nathan]]></dc:creator>
  1063. <pubDate>Wed, 24 Apr 2024 20:25:23 +0000</pubDate>
  1064. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42914#comment-4076775</guid>
  1065.  
  1066. <description><![CDATA[Can someone confirm that the allegations presented by Congress (and not so secretly by American competitors to TikTok) have actually been proven?]]></description>
  1067. <content:encoded><![CDATA[<p>Can someone confirm that the allegations presented by Congress (and not so secretly by American competitors to TikTok) have actually been proven?</p>
  1068. ]]></content:encoded>
  1069. </item>
  1070. <item>
  1071. <title>
  1072. Comment on TikTok Ban by Nathan </title>
  1073. <link>https://mjtsai.com/blog/2024/04/24/tiktok-ban/#comment-4076772</link>
  1074.  
  1075. <dc:creator><![CDATA[Nathan]]></dc:creator>
  1076. <pubDate>Wed, 24 Apr 2024 20:21:48 +0000</pubDate>
  1077. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42914#comment-4076772</guid>
  1078.  
  1079. <description><![CDATA[@vintner
  1080. Yep. Shockingly similar sometimes.]]></description>
  1081. <content:encoded><![CDATA[<p>@vintner<br />
  1082. Yep. Shockingly similar sometimes.</p>
  1083. ]]></content:encoded>
  1084. </item>
  1085. <item>
  1086. <title>
  1087. Comment on TikTok Ban by vintner </title>
  1088. <link>https://mjtsai.com/blog/2024/04/24/tiktok-ban/#comment-4076703</link>
  1089.  
  1090. <dc:creator><![CDATA[vintner]]></dc:creator>
  1091. <pubDate>Wed, 24 Apr 2024 18:27:46 +0000</pubDate>
  1092. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42914#comment-4076703</guid>
  1093.  
  1094. <description><![CDATA[Today&#039;s pair of articles are testaments to how bipartisanship is still possible, when it&#039;s in service of the stupid and the horrible.]]></description>
  1095. <content:encoded><![CDATA[<p>Today's pair of articles are testaments to how bipartisanship is still possible, when it's in service of the stupid and the horrible.</p>
  1096. ]]></content:encoded>
  1097. </item>
  1098. <item>
  1099. <title>
  1100. Comment on Legibility and San Francisco by Anna </title>
  1101. <link>https://mjtsai.com/blog/2024/04/18/legibility-and-san-francisco/#comment-4076667</link>
  1102.  
  1103. <dc:creator><![CDATA[Anna]]></dc:creator>
  1104. <pubDate>Wed, 24 Apr 2024 17:33:53 +0000</pubDate>
  1105. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42882#comment-4076667</guid>
  1106.  
  1107. <description><![CDATA[@Niko Kitsakis
  1108.  
  1109. I fully agree with you. I said that SF Pro is optimised for small scale, and not general legibility.  I listen to what I see. Apple is moving within a very narrow design window and yes, those other typefaces are more legible.
  1110.  
  1111. SF is like, amazing how many letters fit in the viewport, and I find that it works well in that regard. Letters are nicely spaced and decernible..Great esthetics, too, unless, well, you understand esthetics to have something to do with perception in practice and not just design beauty.
  1112.  
  1113. I have a hunch there’s a reason books were printed in larger letters than instruction manuals. Reading as a cultural technique is facing challenges.]]></description>
  1114. <content:encoded><![CDATA[<p>@Niko Kitsakis</p>
  1115. <p>I fully agree with you. I said that SF Pro is optimised for small scale, and not general legibility.  I listen to what I see. Apple is moving within a very narrow design window and yes, those other typefaces are more legible.</p>
  1116. <p>SF is like, amazing how many letters fit in the viewport, and I find that it works well in that regard. Letters are nicely spaced and decernible..Great esthetics, too, unless, well, you understand esthetics to have something to do with perception in practice and not just design beauty. </p>
  1117. <p>I have a hunch there’s a reason books were printed in larger letters than instruction manuals. Reading as a cultural technique is facing challenges.</p>
  1118. ]]></content:encoded>
  1119. </item>
  1120. <item>
  1121. <title>
  1122. Comment on Hackintosh Is Almost Dead by Nathan </title>
  1123. <link>https://mjtsai.com/blog/2024/04/22/hackintosh-is-almost-dead/#comment-4076550</link>
  1124.  
  1125. <dc:creator><![CDATA[Nathan]]></dc:creator>
  1126. <pubDate>Wed, 24 Apr 2024 15:03:57 +0000</pubDate>
  1127. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42896#comment-4076550</guid>
  1128.  
  1129. <description><![CDATA[@Bri
  1130. I don&#039;t disagree. Lot of fear mongering without explaining what purpose the actual feature serves. I think people willing to run MacOS on whitebox PCs understand some risk involved anyway and can decide for themselves what they want to do.]]></description>
  1131. <content:encoded><![CDATA[<p>@Bri<br />
  1132. I don't disagree. Lot of fear mongering without explaining what purpose the actual feature serves. I think people willing to run MacOS on whitebox PCs understand some risk involved anyway and can decide for themselves what they want to do.</p>
  1133. ]]></content:encoded>
  1134. </item>
  1135. <item>
  1136. <title>
  1137. Comment on Apple Removes Messaging Apps From Chinese App Store by Nathan </title>
  1138. <link>https://mjtsai.com/blog/2024/04/19/apple-removes-messaging-apps-from-chinese-app-store/#comment-4076547</link>
  1139.  
  1140. <dc:creator><![CDATA[Nathan]]></dc:creator>
  1141. <pubDate>Wed, 24 Apr 2024 14:54:48 +0000</pubDate>
  1142. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42892#comment-4076547</guid>
  1143.  
  1144. <description><![CDATA[Or Apple could, well, you know, allow side loading and most of these problems go away.]]></description>
  1145. <content:encoded><![CDATA[<p>Or Apple could, well, you know, allow side loading and most of these problems go away.</p>
  1146. ]]></content:encoded>
  1147. </item>
  1148. <item>
  1149. <title>
  1150. Comment on The Apple Jonathan by Nathan </title>
  1151. <link>https://mjtsai.com/blog/2024/04/22/the-apple-jonathan/#comment-4076546</link>
  1152.  
  1153. <dc:creator><![CDATA[Nathan]]></dc:creator>
  1154. <pubDate>Wed, 24 Apr 2024 14:51:03 +0000</pubDate>
  1155. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42894#comment-4076546</guid>
  1156.  
  1157. <description><![CDATA[So this is absolutely fascinating and the reported reason for killing the product was strange, but I&#039;m not sure how feasible it would be to get it working anyway. The Macs with Apple II or DOS cards certainly weren&#039;t very inexpensive once you got everything going. I&#039;m curious how the backbone would work and interface with all the &quot;books&quot;, wouldn&#039;t you need a fast data bus for all these things to interact?]]></description>
  1158. <content:encoded><![CDATA[<p>So this is absolutely fascinating and the reported reason for killing the product was strange, but I'm not sure how feasible it would be to get it working anyway. The Macs with Apple II or DOS cards certainly weren't very inexpensive once you got everything going. I'm curious how the backbone would work and interface with all the "books", wouldn't you need a fast data bus for all these things to interact?</p>
  1159. ]]></content:encoded>
  1160. </item>
  1161. <item>
  1162. <title>
  1163. Comment on Legibility and San Francisco by Niko Kitsakis </title>
  1164. <link>https://mjtsai.com/blog/2024/04/18/legibility-and-san-francisco/#comment-4076342</link>
  1165.  
  1166. <dc:creator><![CDATA[Niko Kitsakis]]></dc:creator>
  1167. <pubDate>Wed, 24 Apr 2024 07:48:48 +0000</pubDate>
  1168. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42882#comment-4076342</guid>
  1169.  
  1170. <description><![CDATA[@Anna
  1171. What is “It is optimised for legibility at small scale, not general legibility.”? SF Pro? Not if you listen to what Apple says about it. According to them, it’s supposed to be legible in any use case. And that’s simply not the case. FF Unit, Fira (almost all typefaces by Erik Spiekermann really) are MUCH more legible than SF Pro.]]></description>
  1172. <content:encoded><![CDATA[<p>@Anna<br />
  1173. What is “It is optimised for legibility at small scale, not general legibility.”? SF Pro? Not if you listen to what Apple says about it. According to them, it’s supposed to be legible in any use case. And that’s simply not the case. FF Unit, Fira (almost all typefaces by Erik Spiekermann really) are MUCH more legible than SF Pro.</p>
  1174. ]]></content:encoded>
  1175. </item>
  1176. <item>
  1177. <title>
  1178. Comment on Fairphone Fairbuds by Kristoffer </title>
  1179. <link>https://mjtsai.com/blog/2024/04/23/fairphone-fairbuds/#comment-4076204</link>
  1180.  
  1181. <dc:creator><![CDATA[Kristoffer]]></dc:creator>
  1182. <pubDate>Wed, 24 Apr 2024 03:56:14 +0000</pubDate>
  1183. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42905#comment-4076204</guid>
  1184.  
  1185. <description><![CDATA[People keep saying that, yet I&#039;m unaware of an alternative.]]></description>
  1186. <content:encoded><![CDATA[<p>People keep saying that, yet I'm unaware of an alternative.</p>
  1187. ]]></content:encoded>
  1188. </item>
  1189. <item>
  1190. <title>
  1191. Comment on Fairphone Fairbuds by Bri </title>
  1192. <link>https://mjtsai.com/blog/2024/04/23/fairphone-fairbuds/#comment-4076103</link>
  1193.  
  1194. <dc:creator><![CDATA[Bri]]></dc:creator>
  1195. <pubDate>Tue, 23 Apr 2024 23:41:19 +0000</pubDate>
  1196. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42905#comment-4076103</guid>
  1197.  
  1198. <description><![CDATA[I would consider getting these if Bluetooth wasn&#039;t so awful.]]></description>
  1199. <content:encoded><![CDATA[<p>I would consider getting these if Bluetooth wasn't so awful.</p>
  1200. ]]></content:encoded>
  1201. </item>
  1202. <item>
  1203. <title>
  1204. Comment on Apple Maps in Tokyo by Bri </title>
  1205. <link>https://mjtsai.com/blog/2024/04/22/apple-maps-in-tokyo/#comment-4076102</link>
  1206.  
  1207. <dc:creator><![CDATA[Bri]]></dc:creator>
  1208. <pubDate>Tue, 23 Apr 2024 23:40:11 +0000</pubDate>
  1209. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42898#comment-4076102</guid>
  1210.  
  1211. <description><![CDATA[&quot;Apple Maps is also bad if you move the map to an area and want to search within that area. It’ll snap back to where you are and search that area first.&quot;
  1212.  
  1213. This has made me fly into a rage so many times.]]></description>
  1214. <content:encoded><![CDATA[<p>"Apple Maps is also bad if you move the map to an area and want to search within that area. It’ll snap back to where you are and search that area first."</p>
  1215. <p>This has made me fly into a rage so many times.</p>
  1216. ]]></content:encoded>
  1217. </item>
  1218. <item>
  1219. <title>
  1220. Comment on Hackintosh Is Almost Dead by Bri </title>
  1221. <link>https://mjtsai.com/blog/2024/04/22/hackintosh-is-almost-dead/#comment-4076101</link>
  1222.  
  1223. <dc:creator><![CDATA[Bri]]></dc:creator>
  1224. <pubDate>Tue, 23 Apr 2024 23:38:48 +0000</pubDate>
  1225. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42896#comment-4076101</guid>
  1226.  
  1227. <description><![CDATA[I object to people saying that disabling SIP and disabling secure boot will &quot;seriously downgrade&quot; a mac&#039;s security. macOS didn&#039;t have them before 10.11, and back then the mac had great security. The mac still has great security now if you disable them, which I do, because I like using my mac the way I like to and not only the ways Apple ordains.
  1228.  
  1229. The trick to mac security is the same as it always was: don&#039;t run malicious software. If you do, SIP and secure boot isn&#039;t going to save you.]]></description>
  1230. <content:encoded><![CDATA[<p>I object to people saying that disabling SIP and disabling secure boot will "seriously downgrade" a mac's security. macOS didn't have them before 10.11, and back then the mac had great security. The mac still has great security now if you disable them, which I do, because I like using my mac the way I like to and not only the ways Apple ordains.</p>
  1231. <p>The trick to mac security is the same as it always was: don't run malicious software. If you do, SIP and secure boot isn't going to save you.</p>
  1232. ]]></content:encoded>
  1233. </item>
  1234. <item>
  1235. <title>
  1236. Comment on It&#8217;s Time for a New AirPort by Nathan </title>
  1237. <link>https://mjtsai.com/blog/2024/04/17/its-time-for-a-new-airport/#comment-4076017</link>
  1238.  
  1239. <dc:creator><![CDATA[Nathan]]></dc:creator>
  1240. <pubDate>Tue, 23 Apr 2024 20:35:55 +0000</pubDate>
  1241. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42875#comment-4076017</guid>
  1242.  
  1243. <description><![CDATA[@Sebby
  1244. Thank you!!!! When I had Airport routers, I started using the Airport Express as a WiFi bridge for older 802.11b/g and non WiFi devices and it worked really well for those devices that couldn&#039;t be wired easily with Ethernet directly from the router. So good to know the last generation model had the same ability, as underutilized as it might have been.
  1245.  
  1246. Another cool feature of Airport routers that basically no one talks about was Bonjour Sleep Proxy, where a Mac on your network could stay asleep until a device called it for a shared service. It was literally a checkbox and things &quot;just worked&quot; is my memory (getting older though, beware the memories); whereas, I feel like setting up a magic packet wakeup on Linux and similar was a little more involved. I loved that feature. My home server was a Mac mini (a couple different models) for many years and it could stay asleep when not running backups or serving media, which was the primary use case for the device. Saved a lot of energy. The trick was the Airport router kept broadcasting all the available services for the sleeping computer so clients could still see them and then request a connection, thus waking up the sleeping Mac.]]></description>
  1247. <content:encoded><![CDATA[<p>@Sebby<br />
  1248. Thank you!!!! When I had Airport routers, I started using the Airport Express as a WiFi bridge for older 802.11b/g and non WiFi devices and it worked really well for those devices that couldn't be wired easily with Ethernet directly from the router. So good to know the last generation model had the same ability, as underutilized as it might have been.</p>
  1249. <p>Another cool feature of Airport routers that basically no one talks about was Bonjour Sleep Proxy, where a Mac on your network could stay asleep until a device called it for a shared service. It was literally a checkbox and things "just worked" is my memory (getting older though, beware the memories); whereas, I feel like setting up a magic packet wakeup on Linux and similar was a little more involved. I loved that feature. My home server was a Mac mini (a couple different models) for many years and it could stay asleep when not running backups or serving media, which was the primary use case for the device. Saved a lot of energy. The trick was the Airport router kept broadcasting all the available services for the sleeping computer so clients could still see them and then request a connection, thus waking up the sleeping Mac.</p>
  1250. ]]></content:encoded>
  1251. </item>
  1252. <item>
  1253. <title>
  1254. Comment on Apple Maps in Tokyo by Sam </title>
  1255. <link>https://mjtsai.com/blog/2024/04/22/apple-maps-in-tokyo/#comment-4076011</link>
  1256.  
  1257. <dc:creator><![CDATA[Sam]]></dc:creator>
  1258. <pubDate>Tue, 23 Apr 2024 20:23:18 +0000</pubDate>
  1259. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42898#comment-4076011</guid>
  1260.  
  1261. <description><![CDATA[@Exhik&#039;s problem is very similar to how Apple Maps functions (or doesn&#039;t) in Korea too. Google is pretty good at figuring out place names in either English spellings or Korean. Apple Maps, meanwhile, is weird. Some places exist only by Korean name, some only apparently by that name in English. Many addresses are missing completely, and Apple seems to often confuse the order of the address parts (like most of Asia, locations go from bigger to smaller, not vice versa). Here too they seem to get their data from a local partner (similar to Google), but seem to struggle incorporating that data into the standard Maps functionality. My &quot;Home&quot; address cannot be saved, so I can never ask Siri for directions home. I can drop a pin in my home, and use that for manually starting navigation. Of course navigation is much less effective here than in USA. It often gives me routes that are wildly inefficient or impossible due to traffic rules. Of course it lacks any of the toll gate or lane info, and often wants me to make turns that are illegal. Additionally, there is no public transit or biking directions whatsoever. It&#039;s just a fundamentally sub-par experience. Everyone here uses a local map app anyway, so I doubt anyone but tourists would even try using Apple Maps here. Good luck to them: finding their destinations is going to be difficult.]]></description>
  1262. <content:encoded><![CDATA[<p>@Exhik's problem is very similar to how Apple Maps functions (or doesn't) in Korea too. Google is pretty good at figuring out place names in either English spellings or Korean. Apple Maps, meanwhile, is weird. Some places exist only by Korean name, some only apparently by that name in English. Many addresses are missing completely, and Apple seems to often confuse the order of the address parts (like most of Asia, locations go from bigger to smaller, not vice versa). Here too they seem to get their data from a local partner (similar to Google), but seem to struggle incorporating that data into the standard Maps functionality. My "Home" address cannot be saved, so I can never ask Siri for directions home. I can drop a pin in my home, and use that for manually starting navigation. Of course navigation is much less effective here than in USA. It often gives me routes that are wildly inefficient or impossible due to traffic rules. Of course it lacks any of the toll gate or lane info, and often wants me to make turns that are illegal. Additionally, there is no public transit or biking directions whatsoever. It's just a fundamentally sub-par experience. Everyone here uses a local map app anyway, so I doubt anyone but tourists would even try using Apple Maps here. Good luck to them: finding their destinations is going to be difficult.</p>
  1263. ]]></content:encoded>
  1264. </item>
  1265. <item>
  1266. <title>
  1267. Comment on Hackintosh Is Almost Dead by Daniël de Kok </title>
  1268. <link>https://mjtsai.com/blog/2024/04/22/hackintosh-is-almost-dead/#comment-4075972</link>
  1269.  
  1270. <dc:creator><![CDATA[Daniël de Kok]]></dc:creator>
  1271. <pubDate>Tue, 23 Apr 2024 18:57:57 +0000</pubDate>
  1272. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42896#comment-4075972</guid>
  1273.  
  1274. <description><![CDATA[I started using Macs because of Hackintosh. A family member and I were both Linux users and we thought it would be fun project to try to run Hackintosh. OS X 10.4 did run on his hardware, but not on mine. After I heard him rave about OS X, I decided to pick up a Mac Mini to see what all the fuzz is about and now I have used Macs for almost 17 years..]]></description>
  1275. <content:encoded><![CDATA[<p>I started using Macs because of Hackintosh. A family member and I were both Linux users and we thought it would be fun project to try to run Hackintosh. OS X 10.4 did run on his hardware, but not on mine. After I heard him rave about OS X, I decided to pick up a Mac Mini to see what all the fuzz is about and now I have used Macs for almost 17 years..</p>
  1276. ]]></content:encoded>
  1277. </item>
  1278. <item>
  1279. <title>
  1280. Comment on Optimizing WebKit &#038; Safari for Speedometer 3.0 by JK </title>
  1281. <link>https://mjtsai.com/blog/2024/04/19/optimizing-webkit-safari-for-speedometer-3-0/#comment-4075948</link>
  1282.  
  1283. <dc:creator><![CDATA[JK]]></dc:creator>
  1284. <pubDate>Tue, 23 Apr 2024 17:50:42 +0000</pubDate>
  1285. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42886#comment-4075948</guid>
  1286.  
  1287. <description><![CDATA[Rerun with private windows and no extensions Safari scored 24.1 along with Brave while Firefox scored 28.1. Interesting benchmark.]]></description>
  1288. <content:encoded><![CDATA[<p>Rerun with private windows and no extensions Safari scored 24.1 along with Brave while Firefox scored 28.1. Interesting benchmark.</p>
  1289. ]]></content:encoded>
  1290. </item>
  1291. <item>
  1292. <title>
  1293. Comment on Optimizing WebKit &#038; Safari for Speedometer 3.0 by JK </title>
  1294. <link>https://mjtsai.com/blog/2024/04/19/optimizing-webkit-safari-for-speedometer-3-0/#comment-4075943</link>
  1295.  
  1296. <dc:creator><![CDATA[JK]]></dc:creator>
  1297. <pubDate>Tue, 23 Apr 2024 17:45:48 +0000</pubDate>
  1298. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42886#comment-4075943</guid>
  1299.  
  1300. <description><![CDATA[Oddly Safari is the slowest of the three browsers by quite a bit when I ran this test (Safari 17.4.1 on Sonoma on an M3Pro MBP) with a score of 17.1. Brave came in second at 25.1 with Firefox beating them both at 25.9.]]></description>
  1301. <content:encoded><![CDATA[<p>Oddly Safari is the slowest of the three browsers by quite a bit when I ran this test (Safari 17.4.1 on Sonoma on an M3Pro MBP) with a score of 17.1. Brave came in second at 25.1 with Firefox beating them both at 25.9.</p>
  1302. ]]></content:encoded>
  1303. </item>
  1304. <item>
  1305. <title>
  1306. Comment on Color Kobo E-readers by Nathan </title>
  1307. <link>https://mjtsai.com/blog/2024/04/19/color-kobo-e-readers/#comment-4075905</link>
  1308.  
  1309. <dc:creator><![CDATA[Nathan]]></dc:creator>
  1310. <pubDate>Tue, 23 Apr 2024 16:11:43 +0000</pubDate>
  1311. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42888#comment-4075905</guid>
  1312.  
  1313. <description><![CDATA[Not in the market right now, but very intrigued. I feel like Kobo is one of the best hardware platform right now, from afar admittedly, given they seem to release a lot of compelling devices, even compared to the other two main American competitors in Amazon and Barnes and Noble. However, I&#039;m guessing market lock-in will largely keep Amazon in the lead, which is a shame honestly. Then again, I haven&#039;t used a modern Kindle nor Kobo to compare store, app, and syncing experiences. So that could be key too. Still, I love the competition.]]></description>
  1314. <content:encoded><![CDATA[<p>Not in the market right now, but very intrigued. I feel like Kobo is one of the best hardware platform right now, from afar admittedly, given they seem to release a lot of compelling devices, even compared to the other two main American competitors in Amazon and Barnes and Noble. However, I'm guessing market lock-in will largely keep Amazon in the lead, which is a shame honestly. Then again, I haven't used a modern Kindle nor Kobo to compare store, app, and syncing experiences. So that could be key too. Still, I love the competition.</p>
  1315. ]]></content:encoded>
  1316. </item>
  1317. <item>
  1318. <title>
  1319. Comment on VLC vs. the App Stores by Nathan </title>
  1320. <link>https://mjtsai.com/blog/2024/04/19/vlc-vs-the-app-stores/#comment-4075902</link>
  1321.  
  1322. <dc:creator><![CDATA[Nathan]]></dc:creator>
  1323. <pubDate>Tue, 23 Apr 2024 16:07:15 +0000</pubDate>
  1324. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42890#comment-4075902</guid>
  1325.  
  1326. <description><![CDATA[@Joshua Ochs
  1327. I think many apps have concerns with app store distribution and VLC has been one of them from the beginning. App stores can be user focused, but iOS and Google Play are not two examples of them. Not developer focused either. At least Android largely allows side loading (I think some embedded stuff tries to disable it though).
  1328.  
  1329. F-Droid is a better example and not sure why, as @Rito mentioned, the F-Droid version is so far behind?]]></description>
  1330. <content:encoded><![CDATA[<p>@Joshua Ochs<br />
  1331. I think many apps have concerns with app store distribution and VLC has been one of them from the beginning. App stores can be user focused, but iOS and Google Play are not two examples of them. Not developer focused either. At least Android largely allows side loading (I think some embedded stuff tries to disable it though).</p>
  1332. <p>F-Droid is a better example and not sure why, as @Rito mentioned, the F-Droid version is so far behind?</p>
  1333. ]]></content:encoded>
  1334. </item>
  1335. <item>
  1336. <title>
  1337. Comment on Cryptocurrency Apple Antitrust Lawsuit by Marc </title>
  1338. <link>https://mjtsai.com/blog/2024/04/18/cryptocurrency-apple-antitrust-lawsuit/#comment-4075878</link>
  1339.  
  1340. <dc:creator><![CDATA[Marc]]></dc:creator>
  1341. <pubDate>Tue, 23 Apr 2024 15:00:03 +0000</pubDate>
  1342. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42878#comment-4075878</guid>
  1343.  
  1344. <description><![CDATA[For crypto-currencies or digital payments, it is mathematically proven that &quot;send payments to each other without any intermediary at all&quot; is not possible.
  1345. See https://en.wikipedia.org/wiki/CAP_theorem
  1346.  
  1347. The problem is double-spending. Just imagine the sender makes a copy of the digital coin, and gives that to a third person. Which of the receivers has the real coin now?
  1348.  
  1349. Last month, I even had to remember the ECB of that, when they claimed the Digital Euro would be capable of doing this:
  1350. https://twitter.com/taler/status/1767621751825907879
  1351. Political intentions are not always compatible with the laws of nature...]]></description>
  1352. <content:encoded><![CDATA[<p>For crypto-currencies or digital payments, it is mathematically proven that "send payments to each other without any intermediary at all" is not possible.<br />
  1353. See <a href="https://en.wikipedia.org/wiki/CAP_theorem" rel="nofollow ugc">https://en.wikipedia.org/wiki/CAP_theorem</a></p>
  1354. <p>The problem is double-spending. Just imagine the sender makes a copy of the digital coin, and gives that to a third person. Which of the receivers has the real coin now?</p>
  1355. <p>Last month, I even had to remember the ECB of that, when they claimed the Digital Euro would be capable of doing this:<br />
  1356. <a href="https://twitter.com/taler/status/1767621751825907879" rel="nofollow ugc">https://twitter.com/taler/status/1767621751825907879</a><br />
  1357. Political intentions are not always compatible with the laws of nature...</p>
  1358. ]]></content:encoded>
  1359. </item>
  1360. <item>
  1361. <title>
  1362. Comment on Should Game Porting Toolkit Be Built-In? by tweakbsd </title>
  1363. <link>https://mjtsai.com/blog/2024/03/01/should-game-porting-toolkit-be-built-in/#comment-4075857</link>
  1364.  
  1365. <dc:creator><![CDATA[tweakbsd]]></dc:creator>
  1366. <pubDate>Tue, 23 Apr 2024 14:11:06 +0000</pubDate>
  1367. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42317#comment-4075857</guid>
  1368.  
  1369. <description><![CDATA[The main problem for Proton on Mac was the lack of Vulkan APIs to translate all DirectX calls. Apple now made a proprietary  D3DMetal Library which does exactly that. If they want Games on the Mac, they could definitely go the route Valve chose. Apple has enough Man-Power to make that happen without embarrasing themselves. But the problem here is they have not ONE device like the Steam Deck to support but from M1 up to M3 Max devices plus use their Rosetta 2 technology to translate to ARM instruction set. They would have to update Rosetta 2 even, because it lacks support for some instructions like AVX which PC games are free to use of course. But that&#039;s all doable. I really wish they would go that way and integrate it into their OS like Steam Deck showed us, but not gonna happen. They want PC game makers to port to Mac and deliver their apps through App Store which BTW is a pain in the butt for games since downloads need TWICE the space of a game to be even installed. No delta patch support and more shenanigan&#039;s I probably don&#039;t know of. Apple also would need to bring back eGPU support in my mind to show they have a competive  hardware product. Their iGPU solution is find for casual games but most demanding AAA titles not so much.]]></description>
  1370. <content:encoded><![CDATA[<p>The main problem for Proton on Mac was the lack of Vulkan APIs to translate all DirectX calls. Apple now made a proprietary  D3DMetal Library which does exactly that. If they want Games on the Mac, they could definitely go the route Valve chose. Apple has enough Man-Power to make that happen without embarrasing themselves. But the problem here is they have not ONE device like the Steam Deck to support but from M1 up to M3 Max devices plus use their Rosetta 2 technology to translate to ARM instruction set. They would have to update Rosetta 2 even, because it lacks support for some instructions like AVX which PC games are free to use of course. But that's all doable. I really wish they would go that way and integrate it into their OS like Steam Deck showed us, but not gonna happen. They want PC game makers to port to Mac and deliver their apps through App Store which BTW is a pain in the butt for games since downloads need TWICE the space of a game to be even installed. No delta patch support and more shenanigan's I probably don't know of. Apple also would need to bring back eGPU support in my mind to show they have a competive  hardware product. Their iGPU solution is find for casual games but most demanding AAA titles not so much.</p>
  1371. ]]></content:encoded>
  1372. </item>
  1373. <item>
  1374. <title>
  1375. Comment on Apple Maps in Tokyo by Ezhik </title>
  1376. <link>https://mjtsai.com/blog/2024/04/22/apple-maps-in-tokyo/#comment-4075851</link>
  1377.  
  1378. <dc:creator><![CDATA[Ezhik]]></dc:creator>
  1379. <pubDate>Tue, 23 Apr 2024 13:55:15 +0000</pubDate>
  1380. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42898#comment-4075851</guid>
  1381.  
  1382. <description><![CDATA[I&#039;ve given up on Apple Maps since it *still* has problems with Japanese addresses written out in Romaji (Latin alphabet). It once took me like 2 kilometers away because it decided to flip some numbers around (3-1-1 turned into a 1-3-1). Even more insulting is the fact that when I type out the address in Japanese on a device set to English, it&#039;ll just show the very same address it just failed to look up properly, translated to English.
  1383.  
  1384. I really did give Apple Maps a shot, but when it can&#039;t handle addresses typed in a pretty standard format, what else is left for me to try? Give it raw GPS coordinates?]]></description>
  1385. <content:encoded><![CDATA[<p>I've given up on Apple Maps since it *still* has problems with Japanese addresses written out in Romaji (Latin alphabet). It once took me like 2 kilometers away because it decided to flip some numbers around (3-1-1 turned into a 1-3-1). Even more insulting is the fact that when I type out the address in Japanese on a device set to English, it'll just show the very same address it just failed to look up properly, translated to English. </p>
  1386. <p>I really did give Apple Maps a shot, but when it can't handle addresses typed in a pretty standard format, what else is left for me to try? Give it raw GPS coordinates?</p>
  1387. ]]></content:encoded>
  1388. </item>
  1389. <item>
  1390. <title>
  1391. Comment on It&#8217;s Time for a New AirPort by Michael Tsai </title>
  1392. <link>https://mjtsai.com/blog/2024/04/17/its-time-for-a-new-airport/#comment-4075837</link>
  1393.  
  1394. <dc:creator><![CDATA[Michael Tsai]]></dc:creator>
  1395. <pubDate>Tue, 23 Apr 2024 13:21:21 +0000</pubDate>
  1396. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42875#comment-4075837</guid>
  1397.  
  1398. <description><![CDATA[@Nathan OK, I just tested it, and the speed is about 1.3 Mbps down and 0.1 Mbps up. This is with &lt;a href=&quot;https://boom.us/collections/plans&quot; rel=&quot;nofollow ugc&quot;&gt;Boom Red&lt;/a&gt;, where $32/month gets you 10 GB, since I’ve found the Verizon network to have fewer dead zones in my area. &lt;a href=&quot;https://www.mintmobile.com/plans/&quot; rel=&quot;nofollow ugc&quot;&gt;Mint Mobile&lt;/a&gt; (on the T-Mobile network) is less expensive but has the worst coverage in my area. AT&amp;T is in between.]]></description>
  1399. <content:encoded><![CDATA[<p>@Nathan OK, I just tested it, and the speed is about 1.3 Mbps down and 0.1 Mbps up. This is with <a href="https://boom.us/collections/plans" rel="nofollow ugc">Boom Red</a>, where $32/month gets you 10 GB, since I’ve found the Verizon network to have fewer dead zones in my area. <a href="https://www.mintmobile.com/plans/" rel="nofollow ugc">Mint Mobile</a> (on the T-Mobile network) is less expensive but has the worst coverage in my area. AT&#038;T is in between.</p>
  1400. ]]></content:encoded>
  1401. </item>
  1402. <item>
  1403. <title>
  1404. Comment on macOS 14 Sonoma vs. exFAT by Michael Tsai </title>
  1405. <link>https://mjtsai.com/blog/2024/04/17/macos-14-sonoma-vs-exfat/#comment-4075834</link>
  1406.  
  1407. <dc:creator><![CDATA[Michael Tsai]]></dc:creator>
  1408. <pubDate>Tue, 23 Apr 2024 13:16:53 +0000</pubDate>
  1409. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42873#comment-4075834</guid>
  1410.  
  1411. <description><![CDATA[@Nathan Yes, both automount and manual mount sometimes fail. I haven’t noticed a pattern with around half a dozen distinct enclosure types (not sure of chipsets) and 50 or so drives of different brands. The problem occurs for 2.5-inch and 3.5-inch spinning hard drives as well as SSDs.]]></description>
  1412. <content:encoded><![CDATA[<p>@Nathan Yes, both automount and manual mount sometimes fail. I haven’t noticed a pattern with around half a dozen distinct enclosure types (not sure of chipsets) and 50 or so drives of different brands. The problem occurs for 2.5-inch and 3.5-inch spinning hard drives as well as SSDs.</p>
  1413. ]]></content:encoded>
  1414. </item>
  1415. <item>
  1416. <title>
  1417. Comment on It&#8217;s Time for a New AirPort by Sebby </title>
  1418. <link>https://mjtsai.com/blog/2024/04/17/its-time-for-a-new-airport/#comment-4075522</link>
  1419.  
  1420. <dc:creator><![CDATA[Sebby]]></dc:creator>
  1421. <pubDate>Tue, 23 Apr 2024 06:07:50 +0000</pubDate>
  1422. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42875#comment-4075522</guid>
  1423.  
  1424. <description><![CDATA[@Nathan I have and treasure my latest-gen dual-band Express and yes it supports &quot;Proxy STA&quot; mode. It is a great way to add a (slow) Ethernet port over Wi-Fi, as well as AirPlay. But since it has the two ports, it generally makes more sense to just turn off the Wi-Fi entirely and simply use it as an AirPlay-enabled fast-ethernet switch.]]></description>
  1425. <content:encoded><![CDATA[<p>@Nathan I have and treasure my latest-gen dual-band Express and yes it supports "Proxy STA" mode. It is a great way to add a (slow) Ethernet port over Wi-Fi, as well as AirPlay. But since it has the two ports, it generally makes more sense to just turn off the Wi-Fi entirely and simply use it as an AirPlay-enabled fast-ethernet switch.</p>
  1426. ]]></content:encoded>
  1427. </item>
  1428. <item>
  1429. <title>
  1430. Comment on Hackintosh Is Almost Dead by Sebby </title>
  1431. <link>https://mjtsai.com/blog/2024/04/22/hackintosh-is-almost-dead/#comment-4075511</link>
  1432.  
  1433. <dc:creator><![CDATA[Sebby]]></dc:creator>
  1434. <pubDate>Tue, 23 Apr 2024 05:53:06 +0000</pubDate>
  1435. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42896#comment-4075511</guid>
  1436.  
  1437. <description><![CDATA[Yeah, that&#039;s cool. The only Hackintosh you&#039;d want to run nowadays is a VM, anyway. And, God willing, the fine folks at VMware and the QEMU/KVM projects continue to support macOS guests. At this stage my Intel Mac fleet is most useful for running non-macOS, and as Nathan rightly says, it&#039;s just very hard to justify that on an ongoing basis; likewise, macOS as a platform, except for portable computers, that run non-macOS VMs, or Mac Minis, that do likewise, as servers with capability to build for Apple platforms, for use by non-macOS clients. Oh, how times change!]]></description>
  1438. <content:encoded><![CDATA[<p>Yeah, that's cool. The only Hackintosh you'd want to run nowadays is a VM, anyway. And, God willing, the fine folks at VMware and the QEMU/KVM projects continue to support macOS guests. At this stage my Intel Mac fleet is most useful for running non-macOS, and as Nathan rightly says, it's just very hard to justify that on an ongoing basis; likewise, macOS as a platform, except for portable computers, that run non-macOS VMs, or Mac Minis, that do likewise, as servers with capability to build for Apple platforms, for use by non-macOS clients. Oh, how times change!</p>
  1439. ]]></content:encoded>
  1440. </item>
  1441. <item>
  1442. <title>
  1443. Comment on Hackintosh Is Almost Dead by Nathan </title>
  1444. <link>https://mjtsai.com/blog/2024/04/22/hackintosh-is-almost-dead/#comment-4075498</link>
  1445.  
  1446. <dc:creator><![CDATA[Nathan]]></dc:creator>
  1447. <pubDate>Tue, 23 Apr 2024 05:28:45 +0000</pubDate>
  1448. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42896#comment-4075498</guid>
  1449.  
  1450. <description><![CDATA[Okay, showing my age here, but when I ran Hackintoshes they definitely had Broadcom WiFi/Bluetooth cards because they worked really well with MacOS. This was so long ago, the newest version of Mac OS was probably 10.7 Lion, maybe Mountain Lion.
  1451.  
  1452. I mean, we kind of knew the writing was on the wall when Apple announced the ARM transition. Either way, I have no desire to run MacOS on &quot;whitebox&quot; PCs anymore because the software itself is no longer compelling (our esteemed host&#039;s sofware and similar indie stuff accepted, I mean the platform itself). I also lost interest in running non Apple OSes on Apple hardware too. While I have an old MacBook in service running Arch Linux, I no longer bother shopping Mac hardware, even used models to run Linux, Windows, or anything else. Not worth the hassle, when there are so many other devices that will run these OSes and all are generally easier to repair and more open for tinkering.
  1453.  
  1454. Still, a sad day. Going back further I miss running OS X on older Macs with XPostFacto, that was a fun adventure too.]]></description>
  1455. <content:encoded><![CDATA[<p>Okay, showing my age here, but when I ran Hackintoshes they definitely had Broadcom WiFi/Bluetooth cards because they worked really well with MacOS. This was so long ago, the newest version of Mac OS was probably 10.7 Lion, maybe Mountain Lion.</p>
  1456. <p>I mean, we kind of knew the writing was on the wall when Apple announced the ARM transition. Either way, I have no desire to run MacOS on "whitebox" PCs anymore because the software itself is no longer compelling (our esteemed host's sofware and similar indie stuff accepted, I mean the platform itself). I also lost interest in running non Apple OSes on Apple hardware too. While I have an old MacBook in service running Arch Linux, I no longer bother shopping Mac hardware, even used models to run Linux, Windows, or anything else. Not worth the hassle, when there are so many other devices that will run these OSes and all are generally easier to repair and more open for tinkering.</p>
  1457. <p>Still, a sad day. Going back further I miss running OS X on older Macs with XPostFacto, that was a fun adventure too.</p>
  1458. ]]></content:encoded>
  1459. </item>
  1460. <item>
  1461. <title>
  1462. Comment on Apple Maps in Tokyo by Ben G </title>
  1463. <link>https://mjtsai.com/blog/2024/04/22/apple-maps-in-tokyo/#comment-4075461</link>
  1464.  
  1465. <dc:creator><![CDATA[Ben G]]></dc:creator>
  1466. <pubDate>Tue, 23 Apr 2024 03:08:27 +0000</pubDate>
  1467. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42898#comment-4075461</guid>
  1468.  
  1469. <description><![CDATA[Having lived in Japan, this guy&#039;s complaints have little merit. Sure, Apple Maps sucks and so does a bunch of other stuff they make, but most of what this guy describes is due to some sort of cultural elitism.
  1470.  
  1471. No reviews in English? Who cares! Japanese people rarely leave reviews anyway. Even if you could read them, they&#039;re worthless. Why is he looking at reviews when he could just walk by some restaurants and see if they look appealing? It literally takes less than 5 minutes to find a good restaurant in Tokyo or Osaka -- they&#039;re everywhere. Japan is not the US where a large fraction of restaurants are terrible. Even the places that look drab and crusty are usually amazing.
  1472.  
  1473. Complaining that transit directions and walking directions don&#039;t work? Jesus, all the transit stops have English signage. Japanese transit has the best wayfinding of anywhere I&#039;ve ever been -- there are even compass roses embedded into the sidewalk at most subway entrances, as well as throughout many of the stations. All you have to do is look at the map ahead of time, remember to exit at Exit 4, then head west when you get to street level, walk 3 blocks, then turn right for 1 block, and you&#039;re at your destination. It&#039;s not that hard.
  1474.  
  1475. And whining about crowds? That&#039;s like complaining about being stuck in traffic. You ARE the crowd.
  1476.  
  1477. I thought this couldn&#039;t get worse, but Uber in Japan? When there are taxis driven by professional drivers EVERYWHERE. I can&#039;t even.
  1478.  
  1479. This guy sounds like an entitled ass who doesn&#039;t know a single thing about the country that he&#039;s visiting, and wants to look at his phone for every possible scenario instead of attempting to interact with a Japanese person. Pathetic.]]></description>
  1480. <content:encoded><![CDATA[<p>Having lived in Japan, this guy's complaints have little merit. Sure, Apple Maps sucks and so does a bunch of other stuff they make, but most of what this guy describes is due to some sort of cultural elitism.</p>
  1481. <p>No reviews in English? Who cares! Japanese people rarely leave reviews anyway. Even if you could read them, they're worthless. Why is he looking at reviews when he could just walk by some restaurants and see if they look appealing? It literally takes less than 5 minutes to find a good restaurant in Tokyo or Osaka -- they're everywhere. Japan is not the US where a large fraction of restaurants are terrible. Even the places that look drab and crusty are usually amazing.</p>
  1482. <p>Complaining that transit directions and walking directions don't work? Jesus, all the transit stops have English signage. Japanese transit has the best wayfinding of anywhere I've ever been -- there are even compass roses embedded into the sidewalk at most subway entrances, as well as throughout many of the stations. All you have to do is look at the map ahead of time, remember to exit at Exit 4, then head west when you get to street level, walk 3 blocks, then turn right for 1 block, and you're at your destination. It's not that hard.</p>
  1483. <p>And whining about crowds? That's like complaining about being stuck in traffic. You ARE the crowd.</p>
  1484. <p>I thought this couldn't get worse, but Uber in Japan? When there are taxis driven by professional drivers EVERYWHERE. I can't even.</p>
  1485. <p>This guy sounds like an entitled ass who doesn't know a single thing about the country that he's visiting, and wants to look at his phone for every possible scenario instead of attempting to interact with a Japanese person. Pathetic.</p>
  1486. ]]></content:encoded>
  1487. </item>
  1488. <item>
  1489. <title>
  1490. Comment on Apple Maps in Tokyo by Charles </title>
  1491. <link>https://mjtsai.com/blog/2024/04/22/apple-maps-in-tokyo/#comment-4075460</link>
  1492.  
  1493. <dc:creator><![CDATA[Charles]]></dc:creator>
  1494. <pubDate>Tue, 23 Apr 2024 03:05:43 +0000</pubDate>
  1495. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42898#comment-4075460</guid>
  1496.  
  1497. <description><![CDATA[Oh Buddha, save me from another &quot;Gaijin Problems in Japan&quot; story.]]></description>
  1498. <content:encoded><![CDATA[<p>Oh Buddha, save me from another "Gaijin Problems in Japan" story.</p>
  1499. ]]></content:encoded>
  1500. </item>
  1501. <item>
  1502. <title>
  1503. Comment on It&#8217;s Time for a New AirPort by Nathan </title>
  1504. <link>https://mjtsai.com/blog/2024/04/17/its-time-for-a-new-airport/#comment-4075459</link>
  1505.  
  1506. <dc:creator><![CDATA[Nathan]]></dc:creator>
  1507. <pubDate>Tue, 23 Apr 2024 03:00:08 +0000</pubDate>
  1508. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42875#comment-4075459</guid>
  1509.  
  1510. <description><![CDATA[@Michael Tsai
  1511. 1 Mbps down? Yikes! Is this a carrier problem? Or have you tried all the main carriers and same issue? Is this 5G?
  1512.  
  1513. As far as paying for data, I mean, when $30/month gets you 40GB (Mint Mobile) or in my case it&#039;s unlimited for $25 per line family plan situation (T-Mobile legacy plan), I&#039;m going to put the data to use. If T-Mobile allowed a 2nd home Internet line (not sure if they do or don&#039;t honestly), I might even switch my Xfinity home service over too (I have one TMHI line for my mom&#039;s place already on the family plan). It&#039;s acceptably fast, like 300 Mbps or so, for a low-ish price, with no installation. Battling the shitty gateways they provide is the biggest issue, so locked down and so limited that I actually had to find a 3rd party app that gave you access to wild and crazy features like disabling the WiFi, changing the WiFi channel, and such.]]></description>
  1514. <content:encoded><![CDATA[<p>@Michael Tsai<br />
  1515. 1 Mbps down? Yikes! Is this a carrier problem? Or have you tried all the main carriers and same issue? Is this 5G?</p>
  1516. <p>As far as paying for data, I mean, when $30/month gets you 40GB (Mint Mobile) or in my case it's unlimited for $25 per line family plan situation (T-Mobile legacy plan), I'm going to put the data to use. If T-Mobile allowed a 2nd home Internet line (not sure if they do or don't honestly), I might even switch my Xfinity home service over too (I have one TMHI line for my mom's place already on the family plan). It's acceptably fast, like 300 Mbps or so, for a low-ish price, with no installation. Battling the shitty gateways they provide is the biggest issue, so locked down and so limited that I actually had to find a 3rd party app that gave you access to wild and crazy features like disabling the WiFi, changing the WiFi channel, and such.</p>
  1517. ]]></content:encoded>
  1518. </item>
  1519. <item>
  1520. <title>
  1521. Comment on Outlook Syncing With Microsoft Cloud by MR </title>
  1522. <link>https://mjtsai.com/blog/2023/03/02/outlook-syncing-with-microsoft-cloud/#comment-4075452</link>
  1523.  
  1524. <dc:creator><![CDATA[MR]]></dc:creator>
  1525. <pubDate>Tue, 23 Apr 2024 02:36:00 +0000</pubDate>
  1526. <guid isPermaLink="false">https://mjtsai.com/blog/?p=38664#comment-4075452</guid>
  1527.  
  1528. <description><![CDATA[Regardless of who invented the practice, Microsoft has taken it far beyond anything in the current iteration of their software. Outlook does not present any option to opt out of syncing with Microsoft cloud (on Windows 11 Pro).]]></description>
  1529. <content:encoded><![CDATA[<p>Regardless of who invented the practice, Microsoft has taken it far beyond anything in the current iteration of their software. Outlook does not present any option to opt out of syncing with Microsoft cloud (on Windows 11 Pro).</p>
  1530. ]]></content:encoded>
  1531. </item>
  1532. <item>
  1533. <title>
  1534. Comment on macOS 14 Sonoma vs. exFAT by Nathan </title>
  1535. <link>https://mjtsai.com/blog/2024/04/17/macos-14-sonoma-vs-exfat/#comment-4075450</link>
  1536.  
  1537. <dc:creator><![CDATA[Nathan]]></dc:creator>
  1538. <pubDate>Tue, 23 Apr 2024 02:25:18 +0000</pubDate>
  1539. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42873#comment-4075450</guid>
  1540.  
  1541. <description><![CDATA[@Michael Tsai
  1542. Doesn&#039;t automount and manual mount sometimes fails too? Does it make a difference with type of drive? Or enclosure&#039;s chipset? Not sure how many external drives you have on hand to test of course. But this is fascinating. Seems like a basic function of the OS is not working.]]></description>
  1543. <content:encoded><![CDATA[<p>@Michael Tsai<br />
  1544. Doesn't automount and manual mount sometimes fails too? Does it make a difference with type of drive? Or enclosure's chipset? Not sure how many external drives you have on hand to test of course. But this is fascinating. Seems like a basic function of the OS is not working.</p>
  1545. ]]></content:encoded>
  1546. </item>
  1547. <item>
  1548. <title>
  1549. Comment on Hackintosh Is Almost Dead by Jon H </title>
  1550. <link>https://mjtsai.com/blog/2024/04/22/hackintosh-is-almost-dead/#comment-4075407</link>
  1551.  
  1552. <dc:creator><![CDATA[Jon H]]></dc:creator>
  1553. <pubDate>Tue, 23 Apr 2024 00:10:05 +0000</pubDate>
  1554. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42896#comment-4075407</guid>
  1555.  
  1556. <description><![CDATA[My Hackintosh never had wifi or card-based bluetooth. I used a USB bluetooth dongle thing.
  1557.  
  1558. Messages and FaceTime worked for me with that configuration. Don&#039;t know if that changed with Sonoma.]]></description>
  1559. <content:encoded><![CDATA[<p>My Hackintosh never had wifi or card-based bluetooth. I used a USB bluetooth dongle thing.</p>
  1560. <p>Messages and FaceTime worked for me with that configuration. Don't know if that changed with Sonoma.</p>
  1561. ]]></content:encoded>
  1562. </item>
  1563. <item>
  1564. <title>
  1565. Comment on Apple Maps in Tokyo by Michael </title>
  1566. <link>https://mjtsai.com/blog/2024/04/22/apple-maps-in-tokyo/#comment-4075367</link>
  1567.  
  1568. <dc:creator><![CDATA[Michael]]></dc:creator>
  1569. <pubDate>Mon, 22 Apr 2024 22:44:45 +0000</pubDate>
  1570. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42898#comment-4075367</guid>
  1571.  
  1572. <description><![CDATA[I&#039;m not sure I agree with the suggestion that showing local data is bad as a tourist.
  1573.  
  1574. I recently spent a week vacationing in Japan, and it&#039;s fairly well-known that that locals using a site like Tabelog review very differently than Google Reviews. I found the ratings and links very helpful. Using Tabelog on its own is a little tricky, since you need to have your search in Japanese as well. But getting in via Apple Maps was actually pretty helpful.
  1575.  
  1576. But, look, I&#039;m the guy that has two maps apps on my home screen and have since Apple Maps was released. They each have strengths and weaknesses and I use both interchangeably. When traveling I do preference Google Maps, but that&#039;s largely because the collaborative lists are much more useful than Apple Maps&#039; Guides which don&#039;t support multiple editors. (I also find, I do prefer desktop Google Maps over the Maps app, but that&#039;s likely habit..)
  1577.  
  1578. Apple Maps transit directions do now include car boarding recommendations for Japan which is great. Admittedly, that&#039;s one of the fewer bits of UI where I actually vastly prefer Google Maps.
  1579.  
  1580. Both apps are great and yet infuriating at times.]]></description>
  1581. <content:encoded><![CDATA[<p>I'm not sure I agree with the suggestion that showing local data is bad as a tourist. </p>
  1582. <p>I recently spent a week vacationing in Japan, and it's fairly well-known that that locals using a site like Tabelog review very differently than Google Reviews. I found the ratings and links very helpful. Using Tabelog on its own is a little tricky, since you need to have your search in Japanese as well. But getting in via Apple Maps was actually pretty helpful. </p>
  1583. <p>But, look, I'm the guy that has two maps apps on my home screen and have since Apple Maps was released. They each have strengths and weaknesses and I use both interchangeably. When traveling I do preference Google Maps, but that's largely because the collaborative lists are much more useful than Apple Maps' Guides which don't support multiple editors. (I also find, I do prefer desktop Google Maps over the Maps app, but that's likely habit..) </p>
  1584. <p>Apple Maps transit directions do now include car boarding recommendations for Japan which is great. Admittedly, that's one of the fewer bits of UI where I actually vastly prefer Google Maps. </p>
  1585. <p>Both apps are great and yet infuriating at times.</p>
  1586. ]]></content:encoded>
  1587. </item>
  1588. <item>
  1589. <title>
  1590. Comment on It&#8217;s Time for a New AirPort by Nathan </title>
  1591. <link>https://mjtsai.com/blog/2024/04/17/its-time-for-a-new-airport/#comment-4075364</link>
  1592.  
  1593. <dc:creator><![CDATA[Nathan]]></dc:creator>
  1594. <pubDate>Mon, 22 Apr 2024 22:41:58 +0000</pubDate>
  1595. <guid isPermaLink="false">https://mjtsai.com/blog/?p=42875#comment-4075364</guid>
  1596.  
  1597. <description><![CDATA[Airport related question:
  1598. Anyone here have a last model Airport Express? The one that sits flat, has simultaneous dual band 802.11n, and a dedicated WAN port? If so, does it have ProxySTA mode?
  1599.  
  1600. As noted by Dan Frakes in his review of the plugin to the wall 802.11n Airport Express model:
  1601. &quot;To activate ProxySTA, you must set up the Express to join a wireless network and then enable the Allow Ethernet Clients setting; both settings are located in the Wireless tab of AirPort Utility.&quot;
  1602.  
  1603. I had that model and it worked very well in this mode, but I never could figure out if the newer model Express could do the same thing. It&#039;s kind of been a curiosity to me this last decade since the model was released. I never knew anyone who owned one of the upgraded models to get confirmation.]]></description>
  1604. <content:encoded><![CDATA[<p>Airport related question:<br />
  1605. Anyone here have a last model Airport Express? The one that sits flat, has simultaneous dual band 802.11n, and a dedicated WAN port? If so, does it have ProxySTA mode?</p>
  1606. <p>As noted by Dan Frakes in his review of the plugin to the wall 802.11n Airport Express model:<br />
  1607. "To activate ProxySTA, you must set up the Express to join a wireless network and then enable the Allow Ethernet Clients setting; both settings are located in the Wireless tab of AirPort Utility."</p>
  1608. <p>I had that model and it worked very well in this mode, but I never could figure out if the newer model Express could do the same thing. It's kind of been a curiosity to me this last decade since the model was released. I never knew anyone who owned one of the upgraded models to get confirmation.</p>
  1609. ]]></content:encoded>
  1610. </item>
  1611. </channel>
  1612. </rss>
  1613.  

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

  1. Download the "valid RSS" banner.

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

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

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

http://www.feedvalidator.org/check.cgi?url=http%3A//mjtsai.com/blog/comments/feed/

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