All valid points, Lugz.
Perhaps I never mastered the previous version’s intended embedding method, but the new version is simpler than what I used to do - attach a thumbnail, then follow its link, copy the address, and then embed it - way more trouble than just choosing and saving, especially with multiple photos.
Also, the “you” in my previous post was meant for anyone dissatisfied with fuzzy, weirdly-large thumbnails, not specifically Lugz.
FINALLY, as Outlaw has said “YMMV.” The procedures that I follow on my iPhone are not going to be identical to what someone on an IBM-compatible desktop does with a two-button wheel mouse. Nor are the results going to display identically.
I’m quite content with the text size displayed on my 5” screen, but if I was on a 32” monitor and could see only the same 1-post-at-a-time, I’d be furious.
What follows “finally?” LOL…
re-re-reading Lugz’s post, I still agree with what he’s said, although it doesn’t alter my preference to embed photos on the new platform. The main drawback I’ve experienced, is that it restricts the flow of language to a linear narrative (as Lugz said). You either indicate and describe the image prior to embedding it, or afterward. Recursive, layered comparisons are awkward with embedded images, whereas they are more natural with separate, viewer-optional thumbnails (thanks to html). Best compromise to me for complex discussion is clustering them at the bottom of the post, like what gearhead just did. A personal preference on my device, because on my screen, the blurry, pixelated thumbnails appear as large as the crisp, embedded images, taking up the same real estate without supplying the useful detail.