Our sandbox build stopped at /tweak.mk, and the test command reported no test target. Use ThreadsPulse if you already sideload iOS apps and want download and feed controls inside Threads; skip it if your daily routine depends on reliable Apple Shortcuts sharing, because the reporter in issue #9 reproduced that failure in a re-signed app even without the tweak.
mumuisdog/ThreadsPulse modifies the iOS Threads app. It isn't the similarly named growth-audit service: threadspulse.app sells profile audits, while the repository describes an iOS tweak. An IPA is an iOS app archive; sideloading means installing it through a route outside the App Store. That distinction matters here because the way you package and sign the app changes which features travel with it.
What people use ThreadsPulse for
Snowflake-2412 used ThreadsPulse to download HDR videos, then supplied examples when the downloads came out in standard quality. Other users tested ad coverage and contributed a translation. These reports are more useful than a feature checklist because they show the task, the installation path and the response.
| Person and task | What happened | Source |
|---|---|---|
| Snowflake-2412 downloaded HDR videos | Reported normal-quality output, tried an update and supplied more failing examples; the maintainer later reported a fix and linked v1.29.4. | HDR discussion, issue #1 |
| Snowflake-2412 injected the tweak and signed a Threads IPA with RyukSign/Esign | Other sharing destinations worked, but Shortcuts did not respond; re-signing without ThreadsPulse reproduced it. | Signing comparison, issue #9 |
| Snowflake-2412 tried the Safari extension for Threads links from Instagram | Got the extension working, then asked about the remaining Open confirmation. | Link-opening follow-up, issue #9 |
| The reporter of issue #2 checked promoted posts in comments | Reported visible ads; the maintainer said current blocking covers the home feed and asked for screenshots and the Threads version. | Comment-view ads, issue #2 |
| The reporter of issue #6 submitted a Korean translation archive | The maintainer requested a pull request adding the language folder and offered to merge it in the next update. | Translation contribution, issue #6 |
The Shortcuts report contains a particularly useful comparison. Snowflake-2412 first said the App Store app worked, then followed the maintainer's request to re-sign the original IPA with the same certificate and tool, leaving ThreadsPulse out. Shortcuts still failed. That gives you a concrete reason to evaluate signing before blaming a download or feed setting.
What you can do with ThreadsPulse
The English README documents photo and video downloads, feed controls and removal of tracking parameters from links. Those features work inside a modified Threads installation, rather than in a separate downloader you paste links into. The README's download controls include saving a post's media or choosing an individual item in full-screen view. Its feed options include disabling autoplay and preserving your place after returning from the background.
For media, the useful distinction is between resolution and HDR, the wider brightness range a compatible video can carry. The current README offers a Highest quality setting and separate Keep HDR or Compatible formats. It also describes a fallback to lower-resolution video if processing fails. Choosing the highest setting is therefore a request with a fallback, rather than a promise that every saved file will match the source. The issue history below explains why that distinction deserves attention.
What happened when we ran it
Our November 21, 2026 sandbox recorded installation success in 0 seconds, a build failure in 0 seconds and a test-command failure in 0 seconds at commit 462d912. The recorded configuration was 3 CPUs, 8 GB RAM and image label lab-cpp:1. That label names the image; actual runtime and operating-system versions require the raw toolchain logs.
| Step | Our recorded result | What the log shows |
|---|---|---|
| Install | Succeeded in 0 seconds | The harness marked the step successful. |
| Build | Failed, exit 2, in 0 seconds | Makefile:15: /tweak.mk: No such file or directory followed by make: *** No rule to make target '/tweak.mk'. Stop. |
| Tests | Failed, exit 66, in 0 seconds | no test target |
The install step returned success. Then make stopped while looking for /tweak.mk; the test step supplied no passing-test result, only the missing-target message. Those are our build and test findings, not an iPhone compatibility result. The scan recorded 67 files, approximately 653 source lines and a 0.9 MB checkout, with two CI workflow files, no Dockerfile and no tests directory. A small checkout doesn't remove the need for the right build tooling: the local-build instructions require Theos, the toolkit the project uses to build its iOS modification. The log alone doesn't identify why the required make include was absent.
A separate attempt to use our container-based hands-on runner stopped at its safety check: none of compose.yaml, compose.yml, docker-compose.yaml or docker-compose.yml existed, and the runner required a Compose file. Docker Compose describes a group of containers; this check cannot exercise an iOS tweak. The run summary's generic statement about deployment conflicts with that failed prerequisite, so it supplies no successful deployment result. The teardown recorded an OK result.
Where people get stuck: signing and the missing Safari extension
Issue #9 ties the reported Shortcuts failure to a re-signed installation and gives a specific workaround for browser links. Universal Links are the iOS mechanism that lets a web link open its corresponding app. In that discussion, mumuisdog says re-signed apps lose Universal Links, then directs the user to the Open in Threads Safari extension.
The package choice comes first. Use the GitHub Actions Build IPA workflow's sideload variant for that extension; injecting the TrollFools dylib yourself leaves it out. Enable Open in Threads in Safari's extension settings and make Safari your default browser. The maintainer says the extension works in Safari, not Chrome. Snowflake-2412's eventual success still included a manual Open confirmation, which the maintainer attributes to iOS itself.
| Symptom | Check or response documented by the project | Result in the discussion |
|---|---|---|
| Share to Shortcuts does nothing | Compare with a re-signed IPA using the same certificate and tool, without ThreadsPulse. | Reporter reproduced the failure; no remedy was recorded. |
| Open in Threads is absent from Safari settings | Check whether you used the sideload IPA rather than manual dylib injection. | Maintainer identified the package containing the extension. |
| Instagram links stay in a browser | Enable the extension and use Safari as default. | Reporter got it working, with an Open prompt. |
| Promoted posts remain in replies | Send a screenshot or recording and the Threads version, as requested in issue #2. | The comment-view issue remained open. |
Before building an IPA, the README asks for a decrypted Threads archive, a direct download link and a signing tool. The project doesn't provide Threads itself. The current documentation separates the sideload variant, which retains extensions, from noplugins for free Apple ID routes, which removes them. Don't choose noplugins and expect the Safari extension to appear later in Settings.
HDR fixes have a version history
The maintainer linked v1.29.4 after Snowflake-2412 reported that some HDR downloads still failed following v1.29.0. In issue #1, the first response asked for a sample post, followed by an announcement that v1.29.0 could download HDR. The user then returned with another failing example.
The exchange didn't end at the first announcement. The maintainer initially questioned whether that example was HDR; Snowflake-2412 supplied a comparison clip and another post. Only after that did mumuisdog report finding and fixing the issue, then link v1.29.4. Read that as a documented maintainer fix following a useful bug report. The question to ask of a downloaded file is whether its actual format and brightness information survived, rather than whether the release title contains HDR.
English docs exist, and maintenance is active
The repository provides an English README and a Traditional Chinese translation, and the current README lists English, Traditional Chinese, Simplified Chinese, Japanese and Korean interface text. It says its language selector changes ThreadsPulse's own text while leaving Threads itself alone. The Korean contribution in issue #6 documents a contributor sending a translation archive and the maintainer asking for a pull request; the current README separately lists Korean support.
GitHub's public metadata records a push on November 21, 2026, and the latest release endpoint identifies v1.31.1 on that date. Its English notes describe clipboard-link fixes during login and typing. Together with the sample reports and replies, that is evidence of ongoing work. It isn't a count of satisfied users. Mid or Real's project page explicitly says it lacks enough comparable adoption data, so its attention signals shouldn't decide whether you trust this app with your account.
Privacy controls don't remove the signing decision
The README warns that modifying third-party applications may lead to account restrictions or suspension. It also calls ThreadsPulse unofficial and unaffiliated with Meta or Apple. Those warnings belong in your installation decision, especially if this is an account you rely on for work.
There is a concrete distribution concern too: the README warns that signed-in GitHub users can download artifacts from a public repository. It recommends keeping the IPA download link in a GitHub Secret and deleting the artifact after retrieving it, or importing the repository privately. Treat the modified app archive as something you must manage, rather than assuming a public fork makes the whole workflow private.
In a Threads post, elina.lin.studio raises concerns about impersonation and misuse of profile images. It asks Meta to investigate and explicitly says it isn't accusing the developer of criminal conduct. Downloading a profile image and copying profile text can concern the person whose material is saved; describing that concern accurately requires keeping the request for investigation separate from a finding of abuse.
ThreadsPulse vs App Store Threads and manual TrollFools injection
The original App Store installation is the stronger choice if preserving the reporter's working Shortcuts workflow matters more to you than extra controls. The meaningful alternative for someone already committed to modification is the packaging route: the GitHub Actions sideload IPA includes a Safari extension that manual TrollFools injection omits, according to the maintainer's instructions in issue #9.
| Choice | Reason to choose it | Tradeoff documented in issue #9 |
|---|---|---|
| Original App Store Threads | Snowflake-2412 reported working sharing to Shortcuts there. | It is the unmodified reference installation in that comparison. |
| ThreadsPulse in the GitHub Actions sideload IPA | Includes Open in Threads for Safari-based link opening. | The link route still requires the Safari Open confirmation. |
| Manual TrollFools dylib injection | Fits an existing manual-injection workflow. | The dylib doesn't include the Safari extension. |
These choices answer different needs. If you mainly want one-tap links from Instagram, replacing the stock app introduces a browser detour. If you mainly want to save media while browsing, the integrated download controls have a clearer benefit. Decide using the action you repeat daily, then choose the package that carries its required components.
What the other reviews get wrong
Mid or Real's captured project page calls the latest release “0 days ago” while also naming v1.31.0 dated November 18 and a November 21 check date. Those statements conflict within that page's own snapshot. The live GitHub release is now v1.31.1, published November 21; that newer release doesn't repair the older page's inconsistent dates.
The launch announcement on X also needs two qualifications. Its broad ad-blocking description should be read alongside the maintainer's narrower home-feed statement in issue #2. It doesn't promise clean comment threads. And the launch calls ThreadsPulse open source, while Mid or Real reports no detected license and GitHub's repository endpoint returns no detected license. For reuse, ask for the project's own license terms before treating public code as permission. Bundled third-party license notices answer a different question.
Questions people ask
Promoted posts in comments are outside the home-feed coverage the maintainer described in issue #2. The other recurring questions concern HDR output, signing and Safari's link-opening behavior.
Why do some Threads HDR videos download in standard quality, and which update addresses it?
Snowflake-2412 reported normal-quality downloads and further failures after v1.29.0; mumuisdog then reported a fix and linked v1.29.4 in issue #1. The current README also describes a lower-resolution fallback when video processing fails, so the setting and the resulting file deserve separate attention.
Does ThreadsPulse block promoted posts inside comments?
The maintainer says ad blocking currently covers the home feed. The reporter of issue #2 still saw promoted posts in comment view, and the maintainer requested screenshots or a recording and the Threads version.
Why does Share to Shortcuts stop working after signing a Threads IPA?
In issue #9, Snowflake-2412 reproduced the failure after re-signing without ThreadsPulse. The maintainer attributed it to re-signing. That comparison supports looking at the signing route rather than treating ThreadsPulse as the demonstrated cause.
How can Threads links from Instagram open in a sideloaded Threads app?
The maintainer's workaround is the GitHub Actions sideload IPA, its Open in Threads Safari extension enabled in Settings, and Safari set as default browser. Snowflake-2412 reported getting it working in issue #9.
Why is Open in Threads missing from Safari extension settings?
The maintainer says manual TrollFools dylib injection doesn't include the extension. Choose the sideload IPA containing it; the current README also says noplugins removes extensions. The packaging explanation in issue #9 directly answers the missing-settings report.
Can the Safari Open confirmation be skipped when opening a Threads link?
The maintainer says no: iOS displays the confirmation, and the Universal Links route that avoids it doesn't work for re-signed apps. That was the final answer to Snowflake-2412's follow-up in issue #9.
Can I lock video playback at 2x speed without continuing to hold the screen?
In issue #3, mumuisdog promised swipe-down locking for the next update. The current README separately documents a default playback-speed setting with a 2x option. A configurable default and the requested swipe gesture are different controls.
Can ThreadsPulse hide its buttons in screenshots?
The current README lists hiding ThreadsPulse buttons in screenshots and recordings. The earlier issue #3 response described that behavior as coming in the next update, so the live documentation is the newer feature statement.
Can downloads run behind a banner while I keep browsing?
In issue #5, mumuisdog said the popup had been changed to a banner for the next update so browsing could continue. The reply doesn't name a shipped version.
Can ThreadsPulse show who followed or unfollowed an account and track profile changes?
Follower comparisons and profile-change history appear as requests in issue #4, an open discussion with no comments. The README's Author Info feature displays account details; don't read it as confirmation of the requested history tracker.
Can ThreadsPulse download old voice recordings or music from posts and comments?
Those audio downloads are requested in issue #4. The discussion contains no maintainer response confirming support, so they shouldn't drive an installation decision.
Can I download all media from another Threads account at once?
Account-wide media downloads are another request in issue #4. Saving the media in one post, as the README describes, is a smaller operation than scanning and downloading an entire account.
What we have not tested yet
Our measurements cover the failed source-build and test-target attempts, not a signed app running on an iPhone. We have not tested the current v1.31.1 package, HDR preservation, playback controls, ad coverage, account switching or the Safari extension on a device. The missing Compose file prevented the separate container runner from producing a functional session; its generic deployment summary cannot serve as proof of one.
The HDR thread ends with the maintainer's fix report rather than a subsequent user check. The banner reply and swipe-lock promise don't identify shipped versions. Issue #6 alone doesn't show a merged Korean contribution. Current README statements are documentation, not our device results. No battery, download-throughput, bulk-workload or long-term account-safety results underpin this recommendation.
Licensing and security need their own examination. No detected project license isn't a legal audit, and the project-health page's absent security policy and attached release signature aren't proof of a vulnerability. We have no independent security assessment, demonstrated impersonation case or Meta ruling to report. Before replacing an installation you depend on, the useful next check is narrow: sign the intended package, try your own Shortcuts and Instagram-link workflow, and inspect a downloaded HDR sample on a compatible device.


