jkaczman

If you're technical, you could probably put together a locally hosted server on your Linux machine and use Tailscale or something like that, it should work fine with the code as-is. Our server binary is in the runtime-binaries zip in the core GitHub release.

Yes they do! Theirs is an IP camera.

Hi muusemuuse, this is meant to be a drop-in replacement to WiFi cameras (and therefore accessible to non-technical users, easy to use and easy to setup). Frigate is great, and we definitely recommend it if you have the time to get it up and running.

In regard to being able to use it without the app, that's not possible unfortunately due to the end-to-end encryption that takes place. An application needs to be on the other end to decrypt things.

Our app is available through Obtainium if you do not like the Play Store. It is also reproducible, so you can verify to make sure it was derived from our mobile_client codebase.

I understand your concern. The way we designed the deployment tool was under the assumption people would be using a freshly-deployed cloud single-use server for it (as we assume they have no technical knowledge).

I'm not sure if a container is foolproof. There have been multiple CVEs in the past allowing processes to escape containers through kernel vulnerabilities. Although, I'm happy to put containers on our to-do list if this will help.

As for what the proper solution should be for advanced users, I personally am not sure. I'd need to research that further. We do try to provide things such as reproducible builds, which means if you build the code yourself using our reproducible build script, they'll match byte-for-byte against our released artifacts. This at least guarantees that it was built from our repository's code, although it does not guarantee the code itself is safe.

I think something that will help here is our planned third-party security audit, which hopefully will be sometime this summer.

Yes, we are working on such a video. I will follow up here once that is ready.

https://mozilla.github.io/cargo-vet/index.html

2.4 "Importing Audits" goes into these third party auditors (the registry).

I can't speak to the account thing, I checked the guy you replied to and it seems like his is 3 months old, not yesterday.

I wanted to mention that we plan to get a third-party security audit by a reputable firm sometime this summer.

Thingino looks like a great option for changing firmware of IP cameras to be open-source, and is useful in local NVR-like setups! Our goal is to different: provide an end-to-end encrypted, easy-to-configure and easy-to-use WiFi camera.

To help mitigate that, we use Cargo.lock files to pin all of our dependencies checksums (integrity validation) until we want to upgrade. When we upgrade, we're working on having Cargo Vet to manually go through (in addition to trusted third party auditors) to ensure the changed code isn't malicious.

We've only tested with a few cameras, and it's able to support that well.

We have work in progress for users. We use OpenMLS for end-to-end encryption and it allows for creating groups. We're using that to allow multiple apps/devices to receive encrypted videos from the camera. We have the core function implemented, but haven't added UI support in the app for it yet.

In theory, that should be possible. We haven't tested it.

We like the Pi because:

• It has a hardware-accelerated H.264 encoder (Broadcom VideoCore IV GPU). This allows video encoding to be off-loaded off the CPU.
• The extra compute allows us to do be able to do higher frame-rates and video quality than an ESP32 is capable of
• We made our motion detection for events more accurate through offering the option of human/pet/vehicle detection, which I don't think ESP32 would be capable of (at least not in terms of the level of accuracy we currently achieve).
• I haven't researched this, but I'm not sure if an ESP32 could handle the end-to-end encryption computation, unless it has a co-processor for it