Conversation

Notices

1. Embed this notice
   Blaise Pabón - controlpl4n3 (blaise@hachyderm.io)'s status on Sunday, 24-Nov-2024 07:35:23 JST Blaise Pabón - controlpl4n3

   in reply to

   • Jonathan Kamens

   @jik
   Tahoe-lafs was created (17 years ago) for a similar use case.
   The TL;DR difference is
   1) it breaks content into encrypted blocks and distributes the blocks across some number of storage servers registered with the "grid".
   2) it requires number of participating storage nodes, sort of the way bit torrent does.

   • Embed this notice
     Jonathan Kamens (jik@federate.social)'s status on Sunday, 24-Nov-2024 07:35:25 JST Jonathan Kamens

     in reply to

     I wrote back: "If I were running a trans support org right now, I'd be moving all non-public info and internal org infra onto a NAS in my basement with encrypted drives that require a long passphrase to be entered on boot, with offsite backups syncing to a similar NAS in the basement of another leader of the org. I would not rely on any cloud service to protect my data and my members from harm. The only thing I would put on cloud infra is a public web site that doesn't store any sensitive data."

   • Embed this notice
     Jonathan Kamens (jik@federate.social)'s status on Sunday, 24-Nov-2024 07:35:26 JST Jonathan Kamens

     On a list I'm on, someone asks for advice protecting a small trans support org worried about e.g. keeping their membership list safe.
     Several people respond, "Talk to company <x>, they help non-profits secure infra."
     I look at <x>. Its flagship product automates managing security controls in apps like Google Workspace and Slack.
     I'm like, this isn't going to help when the subpoenas start flying. Y'all need to change your threat model.
     #smdh #infosec #threatModeling #politics #USPol