It seems to be a new feature of Lemmy. I don’t see it using my client, but when using a browser. So it doesn’t seem too to be hard baked into the preview.

Wouldn’t it be suspicious if cameras loose their connection to the system? I guess in that case a technician would be sent out quickly.

Idk if the Flock cameras also scan Bluetooth, but they are the eyes of the system that feeds the database with location data and destroys privacy. By blinding the eyes, its input becomes coarser, its data older, but the previous data is still there.

Usually, there is a limit on the amount of damage that is covered by the mandatory liability insurance (in Germany, at least 1.22 million € for property damage).

Oh dear!

I mean the approach he outlined in his post

Proton today does way more security reviewing than we have done at any time in the past. With the proliferation of AI tools, our code is also under more third party scrutiny than ever before. We see this across the industry, with critical software bugs (like the recent PHP bug) being found on an almost daily basis. However, several extra days of human review is not the correct way to confront this challenge. We still have human review, but now augmented by AI, has become exceptionally good at finding vulnerabilities in code. For some time now, Proton has also been using unaligned models with custom skills to do a thorough review of our code. This approach is better, and also faster.

I.e. AI augmented code review (if I understand that correctly).

What is the problem with that approach?

Kaputt means “broken” or “non-functional” in German, like: Die Tasse von meiner Oma ist mir heruntergefallen. Nun ist sie kaputt. (I dropped my granny’s cup. It’s broken now.)
Here, it looks like the head of the cat is broken off.