That's sometimes the case, but not here. If you always connect to lfgss over https, that issue never arises because all images are cached by sslcache.se, so any local cache is out of the equation and it's immediately obvious if the host is using the referrer header (or a cookie, for example on sites where you have to be logged in to see content) to decide whether to send the image. The more common issue is short lived img urls, which make everything look fine for the minute (or hour, or day) but the url is no longer valid when everybody else arrives to look at the thread. For that reason, I usually attach images as well, unless I'm actually hosting the embedded image on my own server and know that it will be there and accessible as long as I'm around.
short winded version:
"it's obvious."