this post was submitted on 24 May 2026
724 points (98.4% liked)

Selfhosted

56958 readers
1271 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

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!

you are viewing a single comment's thread
view the rest of the comments
[–] jkaczman@lemmy.zip 27 points 1 day ago* (last edited 1 day ago) (1 children)

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.

[–] NuXCOM_90Percent@lemmy.zip 0 points 1 day ago (1 children)

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

At best, this is enthusiast code without proper engineering and is immensely unmaintainable. Use at your own risk.

[–] jkaczman@lemmy.zip 16 points 1 day ago

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.