Cas_

> I meant already possible i.e. --app already handles webmanifest/PWA features without requiring an --app-id or install haha, but good info nevertheless. yes but app-id install enables PWA features, --app...

notable issue: installable PWAs sometimes get unregistered across updates so the app-id would likely need to be re-registered after each startup this also doesn't solve the issue of API's such...

documenting: https://chromium.googlesource.com/chromium/src/+/refs/heads/main/docs/windows_pwa_integration.md#file-handling-support

> Would be cool, currently is just in order of most preferred/usable by Gluon. Would likely use reg.exe directly to avoid external dependencies. winreg doesnt have any external dependencies, so...

> I meant having a dependency at all, as you can make a wrapper for reg.exe in ~5 lines hm, too bad, wanted to PR this using that lib, but...

> Preferred file associations for `.html` would be a generally safe bet, but accessing based on https preferences may be the best way to go? Windows is a "little" aggressive...

> On Windows getting exe path from this is most universal: `HKEY_LOCAL_MACHINE\SOFTWARE\Classes\${ProgID}\shell\open\command`. It will also work when users have non-standard path. Which would be more common for Firefox then Chrome...

unfortunately, the webtorrent spec never defined how to support PeX or DHT so it was never implemented, webrtc functions a lot differently than other protocols so it was never decided...

I have low interest in supporting linux package managers, because there are more issues per package manager, than in all of Miru together, to put it simply it's a waste...

what's the status on this?