fp.

We actively invite cybersecurity professionals, researchers, and cryptography experts to: Review our open-source codebase Analyze security mechanisms (ECDH + DTLS + SAS, ASN.1 validation, etc.) Share feedback, ideas, and suggestions for improvement Propose new features or enhancements Your expertise is essential to making SecureBit the most private and secure P2P messenger for the future.

baobun•4mo ago

Would make it easier to audit if you removed and .gitignored some generated stuff. In particular node_modules (given that you check in the lockfile with hashes it should be redundant).

SecureBitChat•3mo ago

Okay, I'll do that in the new release.

roscas•4mo ago

Maybe you can explain why it connects to google because it makes no sense at all.

      iceServers: [
        { urls: "stun:stun.l.google.com:19302" },
        { urls: "stun:stun1.l.google.com:19302" },
        { urls: "stun:stun2.l.google.com:19302" },
        { urls: "stun:stun3.l.google.com:19302" },
        { urls: "stun:stun4.l.google.com:19302" }

SecureBitChat•3mo ago

At the moment, my startup doesn't have the funding to set up our own stun servers. Going forward, we won't be using public servers, but rather our own.

roscas•4mo ago

Does it connect to Google or Facebook or any other site?

SecureBitChat•3mo ago

At the moment only stun servers are used