-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(plugin): WebPWA #2994
base: main
Are you sure you want to change the base?
feat(plugin): WebPWA #2994
Conversation
2de2cce
to
8a021a2
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Brilliant idea with a few too many assumptions about where the code is running.
Ignore the outdated stuff, you made a lot of changes did many force pushes while I was trying to review this.
@Sqaaakoi any chance if you know if discord still hardcodes 720p 30fps for screensharing? I remember from GM days the browser code looked something like: screenShare(videoQuality, audioQuality) {
// just ignore the settings lol
return navigator.mediaDevices.getDisplayMedia({ video: { height: 720, frameRate: 30 } })
} but I'm struggling to navigate the new minified code, I wanted to fix that in this plugin too, but I can't verify if it's an issue |
I'm pretty sure it does, but do not count on my word. I am not sure if this plugin is the right place to be doing it, 2 reasons
|
Co-authored-by: Fafa <[email protected]>
I suspect this isn't going to work when using the userscript version because of Discord's CSP. I tried to manually inject the webmanifest just by copying the code out of here:
|
I'm unsure why? This plugin works fine on my end? I'm running brave with the vencord extension |
I mean the userscript version of Vencord, not the extension. |
ah yeah, it defo won't work there, nothing you can do about it, but it's a non issue, the extension is fine, and it's not heavy or problematic in any ways, the bigger issue is discord calls randomly dying because chromium suspends audiocontext in the tab for inactivity |
ah right, that'd make sense, hmmmm |
@xPaw try that |
que? this part works fine for me?
that's what this is for |
open devtools and look at the application > manifest, it reports an invalid scope url.
I don't know what that does, if anything. |
I'm uncertain why that patch wouldn't work for you, I copied it 1:1 from vesktop |
Does it for you? Can you make a screenshot. |
I'm doing these updates from my lap on my phone, so not really no |
https://developer.mozilla.org/en-US/docs/Web/API/Window_Controls_Overlay_API is what that option is for. |
yes im aware, but i'm patching discord to use native title bar, it's not for some reason |
This plugin makes discord installable as a PWA when used in browser, it's effectively a more than slightly worse version of Vesktop, but since it can re-use a browser that's already in use, does wonders for reducing RAM usage even further on devices which have little of it.
This enables vencord on web to:
Most of this code is re-used from vesktop with slight alterations