Title text:
Turning in other directions can be accomplished by using a magnetized centerboard and ocean currents, since a current flowing through a magnetic field induces a Laplace force.
Transcript:
Transcript will show once it’s been added to explainxkcd.com
Source: https://xkcd.com/3090/
I actually like it better this way because the full comic can be viewed and zoomed in on in app (Voyager in my case). I’ve seen these posted with the source page as the post link and I can’t click on the image to zoom in without being pulled out of app with a wait for the web page to load. Also, when entering the post to see the comments, the thumbnail is so small when the source page is linked, making the comic unreadable. With an image alone, the full comic is viewable beside the comments. Is it different for you?
The thing is, with xkcd, the image is not the full comic. Part of the comic is the hover text, which you don’t get with the image alone.
The way things are now, I click the title and it takes me to a bare image, so I then have to go back, and then read through the post body to find the link to the whole comic, and then click that. It’s a hassle.
(And since you mentioned viewing comments alongside the image, you should be aware that Lemmy’s default interface shows only a thumbnail fragment of the image on the same page as the comic. I guess you might be using a mobile app.)
The bot adds the alt text to the post, so no need to head to the site to see the entire comic.
Are you the bot author? If so have you considered using Lemmys alt text field directly? This would display the text with the image is some clients like voyager. It would also federate to Mastodon (post body doesn’t federate). You could also keep the text in the post body and do it both places :)
I am not, that appears to be @deebster@programming.dev
That splits the comic between two separate screens, and requires multiple steps (and page loads) to read it.
It’s not as good as linking to the whole comic, intact, in one place.
As has been pointed out though on non-web clients it’s much more disruptive to link to the webpage instead of how the bot works now. I’m not sure what the split is between web and mobile users but I’d hazard a guess there’s appreciably more mobile client users.
I’m also not sure why it would require more loads on web, if you open a post (as you have to do regardless) does it not show the image with text below it anyways?
I guess this is going to come down to desktop vs mobile preference. On mobile this shows everything on one page with no additional loading. Alternatively, using the source page requires multiple steps and page loads for mobile users, who may also need to amend the link to see the hover text.
In that case, perhaps linking to the mobile site would make sense, since it ought to work for both mobile and desktop:
https://m.xkcd.com/3090/
deleted by creator
If you are on the standard lemmy ui:
Still not equivalent, since it still requires multiple steps, and doesn’t work with privacy settings that forbid off-site images.
Ah, thanks for clarifying. I never knew about the hover text. I just viewed the source page on my desktop browser and now I see it. However, is this text even viewable on mobile, when you don’t have a cursor to hover?
E: Now that I’ve read the hover text on my desktop, I’ve noticed that it’s the same as the text added to the post by the bot. I really like this implementation with the image linked alone. When the post is viewed on mobile, all text is viewable and the full comic is shown legibly.
The mobile browsers I’ve used let you long-press the image to see the hover text.
If yours doesn’t, you can always prepend
m.to the domain name, like this: https://m.xkcd.com/3090/Thanks for the tip!