SpacingBat3

> Current `electron`@19 package actually depends on `@types/node`@16, but this version doesn't contain definition for `NodeJS.Architecture`. Oh, that seems to actually be a reason. I think I'll just add newer...

~~Also, I may not be able to merge PRs that don't sign their commits:~~  Update: no longer the requirement. I can *bypass* checks and sign commits on my own...

@goosesima please resolve all of the conversations (if you disagree with my suggestions, just reply to me why and mark the conversation as resolved) and ESLint warnings. You can see...

> See new commit. Looks like a lot of great changes, actually! I see you've separated the CSS from the one that is always injected, which I approve. You've made...

This is actually an expected behavior – WebCord does not open any unsecure links. In WebCord, everything is enforced to HTTPS and anything that uses unsecure protocol is simply blocked.

That being said, images, videos, scripts etc. from `http:` should also be blocked.

The question is: is there ANY reason why to keep HTTP links as supported? It feels like it is a bad idea and probably is from the security point of...

> Yes, there is some reason to keep HTTP. Some small sites do not use https. Here an exemple link: http://christophe.bray.free.fr/informatique/falcon/Atari%20Falcon%20030%20versus%20Amiga%201200.pdf There should at least be an option to allow...

Is it granted via the **WebCord** settings window?

Also have you read the FAQ?