Earlier quoted context omitted.
And you wrote/maintain the app that can open, process, and serve that data. And you can keep up with storage technologies as they age and become obsolete. And you can run a perfect IDS/IPS/DLP/firewall secure environment with your own custom self-hosted cloud. And your local cloud has four-nines high-availability clustering, power, and network peering. glhf.
You're over-engineering what is otherwise a straightforward solution for this particular instance. Instagram allows you to save stories to your mobile device, so... 1.) Download your story to your mobile device. Congratulations, you now have your own copy of your story that is yours and not under control of Instagram. You could stop here if you want, or you could... 2.) Copy the file to another device you might keep…
I don't know what IG "archiving" entails, does it remove stories from public view or something?
The main point of using an online service like IG is for serving and sharing your content. Not keeping it to yourself. IG stores and serves public content in a secure fashion, with very high availability and unparalelled reachability.
You've replied to my "over-engineering" with single-user hoarding solutions. Do you want to serve the content or not?
IG posts involve more than a JPEG. "Stories" are slideshows made of multiple items. There is metadata, tagging, other users: context. If you want to download a couple of JPEGs and lose all that context, you're not using IG anymore, you're hoarding.