Viewing profile — arrdalan

Our on-device AI is able to detect people, pets, and vehicles. We have tested people detection and it works well. We haven't really tested the other two.

Will do. Thanks for the suggestion.

ESP32: We haven't tested them. I would guess that they won't be able to handle the workload (on-device AI, encryption, and video encoding if there's no hardware encoder). Ciphersui…

There are two comments/questions here and I'll try to address them one by one. Secluso vs. Frigate: I think you correctly mentioned some of the differences. We intend Secluso to be…

The videos are stored in the mobile app and you can view them when you need. The camera captures videos when it detects an event, e.g., a person, encrypts them, and sends them to t…

The camera_hub runs in the camera. It records videos, encrypts them, and sends them to the mobile app. The server is a relay in the cloud. It transfers encrypted videos from the ca…

Hey everyone, I previously introduced an open source private home security camera in 2024, which uses OpenMLS for end-to-end encryption: https://news.ycombinator.com/item?id=422844…

One can use Frigate + Home Assistant + some secure remote access solution (e.g., VPN) to get a usage model similar to Secluso. Secluso however provides the following advantages: 1)…

There are several differences. 1) Usage model: RTSP cameras can be used for on-demand livestreaming. In contrast, the usage model of our camera is similar to a Ring camera: not onl…

Several months ago, I posted in Show HN ( https://news.ycombinator.com/item?id=42284412 ) about this project (previously named Privastead, now changed to Secluso). It's a privacy-p…

Yes, we have different approaches/designs. In fact, I don't even of think of Privastead as an NVR solution. The choice of using a hub is mainly because I didn't have control of the…

I have mentioned the unencrypted traffic between the camera and hub here: https://github.com/privastead/privastead/blob/main/HOW_TO.md (Step 4, second paragraph)

Privastead/OpenMLS erases past keys from persistent storage in order not to suffer from the vulnerability you mentioned.

Interesting. I think the usage model provided by Privastead is reliable enough (at least for me). I have access to my videos on my phone. If losing the phone is a concern (which sh…

The end-to-end encryption part is clear IMO: it's between the hub and the app, both of which are trusted. This is different from an untrusted server decrypting the messages.

Sorry, which question did I miss?

This is a reasonable setup. We discussed it in other comments as well

Correct, that would be even better, but I didn't have control over the camera firmware. Someone mentioned OpenMiko, which I plan to investigate and see if it can allow me to effect…

I haven't designed Privastead for continuous recording/streaming. It's mainly to receive motion/event-triggered videos and occasional live streaming. The usage model is more like R…

The server only stores encrypted videos until they're fetched by the app. It can't decrypt the videos and hence is not meant as a storage space for decrypted videos.

That is correct. The goal is to be able to use the cloud to host the server without having to trust it. I personally use a cheap DigitalOcean VM.

Thanks for the pointers. Frigate, Home Assistant, and HomeKit were mentioned in other comments and we had some discussions there. They're certainly good setups. A key design decisi…

I did not, but I will. I would just point out that Privastead assumes the the push notification infrastructure is untrusted anyway.

Push notifications are for notifying the apps of events (e.g., motion). The actual encrypted video (either motion-triggered video or livestreams) are transferred through the server…