If it’s a low resistance path to ground, it’ll get very very toasty! If it’s a lousy ground though, then it won’t…but it also won’t consume any power, so it’s not an effective way of scrubbing off electricity.
A good ground (low resistance) is found in your household wiring (the ground and/or the neutral). Of you short to that…well…you can guess what will happen! (Let’s hope you have proper circuit breakers.)
Of course. Like I said, we know how to do it, but it’s still an engineering feat to get it done.
That is not how it works.
When you short something to ground, it’s everything in between that needs to dissipate the heat. Think about what “sending it to ground” means—it means you connect the hot to the ground. But with what do you connect the two? A wire? Sure, but you better hope that wire can dissipate all that power, because that’s what it’ll try to do.
You can’t just “dump power on the ground.” That’s not how it works.
This gets posted regularly on Lemmy, and while the economic take is tone-deaf at best, there’s a real issue with generating more power than you can use. You can’t just dump grid power — it needs to go somewhere. The grid needs to consume as much as it generates at all times or else bad things happen.
There are of course solutions, but that doesn’t mean it’s not an engineering challenge to implement.
Figuring out what to do with kilowatts is easy, but figuring out what to do with megawatts, at the drop of a hat, is substantially harder.
I have a keyboard hotkey to take the copy/paste buffer and display a QR code on screen. Straightforward to implement on macOS, and presumably Linux too.
macOS: pbpaste | qrencode -t ANSI
You can/could also find Coffee HOWTO in your distro’s HOWTO package. (I found a reference back to v0.5 of the document in 1998.)
Has simple schematics to get you started for the hardware, using the parallel port to toggle relays.
It’s a very neat little document, and inspired me to write a simple kernel module so I could echo 1 | sudo tee /sys/whatever/coffee0 to turn pin 0 high on the parallel port. (This is silly, and it’s much easier to just do things in user space!)
Humans weren’t meant to live with zero autonomy.
Not every parent removes all autonomy from their child. Sorry that happened to you, sounds like it sucked.
Not just UNIX-like, but actual UNIX.
IIRC there were some UNIX-certified Linux distros out there too, not sure if they’re still around.
Only one of them is UNIX.
Cool, I recommend it!
I have my public facing reverse proxy point to my public services, and I also have it set up as a “roadwarrior” VPN to my home. So, I can connect my phone via WireGuard to my VPS, and a local DNS resolves my private services to the private IP addresses in my home network (so, I also run a reverse proxy on my server, for internal services).
I also have an off-site backup using this — just a raspberry pi and an HDD at family’s, that rsyncs+snapshots over the WireGuard network.
I’m sure I’m not following all the best practices here, but so far so good.
VPS with a public ip (which just takes all the fun out of selfhosting)
Why do you say this? My VPS only runs a reverse proxy and WireGuard, with all services hosted on my computers at home.
I’ve heard stories of grad students flat out refusing to work with HF. (Never relevant for me, other than being something very scary.)
Remember that RAID and redundancy is not backup.
Try to 3-2-1, or something similar/better, if you can.
I am fairly sloppy here, and I am also very cheap. I have multiple copies in my home for important stuff (mainly Immich), the in use copy being on SSD and a few backups on spinning rust. I have a raspberry pi with an external HDD at family’s place, with a daily rsync+snapshot, for off site backups.
Of course, I’ve never had a catastrophic failure, so who knows how smooth that would be…
I switched to Technitium and I’ve been pretty happy. Seems very robust, and as a bonus was easy to use it to stop DNS leaks (each upstream has a static route through a different Mullvad VPN, and since they’re queried in parallel, a VPN connection can go down without losing any DNS…maybe this is how pihole would have handled it too though).
And of course, wildcards supported no problem.
Maybe take a look at Outline. (Not affiliated, but I host it for myself.)
I also host KitchenOwl, but mostly just as a grocery list.
The dot-com bubble burst, but…well, it got better.
Of course there were some casualties (famously pets.com), but Microsoft, Cisco, Intel, Amazon…yeah they got their clock cleaned at the time, but long term they were pretty successful.
For all the problems with tech companies, having a chunk of compensation be in the form of RSUs isn’t the worst idea ever. (I know it’s not specific to tech companies, but it’s generally a very prominent aspect of tech company compensation, Netflix notwithstanding.)
I brought this up to my ex over the course of our usual conversations
…
If we are weeks away from never being able to meet again
…🤔
At this point, they no longer obey the laws of classical physics, and the resulting quantum phenomena — known as relativistic effects…
This is…not how I would word things. Atomic physics is usually not in a classical (Newtonian) regime, and a quantum treatment is standard.
Adding relativistic effects to the quantum treatment is also standard, but many aspects of e.g. the hydrogen atom are reasonably well described without relativistic effects, though of course relativistic effects do matter.
Nitpicking aside, neat stuff!
Oh they absolutely do! My only point is that grid supply must equal grid demand. There are many ways to achieve this, as folks here have pointed out.
Throttling power generation (turning off/disconnecting PV from grid for example), and storage (chemical, heat, or hydro battery) are all established technologies, they just need to be implemented properly to avoid supply/demand mismatch.