314 karma · joined September 24, 2014
Unless you've got your own very-very high power transmitters and large dishes, you're not communicating with either Voyager satellite
"Newer" science & research satellites from the late 2000s onward do support a variety of encryption in transit and authentication from the ground stations
And certainly the corporation couldn't be be coerced by the government that's built the largest surveillance apparatus in human history to keep the csam feature running on billions of devices?
Yes, the corporation can be trusted.
/s
- bastille https://bastillebsd.org
- pot https://potluck.honeyguide.net
bastille is great for personal and small setups, pot is aimed at larger scale and meant to be used along with hashicorp nomad+consul
Loss of DNS causes inter-service api calls to fail, then IAM and all other services fail. Anything not built to handle those situations with backoff causes a 'stampeding herd' of failure/retry and exacerbate the outage
Review the AWS statements about outages here - https://aws.amazon.com/premiumsupport/technology/pes/
Run your own alternate frontend - https://github.com/iv-org/invidious
This lets you set regex/wildcard to contain subdomain or redirect happy sites into a single container
https://aws.amazon.com/blogs/aws/firecracker-lightweight-vir...
There's also similar microVM project with a bit more container-focused support called Kata
I thought it was only able to run ARM VMs which can _utilize_ rosetta to run x86 code?
https://developer.apple.com/documentation/virtualization/run...
I've deployed similar, additionally including GKE, via terraform in a day - Checking TF code for an example 3-env GCP/GKE/CloudSQL stack it's less than 300 LoC
That said, it's not all good - my ongoing complaint with terraforming GCP is that the provider lags behind the features & config available in GCP console - worse than the AWS provider - especially w/r/t GKE and CloudSQL
- status boards are rarely up to date, make sure you have your own internal/external monitoring
- a single vm instance does not indicate the health of an entire region. instances can be stopped for a variety of reasons, check the maintenance log and vm console
- when using cloud resources, architecture should not be dependent on a single vm instance
- your cloud architecture and app code should be built to handle transient failures from the start - queueing, retries, backoffs, load-shedding, graceful state failure, etc. use cloud-native services when possible, lift-and-shift of traditional vm architecture to the cloud can be operationally difficult and expensive to run
For a pre-packaged mailserver environment, take a look at mailcow or mailinabox
There's a variety of ansible/chef/puppet up on github that can also be used to setup the invididual component
A filesystem which supports snapshots and rollbacks is good to have underlying your media collection as well (ZFS, BTRFS, etc)
As far as window management, I use contexts for my switcher, rectangle for hotkey-based window management, and stay for automated per-app & per-display window management
There's also alternate window managers for OSX such as Yabai or Amethyst
If you want to dive into postmortems, there are some repos linking other examples
People vote for crap politicians and policies that lead to issues noted in the OP, then go somewhere else and do it again - watching it first-hand in my state over the past decade.
https://www.linkedin.com/pulse/time-say-goodbye-nicolas-m-ch...
This entire system is ripe for false positives AND adversarial attacks.
As mentioned in the twitter thread, how does image hashing & recognition tools such as PhotoDNA handle adversarial attacks?[2][3]
[1] https://news.ycombinator.com/item?id=27959755
[2] https://news.mit.edu/2019/why-did-my-classifier-mistake-turt...
[3] https://towardsdatascience.com/black-box-attacks-on-perceptu...