EmbarrassedDrum

thanks I'll take that into consideration!

I'll try giving rsync a try

my internet is just not all that stable or fast. so day I wanna get there (my server) a big file, downloading it and then using ssh to upload it sounds like big trouble. if my connection suddenly shuts, or my computer goes in sleep mode.

So I'm thinking of ways to download directly to my server, without needing to send the files from my laptop.

yes, you're right. my message was unclear, I see now. While I do self host many other things, I just didn't want to take the risk regarding my password manager.

Just the reason why I stopped using Vaultwarden and returned to Bitwarden (EDIT: ditching self hosting the password manager).

I'm not specialized in this, can't update right away, might not know of all security vulnerabilities I have - better leave it for the professionals.

I knew this would be a waste of time! *loads gun

that's not to wear off of the importance of awareness. you should be aware always, even if you don't take action.

Obviously I'm not avoiding it all together, but I'm taking a step in the right direction.

And it's not just replacing Google by CF, because CF has much less access in comparison as I explain.

you can deploy some zero trust models in your setup, and eliminate the threat even further. for example end to end encryption

looks really cool!

mind elaborating?

If I let them handle the TLS for me then I can see that. but if, for example, I'm using NextCloud, which implement end to end encryption from client to server, then I wouldn't care if they did, no?

tl;dr: classic convenience/privacy. depends on your threat model. surely better than Google. models of zero trust will help.

That's a great question, that I have asked myself before too. It doesn't have one answer, and any one would make their own choices based on their own respective threat model. I'll answer you with some of my thoughts, and why I do use their services.

I'll take as an example my usage of NextCloud, coming as a replacement to Google Drive for example.

let's break up the setups:

1. client (mobile app, desktop client, browser)
2. communication to server
3. server

It's oversimplified, but to the point: In Google's setup, you have control of 0 out of three things.

1. you use their closed source client, 2. they decide the communication to the server (if there's any CDN, where their servers located, TLS version), and 3. data is on their servers, wether encrypted or not is up to them.

In NextCloud's setup,

1. The clients are open source (you can varify them, or build your own),
2. communication to server is up to you. and in this case you trust your data with CF, that's right. gonna have to trust them.
3. server is your server, and you encrypt the files how you want.

From just this look, NC is clearly better off. now, it's not perfect, and each one will do their own convenience vs privacy deal and decide their deal.

If you deploy some sort of e2ee, the severity level of CF drops even more, because they're exposed to less data. specifically for NC they do do e2ee, but each solution to its own. https://nextcloud.com/encryption/ this goes as an example for zero trust model. if you handle the encryption yourself (like using an e2ee service), you don't have to trust the medium your data is going through. like the open internet.

gotta admit I haven't read the ToS, but I didn't encounter any problems. I'm streaming GBs of music via the tunnel and it still works. p2p I didn't try, but I don't really see a reason to?

another option is to use Cloudflare's tunnels. it's free, I use it all the time. really great.