Here’s the repo in case anyone is interested in hosting an instance: https://github.com/signalapp/Signal-TLS-Proxy
They don’t want to ban encryption, they want to block encrypted chat apps, precisely so they don’t have to build backdoors. AFAIK it’s not possible to break signal/WhatsApp encryption without access to the targeted device, and once you have access you can get the messages directly without having to break the encryption.
Ever noticed how those notifications include the message content and the sender? Google has access to this information, despite the encryption.
Not necessarily. I work on a messaging app, and we only use firebase to “wake up” the app. Initially the notification doesn’t display anything meaningful, but the app very quickly connects to the server (tells the app who it should connect with) and then the peer (to finally get the actual content). The notification is updated once we have the content. But it typically goes so fast that you only ever see the final version of the notification.
Yeah but if the script which initiates the connection to the local server is blocked there’s no connection to intercept in the first place.