> how can e-mail ever be a secure medium

Email can be secure, it’s just that the big US players can’t or won’t agree to proton like privacy.

I am curious to know what is behind these big US companies being so anti privacy.

I hate the idea of making things a tiny bit more difficult for beginner developers, but what is the alternative?

It would in fact be negligent if the police did not properly investigate the server/computer/house of the device.

I’m all for code reuse but Serde for json is a bit of a dogs breakfast when it comes to dependencies. all you need is an exploit in on of those dependencies and half of the rust ecosystem is vulnerable.

Rust should have Jason built in.

You need to lean all in on either the “he’s a toxic male” narrative or the “woke leftists are ruining everything” narrative for your website to make money.

The answer to this is to argue that it’s incorrect to take an overall statistic and apply it to an individual or smaller organisation in that group.

“Not all bugs can be found until you deploy to production. So deploying to production can be called ‘testing in production’”

In these types of situations I’ve been in, usually the developers already complained, and it’s really not the fault of the developers.

This creates this weird situation where developers have to do more and more to protect themselves from situations like this.

It doesn’t take more than a few seconds of thinking to realise that google should have made some kind of way for authentication to be transitioned over. Even something as simple as sending out a “transfer” email link or even just an api that squat space could have called to allow customer transfer verification.

When it’s just a random staff member complaining they want to do something that makes it harder to onboard customers, there’s no proof of incompetence, and incompetence can still be blamed on the developers.