• 3 Posts
  • 208 Comments
Joined 4 months ago
cake
Cake day: June 9th, 2024

help-circle




  • Are you talking about disconnecting power entirely, or just generating as much as possible yourself?

    Because the first, depending on local laws, is going to be something you can’t necessarily do and keep your occupancy permit and be allowed to stay living in the house.

    The other is going to be a matter of figuring out your maximum power requirements and sizing a solar and battery system big enough to fill your needs.

    Just as a thing to consider: you’re talking tens and tens of thousands of hardware if your power bill is $300 a month, and the ROI on this is going to be 10 or 20 years, so if you’re not living there that long, it’s maybe not worth doing.

    Do the math on how much power you use at peak draw, how much power you use in a month, and how big of a system you’d need to generate enough power, and how many batteries you’d need to store your non-solar needs (days with lower production, no production, overnight, etc.).

    (Edit) Meant to give example numbers for what I did in 2022. I ended up spending about $11,000 on the solar panels themselves, and the batteries would have been ~$23,000, for a monthly peak usage of about 1500kwh.

    I did not spend $23,000 on batteries, because that would have been (and the math has tracked afterwards) more than a decade payback time, which was longer than the manufacturer specs indicated that I could expect the batteries to last.

    I’m sure prices have decreased some in the last 2 years, but solar panels aren’t too badly priced, but the rest of the storage stuff around it was just a bit too expensive to make any real sense unless I was somewhere doing the no-grid life, which isn’t the case here.


  • Have some stuff on a VPS, some stuff hosted as static pages at Cloudflare, some stuff hosted at home too.

    Depends on if 100% uptime is required, if they’re just serving static content, or if they’re in some way related to another service I’m running (I have a couple of BBSes, and the web pages that host the clients and VMs that host the clients run locally).

    Though, at this point, anything I’m NOT hosting at home is kinda a “legacy” deployment, and probably will be brought in-house at some point in the future or converted to static-only and put on Cloudflare if there’s some reason I can’t/don’t want to host it at home.




  • But again, most people aren’t running Linux

    Exactly. This is bad, for the 0.3% of the computing population that use Linux AND have CUPS installed AND actually print things.

    Not exactly a prime target, compared to literally almost anything else. If I were going all-in on something after having gained access to someone’s local network, I’m 100% in on any exploit that lets me use an infostealer trojan to steal your session cookies, not fiddling around and hoping you print something.

    (Patch your shit anyways, but there’s no need to freak out.)


  • That’s a very rosy picture, but they skipped a very important detail, alas. Or well, a few.

    First, selling your power to the power companies in Texas is great! Except the amount they pay you is always going to be substantially less than the price you’re going to pay later to import a kwh.

    We have the Freedom™ to pay two seperate charges for power: the delivery cost, and the power cost. This is a great Freedom™ because it lets the power company pay you the power cost for your exported power, but you get to pay both halves when you no longer have that kwh in your batteries later.

    Also this is just an attempt to get someone else to pay their CapEx to catch extreme usage events, and the incentives being paid out to people who have spent tens of thousands of dollars is still tilted in the power company’s favor. The article itself even says it’s helping them make a bigger profit: if it was a fair set of incentives, well, then that wouldn’t be what’s actually happening, would it?

    And, worse, any non-Texans might not catch how unlivable shit gets if your A/C starts screwing with the set temperature when it’s 110F outside. The article says it turns it ‘off’, but the impact I’ve seen from some friends who have one of these plans setup is that it simply sets the temperature to something like 86; high enough to stop the usage, but not quite enough to kill you or your pets if you’re not aware it’s done it. Still, not the most pleasant.

    Still, it’s a good idea and a step in the right direction, but we need (lol, lmao) actual real regulation around this and the incentives to be a little less… lame. They’re very much structured around the ‘well, what else are you going to do with your excess?’, rather than with a real intent of fair dealing.








  • Docker is probably the simplest way to get a working deployment, since there’s a lot of moving pieces in a Nextcloud install.

    Though, it’s not going to automatically update itself unless you’ve made a poor choice for a production environment configuration, which sounds like what happened here.

    (Even using a latest tag isn’t really a problem until/unless you re-pull the image to do the upgrade. And/or have configured something to automatically update your shit, but again, don’t do that in production.)

    Nextcloud is also annoying in that updating the base won’t pull all the apps to a current version, so you have to know what’s going to break before you update the base so you can then update the apps as needed. Which, again, can’t just be left up to automatic updates.


  • I’d like to second the ‘manufacturer doesn’t matter, all drives are going to fail’ line, but specific models from manufacturers will have a much higher failure rate than others.

    Backblaze, for example, publishes quarterly(ish?) stats showing the drives with the highest failure rates in terms of percentages, so you can kind of get a good view on if there’s a specific drive model you should maybe avoid.

    Or just buy an actual enterprise drive, avoid SMR, and have backups is also a sane approach.