Discord port talk
-
wow-
-
Depending on what the actual issues are with Discord, it may be possible to get it working (in the normal DNS browser applet) by injecting javascript into the page that attempts to fix whatever the loading issues are.
So there's two main problems with that, the first is: how do you actual inject the JS? It is technically doable via DNS override to bypass CORS restrictions, however there will be an HTTPS security issue. That though, can also be bypassed by the user (It will prompt and say page is insecure, but in login applet you can accept this warning and load the page anyway). This part is technically doable, even if it's a little flakey.
The next problem is discovering what the actual issues preventing Discord from loading in the first place even are. If it's like, some newer javascript method that just needs to be polyfilled, there would be a pretty decent chance of success. But as of this time of writing, I don't even know where to start debugging that. You would need something like a webkit developer console / inspector that's accessible via Homebrew. Again, it should be possible to debug these issues (something like BrowseNX -> web inspector for instance) just not sure where to start.
Finally there's likely to be a third issue with something like, the page size being too large for memory. This too however potentially be patched via custom JS as well, to try to keep in-memory size low. This is another area where custom homebrew or emulating the web applet on PC would be useful to debug what the custom JS looks like.
From a user perspective, injecting "custom JS" like this is just essentially just acting as a browser extension, besides the part where you load it insecurely from overridden DNS settings. Disclaimer: this is all hypothetical!
tldr: 1. it's possible to inject custom scripts (aka "browser extensions") over DNS + accept security warning without homebrew, so 2. technically may be able to patch whatever issues there are with discord. But 3. need to figure out what those issues are in the first place, in order to know what to patch (which 4. may need custom homebrew or an emulator to debug).
@VGMoose so custom JS everywhere may get us somewhere.
calls my friend studying for a CS masters -
i will literally be the happiest man if I will get to access discord
Probably one of the oldest active people
-
-me trying to figure it out first-
-
LMAO
-
@Akaza idk why seeing others happy makes me feel happy inside
-
This repo appears to allow for some web inspector / debugging tools through DNS + PC, but it may not work on latest firmware. I have not checked yet: https://github.com/sudofox/switch-browser
@VGMoose just read it
imma go investigate -
people make me sad /j idk im just a depressed lil shit that has nothing to do lololol
-
lmao
-
Depending on what the actual issues are with Discord, it may be possible to get it working (in the normal DNS browser applet) by injecting javascript into the page that attempts to fix whatever the loading issues are.
So there's two main problems with that, the first is: how do you actual inject the JS? It is technically doable via DNS override to bypass CORS restrictions, however there will be an HTTPS security issue. That though, can also be bypassed by the user (It will prompt and say page is insecure, but in login applet you can accept this warning and load the page anyway). This part is technically doable, even if it's a little flakey.
The next problem is discovering what the actual issues preventing Discord from loading in the first place even are. If it's like, some newer javascript method that just needs to be polyfilled, there would be a pretty decent chance of success. But as of this time of writing, I don't even know where to start debugging that. You would need something like a webkit developer console / inspector that's accessible via Homebrew. Again, it should be possible to debug these issues (something like BrowseNX -> web inspector for instance) just not sure where to start.
Finally there's likely to be a third issue with something like, the page size being too large for memory. This too however potentially be patched via custom JS as well, to try to keep in-memory size low. This is another area where custom homebrew or emulating the web applet on PC would be useful to debug what the custom JS looks like.
From a user perspective, injecting "custom JS" like this is just essentially just acting as a browser extension, besides the part where you load it insecurely from overridden DNS settings. Disclaimer: this is all hypothetical!
tldr: 1. it's possible to inject custom scripts (aka "browser extensions") over DNS + accept security warning without homebrew, so 2. technically may be able to patch whatever issues there are with discord. But 3. need to figure out what those issues are in the first place, in order to know what to patch (which 4. may need custom homebrew or an emulator to debug).
@VGMoose so it is possible but no one has done it yet? (or has it been done?)
-
@VGMoose so it is possible but no one has done it yet? (or has it been done?)
@CarryOnBag-0 oh it's impossible
used to work
RIP discross -
I started looking into it more and it was harder than I described above... Maybe there are some people that are better at modding discord but right now it's not looking too optimistic.
It would also still be nice to be able to get a web inspector somehow, potentially through homebrew, to debug the specific issue further. I'm sure there's a way to do this but it's not known or understood.
