it can. I'm not saying it does, but it absolutely can
WhatsApp? It can by piggybacking the content on the client itself. It can't read on the server if it's as advertised as following the Signal Protocol.
But that kind of functionality either need targeted deployment, or have that built-in to the client in public channel. It doesn't matter if they does it or if they can do it, the logic of that functionality still have to exist somewhere. I would believe some nerds would pickup some indicators and had that reversed engineered long ago.
Without a solid proof, I would on the err side and refrain from claiming such.
They both are bad in privacy in one way or the other. WhatsApp is collecting vast trove of data about you, though it can't read the chat itself. Telegram doesn't have end-to-end encryption enabled by default, means anyone have access to the server can read your chat history, though you're last subject to data collection.
If you're doing illicit activity though, WhatsApp is better than Telegram because the chat contents are the evidence those law enforcements are going after, not the connection. They can't arrest you because you make friends with a criminal, but they absolutely can because you have a criminal action recorded in chat history.
Say I lived there. BBC needs fundings I get it, but what the BBC contributes to when I watch VoD? Not even watching live programmes as zero of the content have BBC ever contributed. When the content is licensed via BBC, I already paid part with my subscription. Thst's a disgusting double dipping. If no one watches your programmes that's your problem, and citizens have no responsibility to keep a corporate from collapsing. This shit reminds me of how NHK works in Japan.
I think to use it defensively, you should put the path into robots.txt, and only those doesn't follows the rule will be greeted with the maze. For proper search engine crawler, that's should be the standard behavior.
If I understand correctly, you want a two component setup. A PWA client for you to read the mail, and a server acts as IMAP client, fetches mails from all you mailboxes. The server will expose an API for tge PWA to access mail content. When new mail arrives, the server push a beacon via the Push API. The PWA would fetch the sender and title, and display a notification. If you clicks it, only then the PWA will fetch the body.
After a quick glance of the demo, I think SnappyMail fit the bill? It seems can be installed as PWA, and my browser does ask me if I want to give it push notification permission. However, I'm not too sure if the fetch logic happens as I laid out.
AFAIK, any. But expect performance lost due to bottoneck in bandwidth. Even the latest TB5 is only slightly faster than PCIe 2.0 x16. OCulink 2.0 can achieve PCIe 4.0 x8 which is way better, but Surface Pro have neither.
While I'm using Proton rn, I'm planning to migrate to Posteo with Addy.io for aliases. However they all cost money. If you mean free email that's not tie to a billionaire, I can't think one off my head. You can achieve "free" by hosting your own email server as it sounds you're intended for receiving only, but the electricity still cost some, plus you are doning free labor to make sure it is happy.
WhatsApp? It can by piggybacking the content on the client itself. It can't read on the server if it's as advertised as following the Signal Protocol.
But that kind of functionality either need targeted deployment, or have that built-in to the client in public channel. It doesn't matter if they does it or if they can do it, the logic of that functionality still have to exist somewhere. I would believe some nerds would pickup some indicators and had that reversed engineered long ago.
Without a solid proof, I would on the err side and refrain from claiming such.