• 0 Posts
  • 36 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle

  • Sure, they could block based on your VPN provider, but they’re probably also using Deep Packet Inspection .

    The ELI5 verson: It’s possible to just “watch” your traffic and notice that it’s not the “normal” https traffic (which is the most common traffic) . This can be done by finger printing the request itself or just watching the amount of traffic. For example if you “visit” a website, but upload and download 3 megabytes of data and it takes 15 minutes to send/receive that data… well, that looks suspicious… and depending on the country, you may have some people knocking on your door.



  • Since you asked:

    1. The bot provides little “value” vs the noise it creates.

    I don’t need a bot to tell me that the BBC is a legit news source. Maybe if you flip it around and only publish a message if it’s a known scammy website, this might be less spammy. However, this “threshold for scamminess” would be very subjective.

    1. This bot is everywhere. This is closely related to the first point (“value” vs noise). It just sprang up one day and I saw it in every single thread, I’d read.

    Fortunately, most Lemmy clients allow blocking users - which I’ve done and I’m much happier with my Lemmy experience.











  • I’m curious, how would you do this in such a way that it wouldn’t come at the expense of effecting your high availability?

    If the server were on-prem or in the cloud… and the system crashed/rebooted, how would you decrypt (or add the passphrase) to the encrypted drive?.. cause the likehood of the kernel crashing or a reboot after and update is higher than an FBI raid… and it would get tiresome to have the site being down, while we wait for Bob to wake up, log in, and type the passphrase to mount the encrypted hdd.

    You could use something like HashiCorp Vault, but it isn’t perfect either. If the server were rebooted, it could talk to Vault and request the passphrase (automatically) , but this also means that the FBI could also “plug in” the server (at their leisure) and have it re-request the passphrase. … and if Vault were restarted there’s quite a process to unseal (unlock) a vault - so, it would be as cumbersome as needing to type in the passphrase on reboot.

    My point / question is: yes, encryption (conceptually) is easy, but if you look at “the whole life cycle / workflow” - it’s much more complicated and you (as an administrator) might ask yourself “does this complexity improve anything or actually protect my users?”