93 karma · joined November 9, 2016
The Outlook .pst file plays notoriously bad with backup and synching in my experience. I set up CrashPlan for a family member once, and when I followed up a few weeks later it hadn't backed anything up in weeks because it was stuck on the .pst. In this case it was because the .pst was so huge and kept changing so frequently. By the time it had been uploaded for off-site backup, then it had changed and CrashPlan would start uploading it again. CrashPlan wasn't smart enough to prioritize other files in between, probably because it puts the most recently changed files in front of the queue or something.
[1] https://www.tekna.no/en/salary-and-negotiations/salary-stati...
If I am supposed to make $1m more at Public Company over -- say -- a 10 year period, then that means my salary at Public Company would have to be $100k more per year than at Startup Company. Is the difference between startup and public really that big?
The downsides I can think of in that case are an attacker attempting to log in at the same time, or -- more generally -- a user thoughtlessly clicking the link when an attacker is trying to log in.
The first problem can be addressed by displaying a second readable token on the login screen which the user should verify is present in the email before they click the link. That is how banks and other high security systems do it here in Norway now when you select authentication via mobile, except they use some sort of mobile communication tied to the sim card instead of email. You get a popup on your phone containing two random words from a dictionary. You confirm that the words match what the browser is currently displaying and then tap "OK".
The second problem can probably be reduced by short token timeouts and using appropriate language in the email to emphasize the implication of clicking the link uncritically.
require('forecast/jitter').get = function(){return 0;}