Since Andy Yen's unfortunate comments, have any of you left Proton? And if so, what alternative did you choose?
Since Andy Yen's unfortunate comments, have any of you left Proton? And if so, what alternative did you choose?
cross-posted from: https://lemmy.ml/post/25445621
How did the transition go? Do you like the new service(s) so far?
You're viewing a single thread.
I left and glad I did. It was a needed wake-up call. All-in-one is inherently risky. I'd rather support smaller, more focused products. If one doesn't fit my needs down the line, it's way easier to switch.
- Email: Tuta (meh, loading issues)
- Calendar: Tuta (don't like, can't handle recurring events)
- VPN: Mullvad (like)
- Drive: Tresorit (like)
- Passwords: already using Bitwarden (love)
My struggle is finding an alternative to nonesense email alias system proton provides. Tuta and everyone else seems ridiculously limited with aliases. Like, I'll use my own custom domain idgaf, just gimme infinite aliases...
Based on my understanding, Tuta is better for aliases compared to Proton. Their alias limit doesn't apply to custom domains, only the domains they own (tuta.com, tutamail.com, tuta.io, tutanota.com, tutanota.de, keemail.me)
If you have proton pass you can generate random or semi random aliases. I don't believe there's a limit to this. Good to know on the tuta side though.
Oh I see. That makes sense. I think Bitwarden can be hooked up to alias providers but I've never tried that myself
I hadn't thought of that, might have to look into that. That would be great for new accounts. I basically only used proton pass to create aliases and stored it all in bitwarden anyway.
Same stack as me except KeePass for PW manager. I’ve actually been enjoying Tuta though. What issues are you having with recurring?
External calendars I've imported have a bunch of events on the wrong days. I reported the issue and here's what they told me:
It seems like some events in your .ics file use advanced repetition rules which are not supported in the Tuta calendar yet. We are currently working on this to improve compatibility and hope to release them soon so the calendar should be imported correctly.
I know it's a small development team, but it's a little frustrating. A calendar service supporting only a subset of the ICS standard is silly in my opinion
Ah shoot. I guess that makes sense that it might not match 1:1 if it's using some advanced recurrence rules. When I exported from Proton and imported to Tuta, I did it as a CSV and needed to modify the columns a bit to get it to import, but my recurring appointments seemed to have come over fine. They are fairly simple though.