Discussion: Support for TLS Fingerprint Impersonation (uTLS) to prevent JA3 detection

[josemgjunior]

Currently, whatsmeow/socket is tightly coupled to the standard crypto/tls library. This causes two main problems regarding JA3 identification:
Direct Connection: The standard Go handshake is easily flagged as a bot by the Meta infrastructure.
Proxy Connection: Even when using a custom Dialer for a proxy, the subsequent TLS update still uses the standard Go identification or, worse, fails to mimic the behavior of a browser through the proxy tunnel.

The Flow: whatsmeow opens a direct TCP socket with the WhatsApp server and initiates TLS immediately.

The Risk: Because Go sends its own standard ciphers and extensions, WhatsApp detects a "Go signature" instantly.

uTLS needs to act on this first call so that the Hello Client is already "disguised" as Chrome or another browser...