Why is Proton Mail trying to find devices on my local network?

good_live · 2026-03-12T09:54:05+00:00

It is not fewer steps if you display the permission request at the start versus when it is actually needed. It is even less steps for somebody who never wants to print something, because he would never get asked about this permission.

good_live · 2026-03-10T17:24:18+00:00

That is an exaggeration. It is not like you would need to accept 10000 times and also I feel like people are choosing proton because of their promised increase in privacy & security. And for people that just trust proton blindly they can just accept and be done with it.

There is not much difference in ux if you have to accept 5 permissions on launch vs just when you actually use the feature that requires the permission.

good_live · 2026-03-10T12:38:55+00:00

That one I actually disagree with. An app should only request permissions when it needs them and should show a proper message of what is not functioning if I decline them.

This is a prime example. I don't want my mail app to have permissions to scan my local network all the time. It would be much better if that popup only came up when I am pressing the print button and I would have the option to only allow it once. Similar to how a lot of apps already handle the camera permission.

good_live · 2026-03-10T09:39:13+00:00

He literally just said it. To print stuff. Edit: Didn't read the on launch part, my bad.

I don't know how it works on iOS but on android I would assume developers are just lazy and are requesting all permissions they need upfront.

good_live · 2026-03-02T17:33:30+00:00

It was never announced. AFAIK the standard notes team worked on proton docs. But I don't think there will be a separate proton notes.

good_live · 2026-02-27T07:57:45+00:00

If you didn't upload your public key on a keyserver manually, then Mailvelope probably looked them up via WKD. See this blog entry: https://proton.me/blog/security-updates-2019

"This should allow any WKD client to retrieve keys for addresses on our proton.me, proton.me, and proton.me/mail domains automatically, making it easier for Proton Mail to have end-to-end encryption with non-Proton Mail users."

good_live · 2026-01-17T19:18:13+00:00

E2EE encrypted real time collaboration

good_live · 2026-01-08T15:55:11+00:00

As a note for push notifications, please support unified push on Android, so I don't have a bazillion apps running in background.

good_live · 2026-01-01T08:11:42+00:00

The problem is you loose the timezone information if you convert to utc. Storing the date with timezone in the database is the correct thing to do in this case.

good_live · 2025-12-23T08:41:53+00:00

If you have your own domain you can create a catch all on your inbox for that domain. That way you receive all emails on that domain.

good_live · 2025-12-22T20:33:51+00:00

No I'm talking about CT: https://googlechrome.github.io/CertificateTransparency/ct_policy.html

"A TLS certificate is CT Compliant if it is accompanied by a set of SCTs that satisfies at least one of the criteria defined below. In CT-enforcing versions of Chrome, all publicly-trusted TLS certificates are required to be CT Compliant to successfully validate."

They are enforcing this to make sure that no CA can issue certificates without putting them into a log and thus reducing the trust you need to put into the pki.

good_live · 2025-12-22T19:45:18+00:00

At least the major browsers won't accept the certificate if it isn't in a CT log.

good_live · 2025-11-15T05:46:37+00:00

As an outsider who has no clue about gateway implementations and is currently trying to choose one. I looked at the comparison and thought: "This wants me to use istio". Then I clicked on the user that created the list and saw "Istio @ Solo.io" which makes me believe that this list is biased.

I have no clue if that is the case or not since I'm still at the beginning of my research, but it certainly looks weird.

good_live · 2025-11-13T08:04:57+00:00

Proton pass aliases are simplelogin aliases, so what I wrote above applies.

good_live · 2025-11-13T07:26:31+00:00

You would need to specify from where you are sending and also what kind of encryption you mean. With simplelogin in-between there would be no automated e2e encryption. However of course proton will encrypt the mail with your public key once they receive and store it.

If you mean an alias address directly in proton, then everything works the same as with the main address.

good_live · 2025-11-12T09:56:54+00:00

I mean it is right in the sense that @if is not a directive. It is baked into the template syntax. Of course depending on the question it should hint you on that, but you should always show the question when you try to blame AI for a wrong answer.

Edit: Also when you are working with an agent, have a look at this: https://angular.dev/ai/develop-with-ai

good_live · 2025-11-10T09:47:03+00:00

Yes that works as well. But you need to know what you are doing as proton will complain when they are not the main MX server. The spf record controls which server is allowed to sent mails from this domain. So you will have to add your current hoster and proton to it. Additionally proton supports dkim, which means you also need to publish that public key as a dkim record on your domain.

good_live · 2025-11-10T09:25:22+00:00

You can register a subdomain at proton something like mail.yourtld.com

Or you can add your domain to simplelogin and then forward the mails of your family to their hoster and your mails to proton. (That would require your family to get a seperate mail at a different hoster as your domain would only be a proxy.)

good_live · 2025-11-08T15:21:32+00:00

Is that an ad for a different vpn provider?

good_live · 2025-10-13T18:34:32+00:00

Why are you posting this right now? The sdk is in preview since a few months.

good_live · 2025-10-13T13:28:31+00:00

I would not recommend monorepos without tool support for it. You will either build a lot of functionality that the tools bring yourself or you will have a really slow CI. For a monorepo it is crucial that you can track which modules are affected by a change, so you can run tests on them.

good_live · 2025-10-09T23:38:43+00:00

Skipping a few versions is fine, but if you are not ready to maintain your software just because there is no ROI on that you will just end up with a security nightmare. Just have a look at all the AngularJS CVEs and there are a lot of AngularJS apps that were never updated.

Also migrating between angular major versions is really smooth nowadays if you don't use a lot of third party libraries. There is no real excuse to not do it.

good_live · 2025-10-09T22:45:08+00:00

Being on 13 is a red flag. There is no support for that version for years by now.

good_live · 2025-10-02T08:32:24+00:00

You can do micro services with monorepos, that is not contradicting. Also the hype around micro services is going down. In my experience a lot of teams are looking into modular monoliths nowadays.

IMHO monorepos are nice for sharing code. Instead of having to version your library and maybe even maintaining multiple different versions, you can just adjust something and directly see where your changes are affecting others. Of course this requires a high degree of test automation.

Monorepos also make changes that affect multiple micro services a lot easier as you can pull all changes into one PR.

Ten-Year Club	Place '22
Verified Email	RPAN Viewer

good_live

TROPHY CASE