I subconsciously tried wiping my screen.

Forums are an invaluable source of information for countless purposes. Even extremely old forum posts can be a life-saver.

I think it’s time to close some of your open tabs.

Y’all don’t update your services?

FYI, you can edit post titles directly. You don’t need to put an “edit” in the description.

It would put the more popular instances under enormous stress, if they had to serve every single subscriber from any other instance.

From what I understand, media (images, videos, etc.) is not cached. Does that not mean that, in the worst case where every post contained an image, the instance would be serving every subscriber, anyways?

The data in that graph doesn’t show what your title is inferring. For one, the y-axis is relative, and not absolute. Secondly, your data range is set to the past week so this says nothing about how this method of searching is trending over any useful period of time.

I don’t really understand this reasoning. Some server would still need to receive those requests at some point. Would it not be better if those requests were distributed, rather than pounded onto one server? If you have a server caching all the content for its users, then all of its users are sending all of those requests for content to that one single server. If users fetched content from their source servers, then the load would be distributed. The only real difference that I can think of is that the speed of post retreival. Even then, though, that could be flawed, as perhaps the source server is faster than one’s host server.

Please correct me if I am wrong, but this feels like a flaw with how Lemmy (perhaps other fediverse apps as well, I’m not sure) is designed. Why do I need to store all posts made to a community that one of the users on my instance subscribes to? Would it not be better to simply store my user’s posts, and comments, and the posts made to any communities hosted on my instance? Why do I need to store information from other instances, and users?

it is storage that requires more attention

Please correct me if I am wrong, but this feels like a flaw with how Lemmy (perhaps other fediverse apps as well, I’m not sure) is designed. Why do I need to store all posts made to a community that one of the users on my instance subscribes to? Would it not be better to simply store my user’s posts, and comments, and the posts made to any communities hosted on my instance? Why do I need to store information from other instances, and users?

If you single tap on a comment it closes the chain.

Next time I would post on !homelab@lemmy.ml

Thank you for letting me know!

Thanks a bunch for that link! That’s a really useful resource!

Ah, sorry about that. That’s why I mentioned the 3rd paragraph in my post; I wasn’t sure if this was the correct place for this post - I wasn’t sure where else to go.

you could use a lower quality stream (…) for motion detection, then use that to trigger recording on a higher quality stream.

Brilliant idea! Thank you for the suggestion!

If doing CPU-based motion analysis

Whyd do you specifically mention CPU-based motion analysis? Does this idea not work with the Google Coral TPU, for example?

The ram cache with help with speed and reliability

Are you inferring that the torrents would be stored in ram? That would not be feesible with large amounts of data.

Just out of curiosity, why are you setting up a seedbox in a enterprise environment?

What do you mean? What enterprise environment?

That’s quite a few cameras. I would do an audit on how many you will actually need first, because you will likely find you could get by with 5-10.

That’s a fair point. I haven’t actually methodically gone through to see exactly how many I would need just yet. The numbers that I chose were somewhat just ballpark off the top of my head.

You will also want some form of reliable storage for your clips

I am planning to give the camera server dedicated storage for the data. If I’m really feeling like splurging on it, I may look into getting WD Purple drives, or the like.

as well as the ability to back up those clips/shots to the cloud somewhere.

I’m not sure that I would need this very much. I’m mostly interested in a sort of ephemeral surveilance system; I only really need to store, at most, a few days, and then rewrite over it all.

I’m personally running 4 cameras (3x1080 @ 15fps, 1x4k @ 25fps) through my ~7 year old Synology DS418play NAS

Would you say that 15FPS is a good framerate for surveilance? Or could one get away with even less to lessen the resource requirements?

whereas I can tweak stuff on Surveillance Station quite easily.

What tweaking do you generally need to do for the camera server?

The space requirements get super intense with many cameras like that unless you compress the video.

I think Frigate uses h264 if I remember correctly. Also I’m not planning on storing and archiving the recorded data. I most likely would only save a day or a couple days. You do raise a good point about vacations, though - I should probably have enough storage for possible vacations.

Also if the cameras don’t encode then the data flow would congest your network something fierce.

The newtork that the camera feeds would be flowing through would essentially be isolated from the rest of the network. I intend to hook the cameras up to a dedicated network switch, which would then be connected to the camera server.

The biggest issue as I see it with so many cameras would be how to find interesting stuff in all that data.

What’s nitce about Frigate, is that it uses OpenCV, and TensorFlow to analyze the video streams for moving objects.

More Information can be found on Frigate’s website.

Spinning up and spinning down the disk technically always comes with the risk of the drive damaging because of the physical components involved

Ideally, the seebox would maintain a 100% uptime.

Constant writes would definitely be far harder on it

Would there be a difference for constant reads (reading is what the seedbox would primarily be doing)?

I don’t know, but ideally that data would be cached in RAM.

Not feesible, unfortunately, if we are talking about multiple terabytes of data.

Maybe if you used intelligent tiered storage with a flash tier it could reduce wear and access times.

Could you clarify what you mean?

A surveillance camera PVR is writing 24/7 which is more intense, and those drives still last plenty long.

That’s a fair point; however, I have seen special hard drives exactly for this purpose.