eldridgea

This answer might be US specific but one significant reason for the pushback (at least from me) is the centralizing force.

Generally the things cameras like that are good for enforcing are handled by local law enforcement. Probably at the city/county level, at most the state. So prior to Flock and their ilk, camera surveillance was used by local people in the community to enforce laws enacted by the community.

Flock enables that but also provides a nation wide, searchable database available to local and federal law enforcement. Recently SCOTUS ruled that broad geo-based warrants (law enforcement would ask Google for all devices in an area for a time frame) are illegal and overbroad.

A nationwide Flock network with facial recognition ends up in the same place of being able not only to enforce laws, but track people in a warrantless way.

Conceptually at least, this feels very similar to government attacks on encryption where a government wants to see and have access to everything without cause just in case, which is definitely at least in sprint opposed to the right of free association. Flock does the same kind of thing but in the physical world.

I also think a general computer security rule of thumb probably applies here, where for the best security/safety, trust should be provable. If trusting a human is required to make a system work correctly, the system is flawed.

All of that to say I don't think the majority of pushback is against enforcing laws by camera specifically, but a Panopticon-ness of it and all the downstream effects that causes.

Thank you!

I believe it strips everything after a "+" so you can use [email protected].

It ignores periods so you could also use [email protected] or [email protected] or whatever.

Some sides block plus addressing but that's what I use a lot of the time.

~2019 I led a team of highly qualified security R&D folks inside Cisco (we were part of an acquisition), these folks were effectively highly specialized SWEs. But because the title was something like "security researcher" it was compared against the closet Radform ladder which was closer to to compliance officer.

This meant the specialists were on a ladder with often lower pay than a standard SWE, and I couldn't shift the bureaucracy enough to change that. People left for all sorts of reasons but a big part was being able to get 2x-4x the total compensation at other companies.

I use a single node microk8s instance mainly so I can stay familiar with syntax and things for work rather than an actual high availability system.

But I use Portainer and store my files on Github so Portainer can auto-update a deployment if I submit a code change, so kind of rudimentary CI/CD which could be fleshed out more with some GitHub Actions probably.

I use iSCSI mounted storage from my NAS on the host and k8s volumes storing configs there. Actual app data is on the NAS accessed via NFS from the relevant apps.

So a new deployment is usually test locally on my laptop, once it's good commit the code to github and either let the deployment auto update or go to Portainer and do it manually if it's a new deployment. Ingress traffic is done via Cloudflare Tunnels deployed in k8s.

I keep most apps in a single namespace called prod unless they need more than 1-2 pods. If I was doing this again I'd use a namespace per app, I do use a dedicated namespace for anything with a Helm deployment or needs a lot of pods (e.g. Immich)