cyberax
Joined 13 years ago
Joined 13 years ago
Well, you need more oxygen to burn more nutrients. This means faster heart rate.
The body normally doesn't want to waste energy, so the heart rate at any given moment is just enough to cover the requirements.
Precisely calibrating that is another story. You can go into one of the places that directly measure the oxygen use and get the baseline data (e.g. https://www.dexafit.com/services/vo2-max-testing )
I assume that you're just completely ignorant, and as such, you can't be educated.
> Before 1971 we had a gold-backed monetary system
We didn't.
> and no record of deflation in the history of mankind.
Germany, 1932-1933. US, 1927-1933. And so on.
When you transfer a dollar from your account to Putin's account in a Russian bank, in reality your bank transfers a dollar from their account within the FRS (Federal Reserve System) to Putin's bank's account within the FRS.
It can be more complicated with more intermediaries, but it can be traced and reverted.
They also get dimmer and dimmer. The same amount of emitted (or reflected) radiation gets spread out over longer and longer periods of time.
In reality, the light is also quantized, so it doesn't take that long for the last emitted photons to escape.
If you are a free-falling observer, _nothing_ changes for you locally at the event horizon. You will cross it and reach the singularity within a finite (and quite short) time.
You should perhaps look at all the crashes where the autopilot stalled the aircraft on approach due to incorrect settings.
You also can get periodic absolute fixes to correct for the accumulated drift.
mDNS exists. As does SIP and SMB.
I first discovered the ULA/GUA issue when my TimeMachine backup dropped mid-session when I was testing Internet connection failover. Apple later fixed it by allowing multiple SMB sessions in parallel and preferring IPv4 connections. I have a pure IPv6-only network, as I said.
The same issue happens with SIP, as phones send their own addresses during the media connection negotiation.
(I have another funny story about SIP: Asterisk used to send a Cartesian product of available codecs and IP addresses, so if you had IPv6 privacy addresses on, it eventually accumulated enough of them to overflow the MTU, causing connections to silently drop)
My car's GPS does, using dead reckoning.
Trains can also use dead reckoning.
/me checks notes, I've heard that they move on inflexible things called "rails" that almost never change the location.
In English, which is NOT my native language. I had to memorize my lines without understanding half of them :)
Having to waste 64 bits for the local part of the address is another one. There's an RFC in progress to allow neighbor discovery with shorter prefixes, so we might be able to use it by 2045.
And Android _still_ doesn't support DHCPv6.
I don't have a LAN's DNS server or a DHCPv6. BTW, I have had an IPv6-only home network for 10 years, with NAT64 and 464XLAT.
You still haven't solved my puzzle or even understood what's happening. The current source address selection rules result in hosts prefering a GUA address pair over ULA. This _will_ result in broken connectivity when GUA addresses change.
There is currently no standards-compliant way to solve my challenge, except getting an ASN, an IPv6 assignment, and announcing it through your uplinks. Which I've also done in my home network, btw.
There's an in-progress RFC to change this, by preferring ULA-ULA address pairs over GUA-GUA. So it might be usable some time in the 2030-s ( https://www.ietf.org/archive/id/draft-ietf-6man-rfc6724-upda... ).
And no, this is not a theoretic problem. It affects protocols like SIP or even mDNS that exchange the IP addresses. They will consistently prefer unstable GUAs over ULAs.