Live data from Hacker News

Proton Meet

proton.me

21–30 of 64 posts

Re: Proton Meet

#21
post #3

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.

Who still believes that anyway given that WhatsApp, Facetime, and even Google Meet (formerly Duo) (formerly Hangouts) (the one that was not Google Meet 1.0) (not for Woरkspaces) have been supporting E2E multi-party video calls for a long time now?

Re: Proton Meet

#22
post #9

I 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.

They are hiring specifically for that: https://old.reddit.com/r/ProtonDrive/comments/1spx14d/proton...

Re: Proton Meet

#23

I 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.

Re: Proton Meet

#24
> 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

#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?

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.

Re: Proton Meet

#26

I 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.

The thing I am interested in proton docs is if it can have API functionality. Proton docs allow anonymous users to write things and I wish if there was an API functionality, then people can use it to create anonymous/(pseudonomous?) comments and hose those comments as a comment engine and many other interesting things like creating forms themselves on it.

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

#27

I wish Proton would focus on all of the missing features within their existing product suite before creating even more offerings to maintain

It would be really cool for them to get read/write calendar sharing on Proton Calendar to finally work on iOS. It's a huge pain, but just self-hosting a CalDAV server is still a better solution because I can actually share calendars.

https://www.reddit.com/r/ProtonMail/comments/1bptl3c/shared_...

Re: Proton Meet

#28
post #3

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.

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.

You can add the server to the call even if it is E2EE. You don't need to physically show it as a separate user and the client can hide that information and make it seamless.

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.

> 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.

Post reply on HN