EmbarrassedDrum

@EmbarrassedDrum@lemmy.dbzer0.com

• ⁨Comment⁩ on ⁨Typing monkey would be unable to produce 'Hamlet' within the lifetime of the universe, study finds⁩ ⁨⁨1⁩ ⁨week⁩ ago⁩:

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

• ⁨Comment⁩ on ⁨Ditching the VPN and port forwarding the selfhosted way⁩ ⁨⁨2⁩ ⁨weeks⁩ ago⁩:

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

• ⁨Comment⁩ on ⁨Ditching the VPN and port forwarding the selfhosted way⁩ ⁨⁨2⁩ ⁨weeks⁩ ago⁩:

  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

• ⁨Comment⁩ on ⁨NextCloudTalkAutomationBot: A powerful and flexible bot for sending system notifications through messages via Nextcloud Talk.⁩ ⁨⁨2⁩ ⁨weeks⁩ ago⁩:

  looks really cool!

• ⁨Comment⁩ on ⁨Ditching the VPN and port forwarding the selfhosted way⁩ ⁨⁨2⁩ ⁨weeks⁩ ago⁩:

  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?

• ⁨Comment⁩ on ⁨Ditching the VPN and port forwarding the selfhosted way⁩ ⁨⁨2⁩ ⁨weeks⁩ ago⁩:

  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. 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.

• ⁨Comment⁩ on ⁨Ditching the VPN and port forwarding the selfhosted way⁩ ⁨⁨2⁩ ⁨weeks⁩ ago⁩:

  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?

• ⁨Comment⁩ on ⁨Ditching the VPN and port forwarding the selfhosted way⁩ ⁨⁨2⁩ ⁨weeks⁩ ago⁩:

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

• ⁨Comment⁩ on ⁨Antman - Android Tab Manager⁩ ⁨⁨2⁩ ⁨weeks⁩ ago⁩:

  yeah that’s very odd…