Instagram Gallery Deprecated

My Instagram photos, copied out before their links expired. Fifty-two posts.

Deprecated. Its gallery page was removed because a mirror of personal Instagram posts did not belong on a site about software the system builds and runs. The exporter and its tests stay as they were.The photo page is gone. A copy of personal Instagram posts did not fit a site about software. The code stays as it is.

Architecture diagram: Instagram Gallery only when the statechanged one page at a time posts, captions and links the links it stored, alreadyexpiring the picture bytes, onceeach no expiring link, ever Daily access renewal Stored account access Telegram alert Read client Instagram Graph API Media edge walk Local media cache Image downloader Instagram image CDN Locally stored image files Gallery snapshot export Local gallery snapshot Retired render step One-command import
Posts are still walked into a local cache and the pictures still copied out of Instagram's expiring links; since the gallery was retired, the copies stay local and nothing builds a page from them any more.The posts and pictures still get copied here first. There's just no page left for them to end up on, since the gallery was taken off the site.

The Photos Were Served From Here

A snapshot built from what the API returns goes stale by evening, so each image is still downloaded once and identified by its actual bytes. It used to be committed with the site's content; since the retirement it lands in local, gitignored storage instead, rebuildable from a fresh import rather than kept forever.

Instagram's picture links stop working after a few hours, so a page built on them would break overnight. Each picture is still downloaded once and checked to be a real image. It used to stay on the site for good; now it's saved locally instead, and rebuilt from scratch each time the tool runs.

A Bad Read Never Looks Like Deleted Posts

Only a walk Instagram declared finished may conclude a post was removed; a capped or interrupted one has not seen the older end of the account. A finished walk returning nothing over a full cache is refused rather than believed. That costs one retry, and believing it would cost the whole cache.

The tool only decides a post was deleted after reading the whole account from start to finish without any errors. If that full read comes back empty when there should be photos, it refuses to believe it rather than emptying the saved copy. That costs one retry instead of losing everything.

One Command, In The One Order That Works

Fetching stores links that expire and downloading spends them, so a run against a week-old cache still finds every link dead. The fourth stage used to rebuild the site's page; it now reports that there is nothing to render into. Bounded runs, rate limits and held-back posts still resume next time rather than stopping the run.

The steps still have to happen together and in order, or they'd break in ways that look like nothing went wrong. So it's still one command. The last step used to update the live page; now it just says there's no page left to update. Anything it can't finish gets picked up next time.

The Connection Renews Itself, Early

Ten days of runway means ten consecutive attempts before anything is lost, so the schedule is the retry. A replacement is verified, and checked to belong to the same account, before it is stored. Still unproven: it has not yet carried the access across a full sixty-day expiry unattended.

It renews ten days early rather than on the last day, so there are ten chances instead of one. A new connection is tested before it replaces the old one. Still untested: renewing itself across a full two-month cycle with nobody watching.