Just following up on this, I stumbled on this: https://tuta.com/mailbox

I think it might help. I could definitely see that depending on your use case, Mailbox may be a better choice. I think for general privacy they’re both good, with Tuta having a few “a step above” offerings security-wise but maybe not necessary for most users.

I get it, and please, you do you. There’s no issue.

I’d just add that I can save money using Amazon, but I try to avoid it when I can. I’ll pay a little extra when I can, for the greater good.

I think I’d need some more time to really answer, but on the outset, I find Mailbox.org’s interface more intuitive with more settings and generally feels cleaner and more streamlined. Creating aliases and domain aliases in mailbox seems more proton-like in its simplicity.

Tuta I think is more private and secure, but bits of their interface and app need polish. One reason I think Tuta is more secure despite them both touting security and privacy is that Mailbox search works immediately, whereas Tuta requires you to agree to a permission and states it stores everything locally to you so it may take up space. I think Tuta isn’t doing any server-side indexing of any kind? Unsure.

edit: Mailbox doesn’t have a native app, and Tuta has a native app but I think it’s largely a webview. Notifications work OK but you’ll click on a notification and then have to wait for the app to actually connect and resync before you can view it.

I have two domains, one in each of Tuta and Mailbox. It was originally so I could try both out, but now I figure it doesn’t hurt to keep 'em separated. I’m still new to non-proton so I am sort of still feeling things out.

Nothing really too interesting or tricky about it, just bred out of curiosity.

Since ditching Proton for Tuta and Mailbox…I haven’t missed anything and I’m saving money.

For me, they’re also useful because a lot of my jobs don’t allow remote software to be installed on laptops, so I use something like this to be able to remote in still.

It sounds like maybe they sanitized the apostrophe to a space and then encoded it

I know you’re joking, but semi-related, I highly recommend the Kuhn Rikon peelers.

As someone OE, absolutely.

2 years? More like 3-6 months.

I just died a little inside. Thank you.

In their defense (maybe a stretch) it could be 1-tab indents with a 1-space display?

I’m trying for their sake.

And then I realized it’s python.

That’s what I did locally.

But a lot of this JavaScript wasn’t even transpiled/compiled for prod, just uploaded to a bucket and referenced directly. It was painful.

Typo’d property names when accessing was the biggest one. Assuming a property was one data type instead of another and not casting or handling it appropriately. Accidentally calling something like it’s a method when it isn’t.

I ran a bunch of plugins on my end to help with some of that, but many of the older or stubborn devs refused and would refuse anything but, like, vim with no add-ons.

110% agree. But…

One job I worked at wouldn’t let us do this because it created too large of a QA impact (lol). We were only allowed to modify code in the smallest section possible so that testing could be isolated and go faster.

At another job they mandated that TypeScript wasn’t allowed because it “slowed down development”. It was soooo laughable. The number of bugs introduced that could have been readily caught was absurd, but management never put the two pieces together.

In my defense, the backend contracts change so often in early development the any just made sense at first…

…and then the delivery date was moved up and we all just had to ship it…

…and then half of us got laid off so now there are no resources to go back and fix it…

…rinse, wash, repeat

What would be even more wild is if you edited/replied to yourself and said, “nvm figured it out”…only to later discover it and not remember what you did

Wow those benefits are amazing.

Wait so it’s possible a Senior Dev outside of London would make $35k??