The launch of Proton Meet officially eliminates the lazy excuse that securing real-time WebRTC media at scale is "too hard" for modern enterprise platforms. Hopefully this forces the hands of Slack, Teams, and Google to stop treating E2EE as a premium afterthought and start offering it as a standard option for the modern web.
Proton Meet
21–30 of 64 posts
Re: Proton Meet
#22I wish Proton would focus on all of the missing features within their existing product suite before creating even more offerings to maintain
Still waiting for Drive for Linux.
Re: Proton Meet
#23I wish Proton would focus on all of the missing features within their existing product suite before creating even more offerings to maintain
Google docs may not be private but it takes 11-second load time for a page is a lot of friction in 2026, no matter how secure your product is.
Re: Proton Meet
#24So does that mean two people using this in the US will both have high latency to another country?
Re: Proton Meet
#25> in today’s unstable geopolitical environment, laws like the US CLOUD Act can compel US-owned video conferencing platforms to hand over any data they store, even if the servers reside outside of the United States So does that mean two people using this in the US will both have high latency to another country?
Re: Proton Meet
#26I wish Proton would focus on all of the missing features within their existing product suite before creating even more offerings to maintain
I might be an outlier here in caring about this product but I really want Proton Docs to get optimized better, it takes way too long to load. Google docs may not be private but it takes 11-second load time for a page is a lot of friction in 2026, no matter how secure your product is.
I would love to build on proton but Alas the API isn't open source and recently with Proton meet and its controversy, my trust on proton has shifted a bit too which dampened my enthusiasm in all of this.
(To make the API I even used puppeeter instances to do it, and after quite a long time I was able to succeed actually but that's just not scalable)
Re: Proton Meet
#27I wish Proton would focus on all of the missing features within their existing product suite before creating even more offerings to maintain
https://www.reddit.com/r/ProtonMail/comments/1bptl3c/shared_...
Re: Proton Meet
#28The launch of Proton Meet officially eliminates the lazy excuse that securing real-time WebRTC media at scale is "too hard" for modern enterprise platforms. Hopefully this forces the hands of Slack, Teams, and Google to stop treating E2EE as a premium afterthought and start offering it as a standard option for the modern web.
Slack, Teams and Google are meaningfully making this choice and that's because customers rarely care and yes, many of customers do prefer the server side transcriptions, recording and AI note taking.
Re: Proton Meet
#29I wish Proton would focus on all of the missing features within their existing product suite before creating even more offerings to maintain
Re: Proton Meet
#30> in today’s unstable geopolitical environment, laws like the US CLOUD Act can compel US-owned video conferencing platforms to hand over any data they store, even if the servers reside outside of the United States So does that mean two people using this in the US will both have high latency to another country?
Packet round trip between US and EU is approx. 100ms. Given acceptable latency for voice communication is below 300ms, we should not worry about that too much.
I do worry about it and I think lots of people will as well for other reasons.
One of them is screen sharing.