I might be misunderstanding here but if you make a status with a photo, it doesn't attach the literal bytes of the photo but the URL to your local copy of the photo which may, admittedly, by fetched 1000 times by those instances if someone on each of those instances looks at it.
cf https://octodon.social/@pzmyers/110265584018863694 which has the link //assets.octodon.social/media_attachments/files/110/265/581/155/000/717/original/0b24824d56920b79.jpeg and also a preview link of https://assets.octodon.social/media_attachments/files/110/26....
Small example log: https://pastebin.com/raw/jYZ1z8dG
I've seen some cases where there's been 1000+ requests to a site just because a link to it was posted.
But even then, not all of them fetch and cache media on receipt of a status (e.g. mine don't) and they're not fetching them at the same time according to my logs.
You may well still end up serving 1000 copies of the photo (or even more if people aren't caching) but it's 100% not "blast out the photo to 1000 instances when you post" - it's much gentler.
What is the average social media user going to host their Mastodon instance on? I wish it were possible to run mini-servers on something like an Apple TV, goodness knows there’s enough CPU going spare there most of the time. Or that ISPs shipped routers capable of it. But alas most people don’t have sufficiently open hardware just sitting around at home.
A Raspberry Pi?
https://github.com/guysoft/PleromaPi
(Sadly no AkkomaPi yet, it seems.)
> Unzip the image and install it to an SD card
OK, you'll lose some people here but a lot could handle that
> Configure your WiFi by editing pleromapi-wpa-supplicant.txt
Aaand they're gone