← all posts site ↗

reading the comments on your saved posts

saved an unreleased track on instagram and the post said nothing about a release date. the comments did. that is the whole reason comments belong with the reference, and the vault was not saving them. so it learned to, and the old saves needed a backfill.

two thousand three hundred items went through the sweep. almost nineteen hundred came back with a usable comment block. then the run stalled about a thousand requests into the hour and the first suspect was a rate limit, but the real cause was dumber. image only posts make the extractor raise no formats found before it prints anything, so that whole cluster came back empty. one flag later, an image post that previously gave nothing returned eleven of thirteen comments. which is exactly the unreleased track case. the song posts are image posts.

backfill resumed, a thousand or so comments landed, then a genuine block hit. the anonymous endpoint started redirecting to the login page. roughly one request per second for an hour trips it, and the honest fix is waiting it out. the last few hundred items run on a schedule with a longer gap and fewer workers. a failed fetch leaves the saved item untouched, so nothing corrupts while the limit clears.

the vault keeps comments now. the next time an image post gets saved, its comments come with it, and the next unreleased track gives up its release date.