Keychat sends its traffic through a standard WebSocket on wss://443, advertising only the familiar h2/http/1.1 ALPN identifiers, so it’s indistinguishable from ordinary HTTPS traffic.
How do nostr:nprofile1qqsth7fr42fyvpjl3rzqclvm7cwves8l8l8lqedgevhlfnamvgyg78spz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0dsq3camnwvaz7tmwdaehgu3wvf5hgcm0d9hx2u3wwdhkx6tpdssexaht and nostr:nprofile1qqs8t4ehcdrjgugzn3zgw6enp53gg2y2gfmekkg69m2d4gwxcpl04acpzamhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtckhnhd6 protect against aggressive censorship like Russia implemented against nostr:nprofile1qqsygwfllr9zrmw63el9zz3d3there4hrlecj6dxnv6ky9dlks46cxgpr9mhxue69uhhyetvv9ujumt0d4hhxarj9ecxjmnt9ua3jglt? Deep package inspection to block access on a protocol level instead of blocking servers?
Discussion
Yes, this is something nostr fixes for free.
Not by default AFAIK, most clients send their user agent. Maybe your clients do fix that.