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.

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 .

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.

Yeah, they're legit. Bought a few servers from them over the years. No major issues, packing was good, reasonable ship time.

Had one case where they sent a different NIC than what was listed. They just shipped me the correct one and told me not to bother sending the old one back.

Stopped buying from them though because I prefer off-the-shelf modern consumer hardware nowadays. The real cost is always power consumption, and I prefer to shell out more money up front in exchange for huge savings on power usage down the line. I can always run over to microcenter and replace a part same-day as opposed to ordering it online and hoping it comes soon.

If you're a home-labber, I'd strongly suggest doing the same. Some of those old enterprise servers just gobble power for not that much compute relative to current day consumer machines.

If I was still buying older servers though, I'd probably be looking at their prices.

What are you considering buying?

I've had a good experience with Onboard.

And that choice is Robin Williams. The man was a gem 🥲

This one is from 1988 (see the right edge, top). Larson already retired from being a cartoonist in 1995.

https://en.wikipedia.org/wiki/The_Far_Side

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.

Spoiler: Roku doesn't either. Immich + a RaspberryPi or other SBC is the way to go...

I bought the whole Steam deck, I'm gonna use the whole Steam Deck!

They have their place. If you only do multicolor prints rarely, but change materials between prints a lot, that's where they excel.

I have both an MMU (Prusa MK3S + MMU 2) and a toolchanger (very custom Voron 2.4 with Tapchanger), and the MMU gets used plenty to swap filament between prints. I look at my toolchanger as being for color prints, and I usually keep 6 colors of PETG on it. My MMU gets used more as the functional printer with all the engineering filaments on it like TPU, PC, ABS, PA. I rarely have to change filament rolls with this setup.

I am also looking at building one of these Swapper3Ds, which should prevent all the waste from printing multiple colors with the MMU.

A better* fork of Gitea!

I get that, that was also something I used to like about old servers, but let me float a few of the things that I've come to realize through my home-lab career to you:

• Raid is perfectly feasible in consumer hardware. If your motherboard doesn't have enough SATA ports, you can always get an HBA or a JBOD to support for more disks. There's really no good reason (that I have heard of) for hardware raid today. Just remember raid is not a backup :)
• There are consumer ATX PSUs with redundancy. However, the only reason for PSU redundancy is when you cannot tolerate downtime due to a PSU or UPS failure, and that redundancy might save you a few hours of uptime over 10+ years in comparison to a non-redundant consumer PSU that you can go out and buy if it fails. When was the last time you had a (reputable) PSU fail on you? What kind of uptime are you targeting? If you don't have an answer for that, 99% is very easy to reach even on consumer gear, and is a strong indicator that you don't need enterprise levels of redundancy. 99% is literally 3 days of downtime per year. Also keep in mind that redundant PSUs are just going to gobble more power and increase operating costs.
• KVM features - this was the big one for me. I wanted to be able to perform out-of-band remote maintenance on my servers. Then I took a leap and got a Sipeed NanoKVM, and I haven't looked back. there are plenty of them out there - PiKVM is another reputable one. When buying old enterprise servers, you often have to pay for the remote management license, and that is just another added cost. Not to mention that they lose support pretty quickly, and you end up running out of date software on one of your most critical interfaces to the machine. A NanoKVM, PiKVM, and others aren't built into the machine, so they continue to be supported for much longer.

One other thing that I'll mention and you probably already know - enterprise servers are LOUD - even just a single one can literally sound like a jet engine. That's not a hyperbolae. If this is your first one, don't underestimate it. I had my servers in the basement with decent insulation, I used IPMI to throttle the fans back to 10%, and I could still hear the whine on my first floor when everything is quiet. If you end up having to turn down the fans due to noise, you're going to start having heat issues, and then you're losing out on performance and shortening component lifespan. Noise-proofing a server is non-trivial - you have to allow air flow still, and where there's air flow, there's a path for noise too. My current setups all have 120mm and 140mm fans, and I can barely hear them when I'm working right next to them. My 3D printers are the loud ones in the basement now!

I tried hosting Gitlab for a while, but configuration and upgrades were difficult, and your really have to stay on top of updates due to vulnerabilities. It also used a lot of resources and wasn't super responsive.

I moved to Forgejo (a hard fork of Gitea), and haven't looked back; I cant recommend it enough. It's fast, doesn't take a lot of resources, actively developed, and has all the features I need.

Codeberg is a public instance of Forgejo if you want to try it out first.

Try brining the turkey overnight before roasting. Keeps the bird nice and moist in my experience.

Yeah, you just need to get the third dimension involved to make it work. Pythagoras would be fine with it.

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

Nice! But good lord some of those corners/lack of slack make me wince - if you have a few feet of slack at the ends, I'd use them 🫣

They don't want to scratch up their desk with the solder joints on the back of it? I'd normally use cardboard, but a towel probably works too 🤷

Or maybe it just has muddy paws that need toweling off 😜

Nice! Just a tip, it would be helpful to mention the size of the pegboard, such as 1" distance with 1/4" holes. There are a few different sizes of pegboard.

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

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