Proton Meet
proton.me83 points by Einenlum 3 hours ago
83 points by Einenlum 3 hours ago
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_...
Sometimes yes. But with Meet? No. I was really waiting for this!
I actually appreciate how they balance features and new products. They are becoming more credible MS365/Google Workspace alternatives with every step.
Still waiting for Drive for Linux.
They are hiring specifically for that: https://old.reddit.com/r/ProtonDrive/comments/1spx14d/proton...
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 <1 second to load when I click the browser bookmark, vs 11 seconds to load a Proton document.
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)
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?
unrelated but was using र a stylistic choice of some kind or a mistake? I thought my screen had a speck of dust or something on it (also what language do you speak if it was a mistake, linguistics are fun)
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.
This must integrate with Proton's appointment scheduling feature, no? That's a feature offered as part of their Workplace Standard and Workplace Premium plans. Does anyone have experience with that feature? How does it compare to the Microsoft Office 365 bookings feature? Honestly couldn't do my job without something like this manage my stacked schedule.
We at Sourcemeta (https://www.sourcemeta.com) are in the Proton business plan. The "Talk to an expert" and "Schedule Consultation" buttons in the main page point to my (the founder) calendar to book a slot.
No complains from it so far. People get it, book with success, and I run those calls on Proton Meet, which also proved to work pretty well.
Interesting to hear both user experience and thoughts on:
> 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.
Weird that the very first image in the article has a typo ("cancelation" vs cancellation).
American English allows the single l form, like traveling or modeling.
well to be fair american english is just a bunch of typos someone made standardised on because he didn't like the british
Works over MLS and performs well based on personal usage
How is this different from Keet?
[dead]
Honestly... No thanks. It's 2026, those who do not own a domain name should buy one an run their own Matrix/XMPP server.
most of the world has no need and no desire to do any of that. and i dont blame them, either. this is super-nerd level of advice.
proton meet is already targeting a really niche set of customers, and you're taking it to another level.
Or you can just run Jitsi Meet. E2EE is built in but you also have control of the server and the traffic to and from is encrypted