oSumAtrIX

> Fingerprints and patches are not guaranteed to always work. Nothing is, but if the confidence is high you can bet on it more often than having to maintain bumping...

> Then users can venture into the unknown, while users who just want a working app can use the recommended target that is well tested. The patches breaking can be...

If there's flags, there's more than one code path for a specific feature. A patch targeting a version with such flags must support both or force one path. This doesn't...

The code path are known thanks to the flags that exist at the time of the version. This has nothing to do with flags. New versions, new code. It's just...

2 requires most certainly the user downloading the version. 2 requires O(N) developer time. 2 inevitably is the easier route you take instead of the more resilient route of designing...

> The recent YT Music spoof payback that broken for months was not 99% uptime. That's the sharp shooter falacy. We're looking at all patches, not a handpicked individual to...

> But nearly all users need GmsCore, which means they also need spoof streams. That doesn't mean anything for the theme patch for example. Like I said the spoof patch...

It's not a lie. A. Each patch supports individual versions B. Manager requires the default selection C. The most compatible version is calculated and required (in the future multiple will...

> When 99.9% of users are not rooted, then it's a lie to 99.9% of users. Once again here as well, the installation method is not a concern of the...

What I argue for is still the second. Refer to second paragraph https://github.com/ReVanced/revanced-patches/issues/6274#issuecomment-3511733309