This is part of the move to Amazon Open Data. Images that are Creative Commons licensed are now being hosted on a different server and we finally started deleting the duplicates on our old server. See https://forum.inaturalist.org/t/representative-pictures-not-showing-on-all-species-pages/25401/7
You’ll have to change the domain for each img_src URL from https://static.inaturalist.org to http://inaturalist-open-data.s3.amazonaws.com eg https://static.inaturalist.org/photos/82822264/original.jpeg should be http://inaturalist-open-data.s3.amazonaws.com/photos/82822264/original.jpeg That should work, as long as the photo is still attached to an observation or other content.
As for the large blocks of text, that probably has to do with our switch to markdown, which happened about a year ago.
We’ve never officially supported using iNat as an image hosting service for stuff like journal posts, so if a user uploaded an image with an observation then removing them from the observation just so they could use the image in a journal post or comment (I’m not saying you did this, @kaipatiki_naturewatc, just saying this for anyone who might have a similar issue), that photo could be gone. We recommend using an actual image hosting service if you want a place to host images for things like this.
The text formatting is due to the change to markdown support, which happened over a year ago. You probably want to start playing around with the lists you have in your posts, some are not showing up as sublists because they’re not indented. Here’s a guide to lists in markdown: https://www.markdownguide.org/basic-syntax/#lists-1 For example, try indenting your list items two spaces. Here’s what that looks like on the edit page:
I should look something like this when published:
