News for hackers. Stuff that matters.
Re:Proton Meet Isn't What They Told You It Was by rvnx on Friday April 03, 2026 @05:36AM (#47624737)
Most of the privacy claims (of all type of apps) are essentially garbage anyway because realistically, if a website or an app can be compelled to push an update to a specific user, then they can intercept anything they want.

It doesn't even have to be a specific binary, it can be "just turn on this A/B testing / debug flag for that user" or a piece of javascript

Re:Proton Meet Isn't What They Told You It Was by The_Goonies1985 on Friday April 03, 2026 @05:47AM (#47624789)
>Most of the privacy claims (of all type of apps) are essentially garbage...

True. Everything has backdoored CPUs as its foundation. Consider, for starters: (Intel's 'Management' Engine); AMD's (PSP); Apple/Arm (black-box hardware).

You can layer as much theater as you like on top of the hardware-surveillance-layer in modern computers; it still won't grant you privacy.

Re:Proton Meet Isn't What They Told You It Was by badgersnake on Friday April 03, 2026 @05:53AM (#47624815)
Power is open. But nobody wants to build power devices for some reason.
Re:Proton Meet Isn't What They Told You It Was by UltraSane on Friday April 03, 2026 @06:19AM (#47624972)
They are very expensive. Cheapest Power9 system Raptor Systems has is $6,794.99 and it has only 4 cores and 8GB DDR4 RAM and 128GB SSD. Reminds me of Sun Sparc pricing.

https://www.raptorcs.com/content/BK1SD1/intro.html

Re:Proton Meet Isn't What They Told You It Was by badgersnake on Friday April 03, 2026 @01:05PM (#47629232)
Yeah, that’s because nobody is building them so they have to use IBM server chips.
Re:Proton Meet Isn't What They Told You It Was by UltraSane on Friday April 03, 2026 @01:26PM (#47629475)
Why is the motherboard so expensive?
Re:Proton Meet Isn't What They Told You It Was by badgersnake on Friday April 03, 2026 @03:57PM (#47631437)
Same problem, low volume
Re:Proton Meet Isn't What They Told You It Was by ricardobeat on Friday April 03, 2026 @05:55AM (#47624827)
Power?
Re:Proton Meet Isn't What They Told You It Was by supermatt on Friday April 03, 2026 @06:01AM (#47624874)
Re:Proton Meet Isn't What They Told You It Was by ricardobeat on Friday April 03, 2026 @06:07AM (#47624908)
RISC-V is also open. That “some reason” is likely to be power/performance levels being quite far from ARM & Intel for consumer devices.
Re:Proton Meet Isn't What They Told You It Was by vrganj on Friday April 03, 2026 @06:17AM (#47624956)
China is building out RISC-V, just like they are leading actually-open AI.

https://www.scmp.com/tech/big-tech/article/3347684/alibaba-d...

Weirdly, the authoritarian state is the one saving us from our own digital authoritarians.

Re:Proton Meet Isn't What They Told You It Was by NitpickLawyer on Friday April 03, 2026 @06:36AM (#47625083)
> they are leading actually-open AI.

How are they leading? If I parse this correctly, "actually" open would mean fully open data training and weights? Then, by this definition, I'm only aware of Olmo (AllenAI - Seattle), Apertus (Swiss) and to some degree (unclear what data was actually published) Nemotron (Nvda, US). What are some examples of chinese similar models? (I'm not aware of any).

Re:Proton Meet Isn't What They Told You It Was by badgersnake on Friday April 03, 2026 @03:53PM (#47631376)
RISC-V is slow though
Re:Proton Meet Isn't What They Told You It Was by snvzz on Friday April 03, 2026 @07:29PM (#47633689)
RISC-V is an ISA.

There's nothing inherently slow about it, anymore than there is anything inherently slow about x86 or ARM.

High performance microarchitecture implementations are definitely possible. Some of them are available for licensing.

At least one of them (Tenstorrent Ascalon) has been tapped out into a chip and will show up in development boards later this year.

Re:Proton Meet Isn't What They Told You It Was by badgersnake on Saturday April 04, 2026 @07:11AM (#47638019)
If you can’t buy a fast one, then it’s slow.
Re:Proton Meet Isn't What They Told You It Was by snvzz on Saturday April 04, 2026 @10:19AM (#47639301)
>If you can’t buy a fast one, then it’s slow.

Shrug. The first RVA23-compliant chips are coming soon.

spacemiT K3 imminent (likely shipping boards this month) and Tenstorrent Ascalon (via Atlantis SoC devboard) this summer. These won't be the fastest CPUs available, but they'll meet the "fast enough" criteria for many uses and users.

Multiple parties including Tenstorrent expect performance parity with the ARM and x86 offerings available at the same time by 2028. Note performance is mainly gated by access to latest fab nodes, which comes with costs that necessitate serious volume. They expect to be there by then.

>But I don’t understand why the industry decided to start over with RISC-V when the compilers and toolchains and chips already existed in power land.

The rationale was documented in the "Instruction Sets Should Be Free: The Case For RISC-V" paper[0].

Note OpenPOWER is mentioned but is not in the comparison. The reason for that is simple: RISC-V predates OpenPOWER. It was an obvious reaction to RISC-V, and they were too late, as RISC-V already had the industry's attention. Furthermore, Open is a lie; payment to IBM is required in practice.

0. https://www2.eecs.berkeley.edu/Pubs/TechRpts/2014/EECS-2014-...

Re:Proton Meet Isn't What They Told You It Was by jagged-chisel on Friday April 03, 2026 @06:10AM (#47624925)
That’s no guarantee that a Power implementation isn’t compromised.
Re:Proton Meet Isn't What They Told You It Was by fsflover on Friday April 03, 2026 @06:47AM (#47625165)
Re:Proton Meet Isn't What They Told You It Was by txrx0000 on Friday April 03, 2026 @08:41AM (#47626023)
Counter-surveillance is not a binary switch. We can win by forcing the government to use increasingly expensive backdoors and exploits (>$10k per capita per year, beyond which mass surveillance is impractical even with a $1T budget). Hardware backdoor capabilities are costlier to maintain and use than something at the app level. Encrypting content and leaving metadata exposed is still better than encrypting nothing because they'll have less info to work with which means more effort. The point of all this is not to make it impossible for the gov and corps to surveil a targeted individual (of course they'd be able to if they expend enough resources). The point is to ensure that they only have enough resources to do targeted operations rather than blanket mass surveillance. The former is fine for a democracy, but the latter destroys it.
Re:Proton Meet Isn't What They Told You It Was by boramalper on Friday April 03, 2026 @05:56AM (#47624836)
> Most of the privacy claims (of all type of apps) are essentially garbage anyway

I think that’s a sweeping generalisation.

Re:Proton Meet Isn't What They Told You It Was by Ylpertnodi on Friday April 03, 2026 @06:20AM (#47624980)
And sweepingly true.
Re:Proton Meet Isn't What They Told You It Was by boramalper on Friday April 03, 2026 @08:31AM (#47625935)
How so? Reproducible builds are a thing.
Re:Proton Meet Isn't What They Told You It Was by stonogo on Friday April 03, 2026 @09:20AM (#47626387)
So are networks
Re:Proton Meet Isn't What They Told You It Was by boramalper on Friday April 03, 2026 @09:58AM (#47626720)
So? If the app is using reproducible builds and is also audited not to contain any backdoors, what do networks have to do with it?
Re:Proton Meet Isn't What They Told You It Was by victorbjorklund on Friday April 03, 2026 @05:59AM (#47624862)
I don’t think that is a useful definition even if technically true. With that logic even Linux isn’t privacy because in theory they can push code that will only run for you.
Re:Proton Meet Isn't What They Told You It Was by palata on Friday April 03, 2026 @07:03AM (#47625276)
I think the argument is that when you load a webpage, you download the code everytime you want to run it, from servers owned by the company building the service. So they can choose to serve you different software (e.g. with a backdoor), just this one time and just for you, and you won't know (not that it would be impossible, but it is generally impossible in practice).

When you download a program on Linux through the distro package manager, you download it once and run this, every time. You know very well when it gets updated. You can compare the hash of your program/package with the one distributed by the distro, and the distro is not the developer of the program (so there is another layer there). You can audit that code (if open source), and at the very least you can compare with others to see if they receive the same code. And again, the program is served by the distro, not by the developer. The backdoor situation would require asking the developer to implement a backdoor, and then asking the distro to server you a different executable, and then hoping that you never, ever check the hash of that program that you own offline. It's a lot harder.

In a way, for ProtonMail (in your browser) to be "end-to-end encrypted", you have to trust Proton. But that kind of defeats the purpose of end-to-end encryption.

Same applies to e.g. WhatsApp Web, which is an interesting example because there exists a browser extension allowing you to "validate" that you run the code Meta expects you to run. Though you still have to trust Meta: the extension only helps making sure that nobody other than Meta is abusing you. The WhatsApp mobile app doesn't have that problem, as it is distributed as an archive by a third party (Play Store).

Re:Proton Meet Isn't What They Told You It Was by IAmBroom on Friday April 03, 2026 @08:24AM (#47625880)
> In a way, for ProtonMail (in your browser) to be "end-to-end encrypted", you have to trust Proton. But that kind of defeats the purpose of end-to-end encryption.

Yes, and every VPN in the world (that isn't self-hosted) relies on trust that they won't share your info, not even your fingerprint - which defeats the purpose of VPNs. It's very hard to have perfect security. OK, impossible.

Re:Proton Meet Isn't What They Told You It Was by palata on Friday April 03, 2026 @09:22AM (#47626402)
Sure, it's always a tradeoff. There is no "perfect" security, but there is "better" and "worse" for the threat model.

My point here is that when you run a webapp from a browser, you have to trust the server. When you run a program that you download on your system, it's easier to check that it doesn't change and to make sure that others get the same one.

Re:Proton Meet Isn't What They Told You It Was by mapontosevenths on Friday April 03, 2026 @10:00AM (#47626745)
Exactly, as with all security you have to ask what the threat model you're defending against is and what you're willing to pay.

If it's "Google knows too much and I want an alternative" Proton is great, cheap, and convienent. If it' "my own government might kill me" then it might be time to think about self hosting.

Re:Proton Meet Isn't What They Told You It Was by palata on Friday April 03, 2026 @11:08AM (#47627533)
> "Google knows too much and I want an alternative" Proton is great, cheap, and convienent.

I think that Proton does a good job with the suite (docs, sheets, calendar, password manager), and I believe they have a good VPN (for what we may expect from a VPN).

Interestingly, Proton started with ProtonMail, and I find it's the least convincing of their products:

1. As an individual, writing from your ProtonMail account to (probably) someone on GMail doesn't change anything.

2. As a company, writing from Proton to Proton is a good idea, but there is no need for end-to-end encryption: just choose a mail provider you trust, I guess?

3. The ProtonMail end-to-end encryption in the web browser defeats the purpose of E2EE: you have to trust Proton anyway, because they serve the code every time your employees load the page.

Re:Proton Meet Isn't What They Told You It Was by maweaver on Friday April 03, 2026 @06:30AM (#47625040)
Using what mechanism? Most Linux updates are not pushed but rather pulled at the user request. You can use Linux totally offline. This is fundamentally different than a webapp, where code is sent with every visit
Re:Proton Meet Isn't What They Told You It Was by izacus on Friday April 03, 2026 @07:05AM (#47625285)
The automatic updates most distros have enabled by default. Signal desktop outright stops working if you don't constantly pull updates from them.
Re:Proton Meet Isn't What They Told You It Was by the8472 on Friday April 03, 2026 @07:53AM (#47625637)
Distros have mirrors and they don't know which one you use. The updaters don't send user IDs and downloading the package lists is separate from downloading the packages. So targeted backdoor distrubution is much harder than a company's web UI with user logins targeting a specific user.
Re:Proton Meet Isn't What They Told You It Was by 63stack on Friday April 03, 2026 @07:38AM (#47625516)
Debian requires unattended-upgrades to be installed (it's not installed by default), Mint and Fedora has the option of enabling automatic updates (disabled by default), Arch has no mechanism for automatic updates.

Which ones are these "most distros"?

Re:Proton Meet Isn't What They Told You It Was by littlestymaar on Friday April 03, 2026 @07:12AM (#47625329)
Signal pushing updates every other day is pretty much a security anti-pattern though. It makes it almost as vulnerable as a web app to this kind of thing, but this isn't the typical Linux software experience by any stretch.
Re:Proton Meet Isn't What They Told You It Was by izacus on Friday April 03, 2026 @01:03PM (#47629204)
A typical user experience is Ubuntu/Fedora with Auto Updates from repos enabled.
Re:Proton Meet Isn't What They Told You It Was by victorbjorklund on Friday April 03, 2026 @04:17PM (#47631686)
Can you honestly say that you never ever updated anything in a Linux distro without first reading all the code, comparing all the checksums etc?
Re:Proton Meet Isn't What They Told You It Was by aragilar on Saturday April 04, 2026 @12:50AM (#47635880)
The checksums are verified automatically, based on a key bootstrapped by the original install (which could, though likely not done, be verified by other means). As happened with xz, you either get everyone or no-one.
Re:Proton Meet Isn't What They Told You It Was by progbits on Friday April 03, 2026 @06:28AM (#47625033)
How will they push it?
Re:Proton Meet Isn't What They Told You It Was by victorbjorklund on Friday April 03, 2026 @04:19PM (#47631708)
Push or pull is just semantics. Can you honestly say that you never ever updated anything in a Linux distro without first reading the source code, checking all the checksums etc? Be honest.
Re:Proton Meet Isn't What They Told You It Was by 63stack on Friday April 03, 2026 @06:17AM (#47624957)
Linux as in the kernel? Who is "they"? Torvalds?
Re:Proton Meet Isn't What They Told You It Was by victorbjorklund on Friday April 03, 2026 @04:21PM (#47631726)
Choose if you think Windows is just the kernel or the operating system.

The ones that control whatever source you are pulling the updates from. Very very few people are building everything from source and reading the source in full everytime.

Notice I am not saying this is likely. I am saying that it is theoretically possible anytime you accept code from the outside (doesn’t matter if it is pull or push)

Re:Proton Meet Isn't What They Told You It Was by Imustaskforhelp on Friday April 03, 2026 @06:17AM (#47624960)
I once did some tinkering with Proton Docs and I was able to find that the comments within Proton Docs when I used it via curl definitely felt like it had something like logs (I feel like I should try doing this again to have more definitive answer)

Either way, the response was encrypted but they hold the encryption key atleast within proton-docs.

I also want to say that Proton allows the ability to change password through OTP, (Something which I sorta appreciate[0]) but that means that their infrastructure can then have the ability to change password and you can toggle that functionality by sending a request to proton to allow OTP and on which number, so proton themselves can do that too. Unless, I am getting it wrong, by default, Proton still has your encryption keys and even if you change them (which 99% including me might not do), even then I definitely feel like there can be some concern.

To be honest, There is nothing like zero trust, that's what I learnt, You are still trusting Proton Aka The swiss laws behind it so that you know that they won't get legally forced to give more data than usual (like US companies for example) but they will still comply with the swiss laws (recent proton incident)

Then, secondly, you have to trust Proton themselves, but with something like this incident where Proton Meet might be omitting somethings, it doesn't paste a clear picture of transparency or trust.

I don't really know why Proton might create something like Meet especially with its infrastructure relying on the CLOUD Act, and then, try to sell it within the idea of privacy. They both are contradictory.

Proton is, creating lots of products, On one hand I can appreciate that, but on the other, as part of community, I feel frustrated/sad because they don't have some core features like proper proton drive rsync support or even some API[1]'s surrounding it. I tried to do the experiment in first place because I wanted to create a commenting engine for static websites which could use proton-drive as its backend. They really could gain a lot from transparency with proper API support and letting the community do things with it, but that's not really the case :/

I am still using Proton but they definitely aren't a bastion recently. I might still recommend Proton, but I sort of hope that companies self host some open source applications themselves, whether self-hosting with hardware or in a proper EU cloud like Hetzner/OVH.

But Incidents like these are making me a little more hesitant to recommend Proton nowadays.

[0]: as someone who had lost one of my previous accounts after my Keepassxc database got deleted because of me accidentally wiping my archlinux with tinkering with it, Now I use Bitwarden with OTP on proton.

[1]: I was able to make something like an API myself by relying on something like puppeteer, even with puppeteer though, it was really hard to make something like that. I couldn't create a public endpoint of it because having puppeteer instances for a commenting engine would be very resource intensive.

Re:Proton Meet Isn't What They Told You It Was by henearkr on Friday April 03, 2026 @05:42AM (#47624764)
Is there any evidence that the mechanism to do that is in place?

I think that would be widely decried especially on HN if that is one day implemented.

Re:Proton Meet Isn't What They Told You It Was by chrismorgan on Friday April 03, 2026 @06:06AM (#47624898)
You need mechanisms to avoid the possibility. The mechanisms to do such things exist by default, by both the software provider (e.g. Proton) and the software distributor (e.g. Apple for App Store, Google for Play Store, Cloudflare or AWS for web stuff), and various countries have laws that allow them to secretly compel implementing specific backdoors.

In order to block the distributor from going rogue, you need to be able to guarantee that the user device can only install/run code signed by the provider, who must never give those keys to the distributor. My impression is that Android is the only major platform that ever had this, but that Google ruined it a few years ago in the name of lighter bundles by insisting that they hold the keys. (I once had VLC from Google Play Store, but replaced it with a build from F-Droid under the same app ID; Google Play Store shows it has an update for it, but that it can’t install it.)

In order to block the provider or distributor sending specific users a different build, you need something more like Certificate Transparency logs: make it so that devices will only run packages that contains proof that they have been publicly shared. (This is necessary, but not sufficient.)

And if you’re using web tech, the mechanisms required to preclude such abuse do not at this time exist. If you’re shipping an app by some other channel, it can do a resource integrity check and mandate subresource integrity. But no one does things that way—half the reason for using web tech is specifically to bypass slow update channels and distribute new stuff immediately!

Re:Proton Meet Isn't What They Told You It Was by Cthulhu_ on Friday April 03, 2026 @05:45AM (#47624779)
Yes? A/B testing flags, auto-updates, server-side re-routing, etc are just some mechanisms from the top of my head that can do that.

The ways to avoid it is by having locked and cryptographically verified software and connections.

Re:Proton Meet Isn't What They Told You It Was by izacus on Friday April 03, 2026 @06:12AM (#47624932)
That's not evidence, that's conjecture again. Is there evidence that this kind of client push is actually used to extract data in these projects?
Re:Proton Meet Isn't What They Told You It Was by nextaccountic on Friday April 03, 2026 @06:25AM (#47625005)
That's evidence for the mechanism, as asked

The evidence that it's being actively used in the US is in the secret proceedings of a secret court. I kid you not, look up FISA warrant

Re:Proton Meet Isn't What They Told You It Was by henearkr on Saturday April 04, 2026 @06:36AM (#47637809)
There is NO such mechanism (discriminated updates by user), of my knowledge, in:

- Linux (apt, pacman, rpm...),

- Android

And I would add Windows and iOS/MacOS but I'm not at all an expert so I leave others to confirm that their "app stores" don't do such exotic prowesses.

You can artificially insert a malicious script in a package that would scan your system, deduce your identity, and install something based on that, but in this case that means that it is just a malware in the first place. And that would mean that the app to be installed contains a "mutable" component of data that is not defined by the contents of the package but rather written upon post-install actions, so that is also dubious to include that for formally in the "app from that package" definition. In any case, such behavior would get your package banned from any app store or Linux distribution.

Re:Proton Meet Isn't What They Told You It Was by nextaccountic on Saturday April 04, 2026 @09:16PM (#47645223)
Yes, the US government and US courts (including the secret court FISC) have tools to compel Google, Apple and other vendors to install malware on users devices. This is exactly the point.

The US government routinely deploys malware to users devices, for multiple reasons. Here is a 2017 link about this: https://www.aclu.org/news/privacy-technology/challenging-gov...

Re:Proton Meet Isn't What They Told You It Was by henearkr on Saturday April 04, 2026 @09:38PM (#47645337)
Would you mind showing me some evidence that software update systems are able to push to you e.g. a different Android update based on your device ID or specific IP? (not just country geolocation) (PS: your link is about deploying malware through other routes, not by normal software updates)

Because all the other means I can think of are just basic malwarfare.

As you need to rely on a vendor/distributor to get updates, then of course they are able to push you malware, there is absolutely no going around this first ring of trust.

Conclusion : there is no point in accusing Proton of anything... there are just being software providers (FOSS by the way!!!).

Re:Proton Meet Isn't What They Told You It Was by Imustaskforhelp on Friday April 03, 2026 @06:20AM (#47624975)
Not sure if that counts as proper evidence, but I have seen some logs[0] albeit with encryption but from my understanding, they control the encryption keys or atleast certainly have the ability to change (if they get hacked themselves for example)

Would you like to see a proper evidence of the logging policy? I feel like I can try finding that again if you/HN community would be interested to see that.

Edit: also worth pointing out that keeping logs with time might be a form of meta-data, which depending on your threat-vector (journalism etc.) can be very sensitive info.

[0]: my another comment here: https://news.ycombinator.com/item?id=47624960

Re:Proton Meet Isn't What They Told You It Was by izacus on Friday April 03, 2026 @07:00AM (#47625259)
I'd like to see any kind of evidence that there's any substance of in these accusations of services not actually being private - not just theoretical theorycrafting about mechanisms.

And how does that compare to other services we have available and people actually use.

Re:Proton Meet Isn't What They Told You It Was by Imustaskforhelp on Friday April 03, 2026 @10:15AM (#47626903)
At some point, essentially everyone has to trust the product and more importantly, the company/the people in the company. Firstly its worth clarifying that there isn't really something akin to zero-trust in such cases. Thus the theoretical theorycrafting about mechanisms. Those show that you have to trust proton

Now, My issue with proton is that, they try to appear transparent but a lot of what they've done especially with proton meet seems to sometimes even be misleading. If they couldn't create EU/Swiss sovereign infrastructure for meet, then why are they using Cloud-act providers while within the same post talking about the implications of Cloud Act. There is some great irony in all of this and this is what is making me suspicious and how Proton seems to be misleading people rather than leading them towards more privacy.

At some point, it raises atleast some questions about trusting proton.

> And how does that compare to other services we have available and people actually use.

That depends on what service are you talking about from, Do you want a whole eco-system or are you happy with individual apps/companies focusing on one thing in a more unix-fashion of things.

Do you prefer non-profits or for-profit companies to handle such infrastructure?

How familiar you are with self-hosting and what is your threat vector?

Are you a corporate or a person yourself and what are your budget of things?

but just to give a pointer without asking these questions, Some good pointers are posteo.de, tutanota, infomaniak (has whole ecosystem) Within the calling system, I personally used to use fairmeeting.net, it used to have screen sharing option for free as well but looks like they might have paywalled it recently. You can find multiple jitsi community instances.

I feel like the only way to answer this question is if people ask with more depth. The threat model differs for everybody, for some people (like journalists), even just this proton meet fiasco is enough for them to reconsider proton ecosystem as a whole and consider it too threatening, especially with recent incidents and their lives being on the line. You might say, well where might they go and I feel like they might go to disroot (non-profit activism oriented) or tutanota or even posteo.de depending on what they might prefer.

Re:Proton Meet Isn't What They Told You It Was by henearkr on Saturday April 04, 2026 @06:32AM (#47637781)
One by one:

- A/B testing is agnostic of who the user is, it is randomized. If it was not, that would be a bad practice and would legitimately ruin the reputation of the company doing that,

- auto-updates is just the setting allowing the most recently published update to be installed. "Published" means it is for everyone. If that is to be understood in any other meaning, that would also be bad practice,

- and I don't see what you mean by server-side re-routing.

To be honest, maybe I just live with different platforms and apps than you I don't know. I use Android, and Linux on my Laptop, but I would also expect Windows to not discriminate by user when pushing updates.

Re:Proton Meet Isn't What They Told You It Was by kalaksi on Friday April 03, 2026 @06:11AM (#47624929)
You'll have to be more specific what kind of "privacy claims" you're talking about. Proton is definitely a lot more private than, say, Google. But, as always, you'll have to trust the party delivering the binaries you run. Also, any company operating legally, have to co-operate with court orders etc., but afaik they try to push back
Re:Proton Meet Isn't What They Told You It Was by akimbostrawman on Friday April 03, 2026 @08:19AM (#47625840)
>if a website or an app can be compelled to push an update to a specific user, then they can intercept anything they want

yes which is why i hoped they would implement a verification system like with a browser addon that compares the website client code used for encryption and alerts the user if it does not match the one served everyone else.

ctemplar mail used to have this many years ago

https://web.archive.org/web/20200201012958/https://ctemplar....

Re:Proton Meet Isn't What They Told You It Was by illiac786 on Friday April 03, 2026 @08:32AM (#47625943)
Privacy and security are not binary. Statements like “because it isn’t 100% secure or private, then it is not worth it” means one has essentially no clue. There is not such thing as 100% privacy or security, for starters.

It’s all layers of protection and/or trust and compromises.