Even 50W, 24/7, is 36 kWh/month. $3 where I live; $12 in CA.

My Pi spends all of its time around 55°C in a 20-25°C room. Main server idles at 47°C. Those aren’t worrying temps.

I’ve watched enough Lock Picking Lawyer never to want a consumer ‘smart lock.’ Half of them can be opened with a magnet. Maybe commercial grade is better, but I’ve been locked out of my job after every power failure for the last 10 years, until someone comes along with a physical key.

Re homeassistant on a Pi: homeassistant does a lot of database transactions, so you may want to have db storage on something other than an SD card.

At the time, it was part of the whole poisonous structure of the 2017 tax bill, where everything would expire after Trump’s presumed 2nd term to sabotage his Democratic successor, confident that no one has long enough memory to realize where it came from.

You can only spin drives down if they’re idle. If you have a service that touches it - say, homeassistant logging data, tvheadend updating EPG - then they’re going to keep spinning.

I switched from an I3-530, nominal TDP 73W, to an N-100, nominal TDP 7W, and power from the wall didn’t change at all. Even the i3 ran around 0.1 CPU load, except when transcoding, and I’m left with the impression that most of the power goes into HDDs, RAM, maybe fans, and PS losses. My sense is that the best way to decrease homelab power use is to minimize the number of devices. Start with your seyrver at 60W, add a WAP at 10-15W, maybe a switch at 10-15W… Not because of the CPUs, necessarily, but because every CPU every CPU comes with systems to keep the CPU going, keep the power regulated, etc.

It’s from a Molly White doot. I don’t see it on her website https://www.citationneeded.news/ but she’s definitely been all over Trump’s crypto.

I’m not a huge docker expert, but I recently spun up a tandoor…dev, and their config instructions explicitly point out a couple of mounts that have to be volumes and can not be binds.

Docker’s own comments are https://docs.docker.com/engine/storage/volumes/ which my tl;dr is faster, can be shared by multiple containers, and can be a remote (NFS/CIFS) target.

I’d guess that maintainers use the volume structure to let docker handle the details of creating and maintaining the mount, rather than put it on the user, who may be spinning up their first-ever docker and may make all kind of naive mistakes.

The reason for his post was that a provider shut down his access on the accusation of CSAM, without (according to him) much if any investigation. Cloud providers have all manner of automated systems for reporting CSAM, copyright, and other potential abuses, and generally seem to take a guilty-until-proven-innocent approach. They may or may not even be responsive to defense or explanation. Colo isolates you from abuse of those systems.

My ISP seems to use just normal DHCP for assigning addresses and honors re-use requests. The only times my IP addresses have changed has been I’ve changed the MAC or UUID that connects. I’ve been off-line for a week, come back, and been given the same address. Both IPv4 and v6.

If one really wants their home systems to be publicly accessible, it’s easy enough to get a cheap vanity domain and point it at whatever address. rDNS won’t work, which would probably interfere with email, but most services don’t really need it. It’s a bit more complicated to detect when your IP changes and script a DNS update, but certainly do-able, if (like OP) one is hell bent on avoiding any off-site hardware.

Daniel Stenberg claims that the curl bug reporting system is effectively DDOSed by AI wrongly reporting various issues. Doesn’t seem like a good feature in a code auditor.

I, for one, would rather just see them use a couple of 2/0 AWG welding cables, bolted onto a 5mm copper plate on the board. If you need 200 amps, make it look like 200 amps.

The UPS needs some power to keep its batteries full. Could be that it’s triggering off some threshold to do a charge cycle instead of just running a constant trickle. I’ve noticed that my laptop and phone charge that way, for example.

…hanging from their cables…

It really depends on what your data is and how hard it would be to recreate. I keep a spare HD in a $40/year bank box & rotate it every 3 months. Most of the content is media - pictures, movies, music. Financial records would be annoying to recreate, but if there’s a big enough disaster to force me to go to the off-site backups, I think that’ll be the least of my troubles. Some data logging has a replica database on a VPS.

My upload speed is terrible, so I don’t want to put a media library in the cloud. If I did any important daily content creation, I’d probably keep that mirrored offsite with rsync, but I feel like the spirit of an offsite backup is offline and asynchronous, so things like ransomware don’t destroy your backups, too.

With only 15U, assuming devices don’t stick out the back, I’d move it face-up, so devices are more hanging from their ears than cantilevered. A full, 42/48U rack is extremely top-heavy and tipping during move is a serious risk, but 15U is fine. It’s still very dense, and OP should try to ratchet-strap it to hard points in the trailer.

There are still “favors” to be done.

My thought exactly. OTOH, I feel like the anti-Musk ball only really got rolling in March, and this report can’t possibly cover March - it’s got to be Dec24-Feb25, so probably just a hint of things to come.

It kind of amazes me that, in this day and age, email has turned out to be the lynchpin of security. Email as a 2FA endpoint. Email password reset systems. If email is compromised, everything else falls. They used to tell us not to put anything in email that you wouldn’t put on a postcard…how did this happen?

Wonder if there’s an opportunity there. Some way to archive one’s self-hosted, public-facing content, either as a static VM or, like archive.org, just the static content of URLs. I’m imagining a service one’s heirs could contract to crawl the site, save it all somewhere, and take care of permanent maintenance, renewing domains, etc. Ought to be cheap enough to maintain the content; presumably low traffic in most cases. Set up an endowment-type fee structure to pay for perpetual domain reg.