Default WebCord Settings #351
-
|
First, many thanks for the detailed reply to my question about ublockorigin vs webcord, very interesting to read! I have three more questions, i had webcord installed with electron version 21.2.2 and application version 3.9.3 To my final question, after installing webcord for the first time i noticed that under > settings > permissions > access to record the desktop screen and one more feature where enabled, would it be possible to disable that by default so if we really want to we can enable it manually?
Same goes for > settings > content security policy / third party websites (by default all of them where enabled...)
|
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
Someday it might reach it for Windows (there isn't even a mature installer yet!), for others I might be unable to do that (for Linux alternative would be to publish it to repo or host it on your own, macOS however seem to require signed binaries so RIP).
WebCord uses default directories for storing data, listed in Electron docs. I believe
It really shouldn't be – the dialog will prevent recording your screen without your consent anyway. It's just here so you can even silence dialogs. Most likely that will never be needed, but it's better to be safe than sorry.
Definitely not most of these, neither all of them. Actually those Discord ones most likely could be a thing, but given iframes shouldn't normally access all of the parent resources (including
I won't set it, for convenience of some newbie users. Blocking some of them actually may break your client and prevent you doing from some actions like even logging-in (i.e. you need to allow Discord connecting to hCaptcha for a captcha iframe to display). So there are good reasons why these were never be disabled by the default, but should be made available to the users just so privacy hardening is possible. The "connect" word actually means that Discord is at least capable of fetching some static files from them. Technically, CSP itself defines an entire ruleset – I won't go into the details, it would take too long to explain it whole. In worst cases, there will be allowance for Outside of all of this, cross-site cookie tracking is not effective as well – we're only showing single page in WebCord for most cases (unless you use different Discord instances – I don't think that's much of the change of the situation through)! There should also be no way to navigate to page outside of the pages WebCord trust, but even considering that would be possible or there are such cross-origin cookies that are shared to iframes, at worst someone would just associate you with using Discord, nothing more. |
Beta Was this translation helpful? Give feedback.
-
|
Sounds like all in all, webcord has the best privacy-standard possible for people that rely on discord but don't agree with the tracking. |
Beta Was this translation helpful? Give feedback.
-
Sometimes your perception of world makes me laugh 😂. Also take a note WebCord does not allow third-parties by themselves, but rather services that Discord serves integrations to (I mean YouTube is technically owned by Google, yet it is a separate service from Google Storage API that Discord seems to use for uploading files for some time). And for a longer lecture about which specific URLs matching given parts of the URL are allowed and for which type of the content, take a tour there: WebCord/sources/code/main/modules/csp.ts Lines 99 to 208 in d0cb8c4 |
Beta Was this translation helpful? Give feedback.
Someday it might reach it for Windows (there isn't even a mature installer yet!), for others I might be unable to do that (for Linux alternative would be to publish it to repo or host it on your own, macOS however seem to require signed binaries so RIP).
WebCord uses default directories for s…