It sounds like a more realistic motivation for that would be to reduce the risk of failure- if the primary team flubbed the project, the secondary team would still be an option. (Such a system would also give you an opportunity to judge how effective either team was.)
Awful thing to do to engineers, but you can understand why management would do it and why they wouldn't want to demoralize the secondary team by telling them.
Rate limits, feedback loops, and we scan outgoing mail through SpamAssassin. In practice we've only had password breaches causing spam, nothing intentional.
> 1. I don't know if it's the social media kiss of death at work, but I'm getting lots of SSL errors trying to load your site. It's a crap-shoot whether it works or not right now.
Hard to say for sure. None of the servers really went above 15% average CPU and I don't think they maxed out net, and the health checker for HTTPS didn't have any problems. I'll doublecheck.
On the subject of migration, I'll make a note to add a FAQ for that, thanks.
Hm, no idea what would've gone wrong in your case. It sounds like something kept closing the websocket used to provide page interactivity or something?
For the trial hashwall, the browser just does some heavy computations. I guess I should add a warning there, it's probably does have battery impact if you're using a phone for whatever reason.
I'll make a note on the UI elements. Honestly hadn't thought about the punycode usecase, good catch.
The E2E will help so long as you're sending email to other users of the same service, yeah. For most cases, it's probably not a huge upgrade from stored encrypted; the bulk of damage in email leaks would be from accumulated emails from the past.
The reason I don't recommend using it if you're super paranoid is because it'd be easy to mess up, and it comes with quite significant holes- e.g. subjects aren't E2E in Protonmail. Best to use a protocol designed for E2E from the ground up.
Marketing emails are actually against the terms of service, although there are grey areas- like a user personally reaches out to offer people a service, and some occasionally end up marked as spam. If the rate is low enough, it might be acceptable.
Yea, they say as much in the data privacy FAQ. I think my recommendation is that if you're worried about being explicitly targeted by state actors, don't use email. (Not even Protonmail.)
If you're worried about general data hoovering, AWS would probably need to implement very sophisticated introspection into what your machines are doing to break the SSL on SMTPS, and courts might not be sympathetic to that. I expect state actors would find it easier and more convenient to just hoover from big providers like Gmail instead.
You can have as many domains/users as you want. (Unless it's like five billion and breaks the service or something.)
Generally phone access is third party through IMAP. On Android I personally use K-9 mail, but you can use anything that supports IMAP anywhere, which is a pretty good number of options for any platform.
> Accounting for inflation, house prices have soared by 118% since 1965, despite the fact that income has only increased by 15%.
They use the median for that, which seems to have actually increased by 60%:
https://web.stanford.edu/class/polisci120a/immigration/Media...
I'm not sure why nobody else seems to have brought this up- it's a serious flaw in the article.