ReSo7200/InstaEclipse

If you want Instagram to stop broadcasting that you read a DM, watched a story, or are typing, this module puts those switches inside the app instead of asking you to change your behavior. It is worth a look if you already run an Xposed-style framework; it is not a drop-in tweak for a stock phone.

The problem

A privacy-conscious Instagram user wants to read messages and stories without leaving a trail: no read receipts, no viewer entries, no typing dots, no "last seen" movement. Instagram's own settings don't expose any of this, so the usual workaround is behavioral — delay opening chats, avoid stories, or use a second account. InstaEclipse changes the step that matters: the app's network and UI calls are intercepted at runtime, so a read or view can happen locally while the server-facing signal is suppressed. The result is normal browsing with the footprints you pick turned off, plus a set of adjacent conveniences such as keeping unsent or disappearing messages.

What's different

This is an Xposed module, not a modded Instagram APK. It hooks into the installed Instagram process through Vector on rooted phones or LSPatch on unrooted ones, and its menu lives inside Instagram: long-press the Explore tab. The maintainer says DexKit finds the needed code at runtime, so the module is described as surviving Instagram updates, and the in-app menu reports how many switches actually attached (e.g. "62/62 active"). That feedback loop is the practical advantage over blind patching: when a feature silently fails, you see the count and can check which ones didn't bind.

The trade-off is the framework dependency and the target-app fragility. Hooks point at Instagram internals, and the README concedes that a big Instagram update can knock a feature out until it is patched. There is also a specific interaction to watch: if you use Hide My Applist, the module must stay visible to Instagram, or menu text disappears. Features can additionally be blocked by Instagram's own config, which the Developer Options section can reset.

Who should try it

Good fit: an Android user who already has Vector (root) or is comfortable running LSPatch to patch and sideload Instagram, and who mainly wants Ghost Mode-style privacy plus message retention. The no-root LSPatch path means you don't need a rooted device, but it does mean installing a patched Instagram build and logging in there.

Poor fit: anyone who wants to keep the Play Store Instagram build and its update flow. The README explicitly recommends the APKMirror build of 451.0.0.20.80 and notes the Play build is not always fully supported, so you are taking on manual version management. If you are unwilling to sideload a patched app or maintain an Xposed framework, the setup cost outweighs the benefit.

Requirements and limitations

You need Android 9 or newer, the right framework (Vector 2.2+ for root, LSPatch 1.0+ without root, or the -L Legacy build for classic Xposed API frameworks such as LSPosed), and the module enabled specifically for Instagram. The README's installation and FAQ sections cover the steps; expect to force-stop and reopen Instagram after changes.

Ongoing upkeep is the real cost. Compatibility is pinned to a tested Instagram version, the Play build is discouraged, and features can break after Instagram updates. Announcements and config resets are handled through the project's Telegram channel, so following it is part of keeping the module working. There is no documented promise that suppressed signals stay suppressed if Instagram changes its behavior.

HotRepo's take

HotRepo's stored coverage is thin: a weekly Java board observation on 2026-10-25 showed +95 stars at #4, with only two recorded dates and no daily-board history. That is a dated snapshot of interest, not evidence of a trend, so persistence cannot yet be judged. Before committing, verify that the release build matches your framework and that the tested Instagram version is the one you can actually install.