Provide module downloads on GitHub releases page

[Iron-E]

Is your feature request related to a problem? Please describe.

I use the latest version of my browser, hardened to prevent unecessary tracking and JS privacy breaches. It does not work on the website linked in the README. I've seen other issues on this repo about similar issues, where users have nonstandard browsers are unsupported by the website. These issues usually must be resolved through manual changes, which are understandably low-priority.

Describe the solution you'd like

Provide module downloads on the releases page of this repository. GitHub has already optimized this website for many browsers (including legacy ones), which would save you time and energy. You wouldn't have to worry about as many server costs / rate limiting either, since downloads would be on Microsoft's dime.

Other Magisk modules tend to use this approach as well (including Magisk itself)

[github-actions]

Thanks for your contribution! Please keep in mind we will get to this issue when we have a chance. Logs and device information are mandatory if you do not want your issue closed without response.

[androidacy-user]

The answer is no and will always be no.

Reasoning

Completely controlling releases from build to release gives us additional control over the process to ensure integrity, the ability to quickly pull back updates, a/b testing updates and the ability to monetize an otherwise costly (bandwidth and hosting wise for the backend the module uses) install process.

The bandwidth the modules use to download the required components uses more resources than the downloads of the modules themselves in almost all months we have statistics for.

We decided a long time ago we would not limit ourselves to providing an inferior solution with gobs of hacks around GitHub and their API. We understand this leads to frustrations for many users and have been working out the kinks and can say at this point in time, minus some legacy browsers and browsers with < 1% user share amongst our userbase, we believe we have resolved most issues resulting from normal browser and app usage (not accounting for extensions such as AdBlock).

We are also working on v11 which will have an even smoother install process, and have made UX improvements to downloads like improving error messages, improving UI, switching to CAPTCHA instead of wait times to keep the bots from using up free users bandwidth, and more.

Very few if no other modules have the same amount of time and effort put both in to the module itself and the backend resources powering it. No other module developer also has a paid staff nor the infrastructure we do.

I hope you understand our position.

[androidacy-user]

@Iron-E out of curiosity what's your setup? Like what browser and "hardening measures"? I'd be happy to pass it on to the right people to take a look

[Iron-E]

Mull with HTTPS-only, "custom" Enhanced Tracking Protection (no third party cookies; block tracking content in all tabs; no cryptominers, fingerprinters, or redirect trackers), all site permissions blocked (e.g. camera, location), Decentraleyes, and μBlock.

μBlock has disable pre-fetching, disable hyperlink auditing, disable webRTC, block CSP, uncloak canonical names, disable javascript by default (which I manually enable on certain websites), "I am an advanced user", every filter list (except regional) enabled, plus MVPS hosts and NoCoin.

FWIW the website also did not work even with μBlock, Decentraleyes, and Enhanced Tracking Protection completely turned off.