You will not like this answer:
An old 11” macbook air or the 12” macbook circa ‘17.
They’re everywhere, last forever, parts are cheap, they’re durable, there is good Linux support, the screens are good and they don’t stick out when you’re using them in public.
I used to have 11” as my hard upper limit of diagonal size years ago but since then I realized it’s no big deal to carry a 13” diagonal computer now that they’re all incredibly thin and light.
YOU SHOULD NOT RUN YOUR CAMERA SERVER ON YOUR DOCKERPILE HOMELAB BOX THATS HOSTING 69 DIFFERENT THINGS!
If you have the time to set it up, learn the different use cases of cameras and monitor it for failure somehow then frigate is good.
If you’re using ip cameras you 100% no foolin without question have to put them on a vlan at the very least. They are an insane liability when it comes to network security.
If I had it all to do over again I’d have done power over ethernet, put them all on their own switch that does poe injection and done vlan by the one phy going from the poe switch to the router.
People will fight me about this, but ip cameras are all pretty much the same. They make available some video stream at a preset bitrate and resolution, use built in infrared or visible lighting and offer pan, tilt and zoom (ptz) controls to authorized users. Some have motion detection and object recognition on device which may or may not be surfaced to the camera server.
I always offload object detection and classification to the server even if the camera has it on board because even on cpu image inference is “okay” and with an old gt750 nvidia card you can do much faster object detection and classification. The reason for doing it all on server is in order to get consistent results.
If you are a computer savvy person: congratulations, you picked a project that uses memory, gpu and disk space at a time when they’re all at a premium! Hell yeah!
YOU SHOULD NOT RUN YOUR CAMERA SERVER ON YOUR DOCKERPILE HOMELAB BOX THATS HOSTING 69 DIFFERENT THINGS!
Fortunately you don’t need ddr5 for this so any old server is fine. Scale your ram needs up or down depending on the cameras you’re looking for.
Consider buying one of those ten year old servers with redundant power supplies. Even if they’re both connected to the same ups (and you need the camera server on it’s own ups) you can keep going when one dies.
There are two minds regarding disks in surveillance servers. The first is “fuck it, kill the disks, who cares, they’re a wear part!” The second is “no, careful management of our disks will ensure trouble free use for years to come.” I’m of the second variety and run a zpool of small (<2tb) disks with an optane cache. The cache saves the disks from some of the drive killing random writes and reads and lets me keep running at speed when reviewing things.
When you go to put in an old gpu, make sure the plastic cowling shaped like an anime titty isn’t too big otherwise the pcie standard sized spaces in most servers won’t be able to take it.
YOU SHOULD NOT RUN YOUR CAMERA SERVER ON YOUR DOCKERPILE HOMELAB BOX THATS HOSTING 69 DIFFERENT THINGS!
I have been robbed and had to hand camera data over to the cops and can offer you some more practical advice if you’re open to it.
No it’s because there isn’t any description or additional context.
If I wanted to watch youtubes based on their titles and thumbnails I’d click on the address bar of my browser, type “youtube.com”, press enter and do it myself.
The party isn’t properly alt right in any way that an anglosphere dweller would recognize.
It’s not a bad sign for the company in any way. Remember that mullvad was the vpn of choice for pedophiles distributing csam until it wasn’t.
Mullvads recent statement is also extremely carefully worded to avoid taking what the state would call a political stance. While we may recognize that not condemning the donor is political, what the state considers political is support or detraction from some party or of some speech. If mullvad were to make such a political statement it could be subject to a whole different kind of law.
They use networking software that’s optimized for speed and low resource use (you’d rather be spending those arm/esp cycles handling video, right?) with a slow patch cycle and little chance the user (you!) will actually get up on a ladder and install the damn patches.
Some of them will dial out and try to get their patches, but did it work? Are they still running right after the patch? You don’t know that because you don’t even know they got a patch notification, dialed out, downloaded and installed it, silently changed a default or removed a resolution you relied on and aren’t sending video anymore! Do you even want them doing that?
Even if they weren’t doing all that, there are hundreds of vulnerabilities that allow a user on the local network to silently bypass auth and view them, change settings etc.
The above isn’t because they’re crappy (they are crappy.) but because they’re using some weird .005$ cheaper esp32 variant that needs a modified binary which isnt on anyone’s radar and had support dropped 2 years ago.
I have even run into modern ip cameras that would try to proxy their feed on a public facing ip that used to be owned by the (now defunct) manufacturer but is now some weirdo just slurping up what gets sent to them.
The simple solution is to put them on a derek zoolander vlan for network devices that can’t network good, cut em off from the outside world and check for updates manually.