There is more to this argument. Adobe made themselves an industry standard with a perpetual license - pay once, own forever. Once they transitioned to a subscription model with a strict cancellation policy, it became the only option.
Saying that designers could have just continued using Photoshop CS on a 2006 MacBook doesn't reflect the reality of hardware updates and the changes in the industry-wide design trends.
The concern is here is clearly not the revocation of licenses.
The cost of not just learning but becoming a professional user of a specific set of tools is very high. Then later as time goes by being forced to either abandon these tools or to accept a different pricing model is - to many people - unfair and unethical.
As mentioned somewhere in this thread, using a custom domain poses other risks, in some cases more significant. All your aliases will be forever tied to your identity (and potentially de-anonymized by a single leak).
> All your aliases will be forever tied to your identity
A separate domain can be used if really needed. But even with using my own domain, I don’t see it as a problem. After all, emails are not anonymous, and a leak with an alias with a custom domain is still meaningless and doesn’t affect other services.
Most domain registrars require providing identity details. Even if these details are private, a single leak or a config mistake on this domain will expose your real identity, tied to all aliases. With an alias service or a shared email provider you don't have this risk as you don't have to provide your real-life identity.
So while it's tempting to use one random alias (h3hj4gjh234@yourdomain.com) for a high-risk service and another alias for a critical service (github@yourdomain.com), these aliases are easily identifiable as belonging to the same person.
It's not in the same category. You can use Firefox Relay as an alias generator within Bitwarden. It provides a convenient UI and an integration with the password manager.
Integration. When signing up with a new web service, you can just pop open Bitwarden and will generate both a unique email alias and a unique password, prefill the sign up form, and save the details to the password manager.
I'm not sure if the comment I replied directly to got deleted or if I accidentally replied to the wrong thread or something, but for some reason I thought I had replied about provenance specifically in response to a comment saying that separate prefixes didn't provide anonymity. Using a custom domain is mostly a fun novelty for me, and if separate prefixes didn't provide any value, I'd still just use use a single prefix on my custom domain because I like it.
I feel like this is a somewhat recent change, so I don't know what happened on my computer or within Protonmail; I have an Intel Macbook Pro, and it really seems to slow everything down. Maybe I screwed up a setting but as I said everything else seems to work fine and when I use the Protonmail Bridge it works fine.
Yes, could potentially be related to a different CPU architecture, but could also be something else eg RAM capacity (I have 64GB) or Proton Mail settings (do you have offline enabled? I don't).
I have 64gb of RAM as well. I don't think I have offline enabled. My CPU is an i9.
I'm happy enough with my Mutt solution, and the iOS app is generally ok, and I do like the service overall, so while I complain it's not out of hatred. I just want the service to get better.
