Please elaborate. Doesn't the Dropbox client app only have access to the specified Dropbox folder?

I use EncFs folders inside the Dropbox share. All of my content to Dropbox is encrypted. When I have an EncFs share mounted, the raw data becomes available elsewhere on my local filesystem. How would Dropbox have access to my unencrypted data in this case?

I understand that it's much easier (and cheaper) to emulate than to run on original hardware, but emulation doesn't bring the nostalgic factor like original hardware does and to be perfectly honest, it just isn't as cool. Also, half the fun in running old gear is keeping it clean, making repairs as needed and providing all the love necessary to keep things running clean and quiet.

I've been collecting Commodore hardware over the last decade and have quite the Commodore museum for an office. There's nothing more satisfying than writing a daily journal using Pen Pal on an original Amiga 2000 or using Paperback Writer on a Commodore 128 in 80 column mode with a 1802 monitor and 1571 disk drive.

>But why does the key work better than authenticating with a mobile phone?

Because it's trivial for someone to contact your phone provider, pretend they're you and have your phone number ported over to the hacker's device. This gives them SMS 2FA, call-back 2FA, etc.

Best to use a Yubikey and Yubico Authenticator for all 2FA websites that support Google Authenticator.

Not sure if you're trolling or what, but perhaps you have no idea how yubikey works.

https://www.yubico.com/solutio...

I work in the crypto asset space and these types of attacks have been going on for years now. If your 2FA is based on SMS or a call-back, you're doing it very wrong.

For those interested in doing 2FA correctly, buy a yubikey (USB-C if your phone supports) and couple that with Yubico authenticator which is 100% compatible with Google Authenticator. The major difference is that none of your 2FA codes appear until you plug your yubikey into your phone and nothing sensitive is stored on the phone itself. This way, the attacker would physically need your yubikey to authenticate as you - problem solved.

If what you're saying is true, then why has Google been almost the very last email provider to provide email end-to-end encryption?

Because of ads.

This is like saying that once all the gold and silver dries up, we can just switch to bottlecaps. It doesn't work this way. Something is only valuable if people give it value. Sure you can start a new coin, but if people don't give it value then it's worthless.

What gives something value is what people are willing to pay. If people are willing to pay $7000 for a single bitcoin, then that's the value. Just because you don't agree with it doesn't make the value wrong, it just makes the value wrong to you. If enough people think this way, then the value will be driven down by market forces, however that's not what we're seeing here.

It costs approx. $1000 to create a single bitcoin. How much money does it cost for the US Govt to print $100?

>>The government should be allowed to shake me down because I made some risky, but good financial decisions. Keep in mind that I take all the risk.

Make that, shouldn't be allowed to shake me down.

My car registration is my taxes paid for using public roads.
My taxes paid on my income pays for public services (and killing innocent women and children in foreign countries via drone strikes).
I enjoy living in a free country thanks to the actions of me and my military brothers that have fought in wars protecting this country.

The government should be allowed to shake me down because I made some risky, but good financial decisions. Keep in mind that I take all the risk.

>how can it back up your chat history to keep it accessible across all your devices?

That's why you typically scan the QR code between clients, you're sharing your private key across applications. All of your chat history is stored encrypted server-side.

The content would be the same. How the content is rendered, filtered, organized would be handled client side with something like javascript.

two different BBS software on a C-64: HAL9000 and CNET v10 in SoCal from 1983-1986. It started at 300 baud and ended at 1200. It was called The Pirates Galley and later, The Probability Broach. CNET v10 software had lots of basic parts to it, so was highly customizable. For example, the email section was fashioned after the wild west and visiting the old post office. File transfer section was science fiction themed. We only had a few thousand user accounts, but for a single line BBS, that's pretty good. I can still remember the phone number, 805-647-8093. No, don't try it, it's been offline for over 30 years.

I still have the basic portion of the CNET printed out on some dot-matrix printer around here somewhere..good times.

>>You're either being deliberately ignorant, or the point hasn't been made clear to you. I'll try to help.

Here, let me help you.

"Cloud based" password managers (like LastPass) use client side encryption, so even if they get hacked, your passwords are still safe.

Here's the right way to do it. Use a password manager like LastPass, couple that with physical 2FA yubikey and require that both master password and yubikey be present everytime you unlock your computer.