3 ms·

Man I wish they would explain what UTM SE is in either the article or in any of the linked (other) articles...

derefr 2y ago
Pedantry: 1. if you click "UTM SE" in this article, you get taken to https://taoofmac.com/space/links/2024/07/14/0819 https://taoofmac.com/space/links/2024/07/14/0819; 2. and this page in turn is apparently of an unusual "commentary on a link" CMS type — where it seems that clicking the little arrow wingding beside the title — or clicking the thumbnail (which is a thumbnail of the page the comment is "about") — takes you to the page that the comment is "about"; 3. where that page (https://www.theverge.com/2024/7/13/24198015/apple-utm-se-pc-os-emulator-for-ios https://www.theverge.com/2024/7/13/24198015/apple-utm-se-pc-...) then explains what UTM SE is, across its header and subheader: > After initially rejecting it, Apple has approved the first PC emulator for iOS > UTM SE can ‘run classic software and old-school games’ for Windows, Mac OS 9, and Linux on your iPhone. --- This is admittedly confusing and indirect — but that's mostly due to this website's publishing system's weird reading-UX choices, not so much due to the author's editorial choices. (Unless this publishing system is created by the author, in which case...) A few UX recommendations to the site's designer: 1. fix the rendering for your "Link" resources! Facebook and Twitter have forced the rest of the web into expecting that this kind of resource will be rendered as what they call a "link preview" — using the OpenGraph metadata (og:title and og:description) of the target page. As such, only rendering the page's scraped <title> might produce bad results, as nobody's expecting you to do that, and so hasn't optimized their pages' out-of-context comprehensibility for that. They've optimized for people rendering og:title + og:description — so if you want your own "link previews" to be comprehensible, then that's what you've gotta do too. 2. You probably want to give "supplementary" Posts like this one, some CMS metadata that points to a previous Post or Link as the "prerequisite reading." If a Post has prerequisite reading, then your CMS should render the Post's full unfolded body view with an embedded summary of the previous resource at the beginning. (Where in this case, what I'd expect is a blockquote of the Link resource — in turn including the link preview!)
- dark-star 2y ago
  That's exactly what I did, which confused me a lot: * See an article about something called "UTM SE" * See a linkified "UTM SE" in the first paragraph, thinking it would take me to a homepage or GitHub project or something * But instead it takes me to another article on the same site that talks about JIT and apt-get update and how Apple disallows that. Not very helpful * Further down on the first page is a link to "the 'real' UTM", but guess what, it also goes to some other article on the same blog that doesn't explain anything I realize that most of this has been fixed now, but seriously, to me that just looked like some sort of SEO by using dozens of intra-site links, or something.
rcarmo 2y ago
That's fixed. I realize people outside the Mac/iOS sphere might lack context, so I added it in.

Pedantry: 1. if you click "UTM SE" in this article, you get taken to https://taoofmac.com/space/links/2024/07/14/0819 https://taoofmac.com/space/links/2024/07/14/0819; 2. and this page in turn is apparently of an unusual "commentary on a link" CMS type — where it seems that clicking the little arrow wingding beside the title — or clicking the thumbnail (which is a thumbnail of the page the comment is "about") — takes you to the page that the comment is "about"; 3. where that page (https://www.theverge.com/2024/7/13/24198015/apple-utm-se-pc-os-emulator-for-ios https://www.theverge.com/2024/7/13/24198015/apple-utm-se-pc-...) then explains what UTM SE is, across its header and subheader: > After initially rejecting it, Apple has approved the first PC emulator for iOS > UTM SE can ‘run classic software and old-school games’ for Windows, Mac OS 9, and Linux on your iPhone. --- This is admittedly confusing and indirect — but that's mostly due to this website's publishing system's weird reading-UX choices, not so much due to the author's editorial choices. (Unless this publishing system is created by the author, in which case...) A few UX recommendations to the site's designer: 1. fix the rendering for your "Link" resources! Facebook and Twitter have forced the rest of the web into expecting that this kind of resource will be rendered as what they call a "link preview" — using the OpenGraph metadata (og:title and og:description) of the target page. As such, only rendering the page's scraped <title> might produce bad results, as nobody's expecting you to do that, and so hasn't optimized their pages' out-of-context comprehensibility for that. They've optimized for people rendering og:title + og:description — so if you want your own "link previews" to be comprehensible, then that's what you've gotta do too. 2. You probably want to give "supplementary" Posts like this one, some CMS metadata that points to a previous Post or Link as the "prerequisite reading." If a Post has prerequisite reading, then your CMS should render the Post's full unfolded body view with an embedded summary of the previous resource at the beginning. (Where in this case, what I'd expect is a blockquote of the Link resource — in turn including the link preview!)

dark-star 2y ago
That's exactly what I did, which confused me a lot: * See an article about something called "UTM SE" * See a linkified "UTM SE" in the first paragraph, thinking it would take me to a homepage or GitHub project or something * But instead it takes me to another article on the same site that talks about JIT and apt-get update and how Apple disallows that. Not very helpful * Further down on the first page is a link to "the 'real' UTM", but guess what, it also goes to some other article on the same blog that doesn't explain anything I realize that most of this has been fixed now, but seriously, to me that just looked like some sort of SEO by using dozens of intra-site links, or something.

rcarmo 2y ago

That's fixed. I realize people outside the Mac/iOS sphere might lack context, so I added it in.