…I have been in touch with Flickr support. I am trying one of their suggestions below: Two photographs should appear, but the first (original size at 1176 x 1176) might not if one of their theories is correct.
And...
This time they both showed up immediately after I posted them.
- - -
Also...
It is a photograph, so I suppose I should say something about it. :-)
I live close enough to the Big Sur Coast that I can drive down and back for photography... and be home by mid-afternoon. This time I stopped at Point Lobos as soon as they opened the gate and went in as the fog was starting to clear. I spent a few hours walking slowly and looking for photographs, some of familiar views (like this one) and some that I had not noticed before... even though I've been photographing there regularly for decades.
i've investigated this because this has been happening on an off and it was worse around the time this thread started.
as pointed out here it's due to HTTP 429 (You can see the requests to flickr images under Network in your browser...easily accessible by right-click on mouse -> Inspect...for Safari you need to enable "Developer Mode" or something).
When you embed the BB code it's basically hot-linking the image--i.e., image embeds the image but flickr is serving the image. Flickr's web server (any web server for that matter) will know the embedding server (HTTP HOST sent via HTTP headers) which in this case fredmiranda.com not matching its own (flickr.com) and by looking at the client IP (your machine usually via X-Forwarded-For header, either through VPN or your gateway or whatever) that becomes a unique key to start throttling the requests and that throttling results to HTTP 429 response. HTTP 429 response is not permanently disabling the image serving but as you have noticed it's intermittent, you get a bit of reprieve when the your IP reported to the flickr server changes as it thinks it's a different machine.
you don't see this issue when viewing your pictures at flickr, because there server is the same as HOST (flickr.com) so they will not throttle.
this is a somewhat watered down explanation. I'm sure there may be other tricks on flickr to throttle requests since serving the image from their servers is _their_ cost, not fredmiranda.com's.
