398 karma · joined January 7, 2025
It seems like the development team has gotten much more organized in the last couple years, so I have a lot of hope for the future. I think that good open source parametric CAD is something the world really needs.
If electromagnets don't work for DC then what am I supposed to do with this pile of DC solenoids and relays? ;)
> PV Batteries in general have a very high current (100s of A) at ~50Vish volts, so I dont think there's a major usecase for using household breakers for them.
That's what the SCCR rating is for. When there's a fault you're going to have a LOT of current flowing until your safety kicks in. Something like the grid or a battery bank will happily provide thousands of amps almost instantaneously. Breakers designed for protecting building wiring are rated for this. Now, most household breakers aren't dual DC/AC rated, but you can actually buy DC rated breakers that fit in a home panel (Square D QO series).
> Im still not getting your point BTW, switches and breakers are two separate things, with different workings, and household (and datacenter) DC would be I think around 400ish V, which is a bit higher than the peak voltage of AC, but still within the arc limits of household wiring (at least in 230V countries).
My point is that there isn't any material reason why DC can't be as safe as AC, all the proper safety equipment already exists. Extinguishing a DC arc during a fault is a solved problem for equipment at household scale.
> The advantage of DC is that you use your wiring more efficiently as the mean and peak wattage is the same at all times. Going with 48V would mean high resistive losses.
I just mentioned 48V because it's a common equipment voltage for household DC systems. 400V would be good for big motors and resistive heating loads.
Regarding DC vs AC and wiring efficiency, talking about mean vs peak wattage just confuses the issue. 1 volt DC is 1 volt RMS. It is an apples-to-apples comparison. If you want to say "we can use 170VDC or 120VAC with the same insulation withstand rating, and at lower current for the same power", then that is absolutely true. But your common 600V THHN building wire won't care if you're using 400V AC or DC, so it's mostly immaterial.
That is to say, if you misconfigure it, or try to turn it off, you will have an invalid domain until the TTL runs out, and it's really just not worth the headache unless you have a real use case.
The new setup is using uAcme and nsupdate to do DNS-01 challenges. No more fiddling with any issues in the web server config for a particular virtual host, like some errant rewrite rule that prevents access to .well-known/.
https://github.com/ndilieto/uacme
Tiny, simple, reliable. What more can you ask?
https://americanhistory.si.edu/comphist/sj1.html#kids
My point is it's harder to switch from the system you know.
sysctl kern.randompid=1
Oddly enough, not in the sysctl(3) manualhttps://freebsdfoundation.org/end-user-stories/netflix-case-...
But it's still a pretty small market share.
> Two problems remain with the lack of encryption, first is authenticity. Anyone can man-in-the-middle and change the web page, TLS prevents that. But what I think is an even better solution is to do it at the content level: sign the content, like a GPG signature, not the server, this way you can guarantee the authenticity of the content, no matter where you are getting it from.
If your microcontroller can't do TLS then it probably won't do GPG either. But you can still serve HTTP content on port 80 if you need to support plaintext. I believe a lot of package distribution is still over HTTP.
Edit: Sorry, missed the web server part somehow and was thinking of a microcontroller based client.
> In addition, TLS comes with expiring certificates, requiring regular maintenance, you can't just have your server and leave it alone for years, still working. It can also bring back simple caching proxies, great for poor connectivity.
Yeah, TLS and DNS are the two of the biggest hurdles to a completely distributed Internet. Of course you go down that road and you get IPFS, which sounds cool to me, but doesn't seem to have ever taken off.
Same. We've got qmail config files with 2006 as the mtime
As a server OS I find FreeBSD really consistent and easy to administrate. I never have trouble finding things: packages always go in /usr/local. The old-school init system works great at what it's designed to do, and all the startup scripts are easy to understand. The whole thing just feels kind of cozy and familiar. If you like working in a shell then FreeBSD just kind of feels like /home.
Coming from modern Linux though, some of the constructs can feel a bit outdated. Usually this gives me a warm fuzzy feeling, but sometimes it's a real pain (looking at you, make(1)). It's like hacking Perl, once you understand the idiom and what it's good at then you can be good friends.
If you want to run a mail server for 20 years and go through multiple hardware and OS upgrades with minimal pain and maximal uptime then you can't beat it.
That said, for non-core utilities on Linux it's pretty hit-or-miss. The BSDs are generally pretty consistent in what they do offer, and that's what I love about them. Of course it's a different development model and it shows.