Ah yes, keeping your Lambda functions running, rendering the main benefit of them pointless 🙃

People really should just set up a Fargate task instead…

This process is called ‘bootstrapping’, and is actually quite common in software. For example, the C compiler is written in C. The first iteration of the C compiler was written by hand in assembly code with a very limitted feature set, and that compiler was then used to compile the next iteration, allowing the second version (I’m not sure it was actually the second version; there may have been a few iterations in assembly) to be written in C itself.

For Forgejo, you dont actually need Forgejo to build Forgejo; just a computer with the Go compiler and any other dependencies. Then, once you have the first version, you can publish the code you have on Forgejo. Nothing too crazy there 🙂

This also leads to ‘dogfooding’, which is a whole other term…

Since you’re a bit concerned about self hosting and collaboration, I would recommend Codeberg - they are a non-profit based in Germany with widespread support and, as far as I know, is the public Forgejo instance with the largest user base.

If you want, you can also host your own Forgejo instance and mirror your Codeberg repos to it. That way you can have two copies of your data, just in case Codeberg ever goes offline.

You could also potentially use Gitlab, but I would personally prefer something Forgejo based. Forgejo has been much more responsive/snappier in my opinion; Forgejo is primarily written in Go, while Gitlab is mostly Ruby.

https://forgejo.org/compare-to-gitea/

CI actions and actually being free software are my main notes, but there are many reasons.

A better* fork of Gitea!

IMO, the issue here is that Microsoft appears to have violated the MIT license requiring inclusion of the original author’s copyright notice. I think he has every right to be salty about that violation.

In your analogy, the sign on the furniture says:

Free, but if anyone asks, you got this furniture from <name here>.

Microsoft took the furniture from the curb, but isn’t telling people whom they got it from.

I agree in regards to your opinion that he shouldn’t be complaining about the fact that someone forked his project, that just the nature of the MIT license. However, I do think he is justified in being upset that the license was violated. Hopefully this gets remedied; it’s not hard nor expensive for Microsoft to add his name to the copyright notice in the license.

I have a similar cold brew setup, and I generally don’t let it sit in the fridge for more than a few days. It would probably last up to a week in there though. Definitely don’t let it warm up though; it won’t last more than a day if it’s at room temp.

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.