Hey everyone,
We’ve built an open-source, privacy-preserving alternative to Ring cameras using a Raspberry Pi Zero 2W (called Secluso). It uses end-to-end encryption to send videos from the camera to a mobile app, which is available both in Google Play Store and Apple App Store. We also support Obtainium for people that do not wish to use Google Play.
We’ve put in a lot of effort to make it easy to set up! You can set up our camera on your own Pi in less than 5 minutes with minimal technical expertise using our easy-to-use GUI deploy tool. Here are our setup guide and open source release.
The image shows a Pi in an official Raspberry Pi enclosure that you can use for your camera. We’ve also been working on a HAT for the Pi to add night vision, audio, temperature monitoring for safety, all in a compact form factor. You can see the HAT and an enclosure for the whole camera in the photo.
We’ve been working on this for almost 2 years now, and we look forward to we look forward to seeing what you all think!
From a quick glance at the repo?
The commits generally come hot and heavy. Going back to the earlier 2025 commits and the messages mostly look like what you would expect from folk raw dogging
main. Arrdalan in particular looks “real”-ish. Whereas jkaczman is already showing signs of the kinds of commit messages that claude et al generate, but those ARE based off certain style guides.Roll up to 2026 and I can see 11 commits on May 17 alone, they all look like claude messages, some are outright just arbitrarily changing magic hashes, and there are little to no comments.
Not gonna fully call this ai slop but, it is REAL flipping sus as it were. At best, this is enthusiast code without proper engineering and is immensely unmaintainable. Use at your own risk.
What an amazing conclusion, and the best part is, no matter what you’ve been waffling about before - it’s always right. Can we stop calling random things AI slop and telling to be careful bEcAuSe iTs Ai sLoP, and back to being cautious until something has been reviewed properly? Being careful with random stuff from GitHub you install and run in your private network?
Your whole comment may have been AI slop as well. “From a quick glance at the repo”, you should be careful! Thanks, Sherlock.
Those 11 commits were from a rebase-and-merge PR, which changes the date from the original commit. Notice how there’s a week gap between those and the prior commits on the main branch.
The only thing AI is used on in this project is strictly for user interface work (our website, the front-end for the mobile app, the front-end for the deploy tool). We carefully vet anything like that.
Fair enough. I’ll still say that is bad engineering but acknowledge that starts to get into the realm of taste.
Either way, in the past 24 days you have MR commits on 8 of those and April looks similar. The code is generally poorly documented and skimming the closed MRs, I am not seeing much discussion or review in any of them. So I stand by
Fair points. I appreciate the constructive criticism! Moving forward, we will improve on our documentation. In terms of review, we always review and test each other’s code (sometimes via other mode of communication), even if there weren’t any comments on the pull request.