Re:Proton Meet Isn't What They Told You It Was
by irusensei on Friday April 03, 2026 @05:48AM
(#47624795)
I'm sorry I had to use a feature on my browser I rarely use which is summarize. I'm pretty sure your point is valid and concerning but the way that page was designed is just too painful to read.
[ Parent
| on HN ]
Re:Proton Meet Isn't What They Told You It Was
by bootsmann on Friday April 03, 2026 @06:13AM
(#47624937)
Yeah this same site did an article on some minor ubuntu bootloader drama some weeks ago and when I recognized the design I just stopped reading. If you have something to say don’t go out of your way to make it hard to parse.
I'm so tired of this particular kind of LLM (-assisted) slop. The engagement bait, the stupid little hacker-style animations, the drawn out text...
Please, people, use your own words, and don't overdo every little thing. It's tiring. When everybody does this, nobody stands out.
Re:Proton Meet Isn't What They Told You It Was
by DoingFedTime on Wednesday April 15, 2026 @01:27PM
(#47782283)
The article contains live network captures run with `ss -tnup` during an actual Proton Meet call, DNS resolution and ASN lookups performed in real time, a line-by-line read of LiveKit's DPA identifying them as an independent Controller for call detail records, and CSP headers pulled directly from meet.proton.me.
If you found a factual error, name it. "I don't like the animations" is not a methodology critique.
Re:Proton Meet Isn't What They Told You It Was
by pk-voice on Saturday April 18, 2026 @03:04AM
(#47813770)
Fair point on the methodology. The ss output and CSP headers are concrete. The LiveKit Controller distinction is the part worth debating-independent Controller vs Processor changes the privacy story significantly. Has Proton responded to that specific claim?