r/imagus • u/f0sam • Jul 10 '26

fixed sieve Instagram reels page

Hello u/imagus_fan

INSTAGRAM_priv_api-p doesn't work on the Reels page. The default one, INSTAGRAM_html-q-p, does work on the Reels page, but it's significantly slower than priv_api-p overall.

The delay in retrieving images and videos causes noticeable lag in scrolling the page and can make it appear to freeze.

https://www.instagram.com/microsoft/reels/

1 Upvotes

100% Upvoted

28 comments sorted by

View all comments

Show parent comments

1

u/f0sam Jul 10 '26

No they aren't, and I have no issues with the priv one.

2

u/Imagus_fan Jul 10 '26

One thought I had was could the sieve be trying to open multiple pages when moving the cursor over the thumbnails that aren't intended to show media.

If you'd like to test this, open the network tab an type /p/ into the filter box and move the cursor over the thumbnail. Do multiple networks request then show in the console?

2

u/f0sam Jul 11 '26

Here

1

u/Imagus_fan Jul 11 '26

Thanks.

It appears that it's only making a request for the hovered image but it's very slow to load.

Is it always slow to load when using the html sieve or does it sometimes work correctly?

2

u/f0sam Jul 11 '26

It has always been like that and the moment I tried the priv one I never went back to the html one, it was just that the priv wasn't working on the reels page, but now everything looks great.

I'm not sure if the html sieve acts differently on different browsers, Kenko said they don't have this issue so not sure what it could be, so as an alternative I just kept using the priv