Regardless of whether you are using a block or an allow list, you have to maintain the list…

I’m not sure what your point is; if you want to devote your time, effort, and potential liabilities to it, that’s up to you. I just figured I would share a perspective on why I didn’t want to do that.

I appreciate all the hard work done by instance hosts; using individual Lemmy instances are a privelege, not a right. I would fully understand and not be upset if my home instance were to shut down at a moments notice.

Sure, but then you’re left with text only and are relying on your blocklist for URLs, which is just going to be a game of whack-a-mole. I personally didn’t want to have to worry about that in my free time, but I’m sure other folks feel differently.

I self hosted a Lemmy instance for a little while, but I stopped over concerns of malicious actors posting CSAM which would then get federated over to my server. I don’t have the appetite to deal with that, and I’m glad I shut it down because just a few weeks later there was a big instance of it happening all over Lemmy, and I’m sure I would have had to deal with cleaning it up on my server too. Just something to keep in mind.

Otherwise though, the setup process isn’t too complex.

Frankly, once you get more than just a few cameras, being able to edit a config file is so much better than having to click through settings for literally hours like with Shinobi or Motioneye.

I’ve personally been quite pleased with the combination of Frigate and some Amcrest POE cameras. Just make sure the cameras you are getting support RTSP though and you should be able to use them with Frigate.

Also make sure you block the cameras from reaching the public internet using your firewall, and only make them reachable from your Frigate host. Personally I use a VLAN with no internet access and enforce tagging at the switch level (i.e. don’t trust the cameras to maintain their own VLAN) settings.

Tt-rss has been reliable for me, and the frontend is decent. Not to mention you can just republish feeds for a different frontend to use.

Yup, that’s true, and I am always open to and looking for new opportunities, but that also requires them to be interested in hiring me - not a trivial feat, especially in the current job market.

I’d also wager that the number of job positions writing OSS for organizations like that is much lower than proprietary job positions.

But you know what, I’ll go shop around a little in my free time the next week or two. I’d love for (more of) my work to be publicly accessible and not locked up in a proprietary codebase.

Yup, as a software dev, I would love to be able to devote all my time to writing open source, but I gotta make money to live as well. Switching to working on OSS would be a huge leap of faith that there is someone out there willing pay/donate for my work. As it is, I think it will be my way of giving back once I have saved up enough money from my proprietary work, and hopefully I will be able to switch over sooner rather than later.

Maybe I’ll go take a look at what the process is for getting grants from the government or non-profit orgs like Apache foundation…

That’s the reason you pass on node? Compared to all the others?