Don't do this. Install a transfer switch. A simple plug and another power source feeds power back into the grid. It's absolutely against code. If you remember to flip the furnace breaker off before you do this, then it's not going to backfeed, but this isn't something you should rely on remembering to do. It doesn't cost much more to do it right.
I think they're proposing switching your furnace from hard wired to plugged, so you have the option to power it either from an outlet (grid) or solar/generator/etc. This can't backfeed the grid, and is very safe.
It looks like when it's against code it's "by default": if an appliance is not explicitly listed as acceptable for a plug it has to be hard wired. ND and OK have passed state level amendments allowing it, some places have done this locally, and in many places building inspectors allow it with their discretion.
Yeah, maybe I misread. Switching it manually via a plug such that it could only ever be powered that way is fine (well, "fine" insofar as it alleviates my concern). I thought the suggestion was to add the new plug in addition to the permanently-wired solution.
On a beast of a HVAC system, a simple 15A wall plug isn't going to cut it for powering the whole thing, but if the furnace runs off e.g. natural gas and you just want to power the blower off a 15A plug, that solves the problem of switching power sources.
It's not against code in all locations. You're essentially adding a power cord to your furnace and turning it's existing panel connection into an outlet.
Eg, in North Dakota
"If manufacturer instructions allow the use of not more than six feet of flexible appliance cord, it shall be permitted on permanently installed one hundred twenty volt twenty amp or less fuel-fired furnaces in residential dwellings."
By the nature of blockchain, it's never, ever your crypto. It's allocated to whichever bucket the majority of participants in a given network agree to allocate it to.
Well, not exactly. A malicious majority of miners could rewind the chain as they please. They could indirectly steal some funds by undoing certain transfers, but they couldn’t just directly reassign funds to themselves.
Absolutely not, as GPUs used in data centers cannot compete with ASICs designed specifically for Bitcoin mining.
The Bitcoin mining network is somewhere around 1000 EH/s, while the (AI assisted research ahead) 34.5 million H100-equivalent GPUs globally would yield about 0.435 EH/s. They'd represent less than 0.05% of the Bitcoin network.
Don't you say. You don't even know what was that horrible treatment exactly - didn't even ask, why would you, right? - but you've promptly explained to the guy that it was his fucking fault - he's from the sanctioned country after all, he should know his place and be quiet. You guys are just adorable, aren't you?
That is exactly what the people who live under HOAs want. I despise HOAs, but I'm happy that the kind of people who like HOAs have a community they can all congregate in. It keeps some of them from mingling with the rest of us.
You'll know from bounced email and logs, which you should have monitoring setup on.
It's not trivial to run your own email stack, but it's not hard either. It's more tedious than anything. Once it's up and running, it's low-maintenance. And it's fairly trivial to avoid spam. I get vastly more spam in my Gmail than I do on my self-hosted domains.
The biggest challenge with self-hosted email is getting an IP address that's not blocked or carrying low reputation. Most VPS IPs from e.g. Digital Ocean, Linode, Hetzner, AWS, etc. are going to get blocked from Google (the strictest) and Yahoo, Hotmail/Live/MS, etc. Cloud providers often block incoming and outgoing mail ports, too. I have a Digital Ocean VPS and my account is old enough to be grandfathered into the old policy, which means my email ports aren't blocked. I used to have no trouble sending email anywhere from my VPS, until I downsized it and got stuck with an IP in a bad reputation CIDR. Now I use smtp2go for relaying outbound mail, but still handle all inbound mail. 10/10 score on mail-tester.com, and I never have any problems or need to do any maintenance.
A few major vendors (I want to say Microsoft was among them) were infamous for silently dropping email without bounce backs. They'd perform then whole protocol sequence as if they accepted the email, then simply never actually put it in that user's inbox or even spam folder.
People should read the parent post and stop spreading FUD about email. The only part that isn't easy is the IP requirement. If you don't have a fixed public IP, preferably v4, then self-hosting email is out of reach, but so is hosting other things like game servers. It's the main cost of self-hosting, and one that isn't big relative to all the benefits. Privacy is the biggest one I think, and so is the ability to create unlimited aliases, one for each company/website.
Dynamic DNS clients are a thing. I host a bunch of stuff on my domain, the only issues I have are related to having a local address when I'm at home. I don't host game servers much, but I hosted terraria (tshock) for few a few years.
You can't really host email with dynamic DNS. At least not well. You need stable MX records, you need various other DNS records for SPF/DMARC/DKIM, and most of all you need an IP address with a positive reputation. If you go changing your MX record constantly, you're not going to be receiving email reliably, if at all.
I don't see how. I run them with no public ingress, no plugins or mods. I don't torrent. I'm not sure there's really any attack vector worth worrying about. Certainly no more than many of the other services I host.
reply