Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Proton Meet

proton.me

Post reply on HN
Print view View original

31–40 of 64 posts

Re: Proton Meet

#31

Post by mghackerlady »

lxgr wrote: post #21
mikece wrote: 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?

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)

Re: Proton Meet

#32

Post by mghackerlady »

buran77 wrote: post #20
LoganDark wrote: post #18

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

Re: Proton Meet

#33

Post by interf4ce »

kkfx wrote: post #6

Honestly... No thanks. It's 2026, those who do not own a domain name should buy one an run their own Matrix/XMPP server.

I don't think that's the target audience here.

Proton makes safer, more private (than, say, Gmail) email a possibility for people who don't have much technical knowledge but who know enough to want to keep their emails out of Google's hands.

If you have both the knowledge and time to run a server, by all means, that can make sense (and can be fun!). It's just not as widely applicable.

Re: Proton Meet

#34

Post by lxgr »

mghackerlady wrote: post #31
lxgr wrote: post #21

Earlier quoted context omitted.

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)

Just a typographic approximation of my mental state when thinking about Google's instant messaging product naming and strategy, or rather the lack of both :)

Re: Proton Meet

#35

Post by LoganDark »

buran77 wrote: post #20
LoganDark wrote: post #18

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.

I stand corrected; American English uses double-l in places like "compelling" but not always in places like "canceling".

Re: Proton Meet

#36

Post by HDBaseT »

ranger_danger wrote: post #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?

[dead]

Re: Proton Meet

#37

Post by kkfx »

interf4ce wrote: post #33
kkfx wrote: post #6

Honestly... No thanks. It's 2026, those who do not own a domain name should buy one an run their own Matrix/XMPP server.

I don't think that's the target audience here. Proton makes safer, more private (than, say, Gmail) email a possibility for people who don't have much technical knowledge but who know enough to want to keep their emails out of Google's hands. If you have both the knowledge and time to run a server, by all means, that can make sense (and can be fun!). It's just not as widely applicable.

You send emails to @gmail addresses most of the time, so... How you can avoid giving Alphabet (or some other giant) your messages?

The point of ownership is having your mails in your hand, on your iron, anything who can talk IMAPs or even POP is ok for that. For voice/chat etc Matrix or XMPP might be yours, so nobody could decide to ban you or shut the service down. You still depend on a ISP ok, but much less dependencies anyway. That's the point IMVHO.

While thinking that company X is better in privacy terms than company Y is honestly meaningless, you can trust them or not, you don't know what happen on their servers or someone else ones where they actually live on (like using Amazon o Microsoft cloud as a backend).

Re: Proton Meet

#38

Post by stackskipton »

charcircuit wrote: post #28
stackskipton wrote: post #12

Earlier quoted context omitted.

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.

Sure, you COULD or you could just encrypt between client and server and be done with it.

Business users are their focus and outside select industries, vast majority of businesses don't care if government is spying or not. Heck, most businesses would turn over information to government without any fight. It's just not something they worry about.

Post reply on HN