(Justin)
Tech nerd from Sweden
When have quants ever used good decision making as a basis for their trading? Saying you use AI brings in investors, that’s good enough for quant funds.
Sure, but you can also rip off electrons from atoms by rubbing them or bending a piece of wire. The energy needed to trigger fission in uranium is less than a picojoule, it just needs to be focused enough to knock away the part of the atom, which is why neutrons are the most common way.
Here is a chart with the rate of fusion for two hydrogen atoms at various temperatures.
https://en.m.wikipedia.org/wiki/Nuclear_fusion#/media/File%3AFusion_rxnrate.svg
This chart bottoms out at a few million degrees, since the probability is extremely low.
ENEMY STAND: ORGAN DISLOCATOR
Oh, you might have one of the newer ones that use interferometry to detect soulless entities.
Yes. This is how motion detectors work. Normally, motion detectors have an IR emitter that acts as a particle, but when someone walks by, the IR emitter works as a wave, triggering the motion detector.
Notably, this doesn’t work with dogs, as they have no souls.
bobcat/lynx mating calls are scary as fuck to hear out in the woods.
I prefer my activity graph in blue.
Oak trees are more closely related to palm trees than they are to pine trees. It would be pretty arbitrary to exclude monocots but still include magnolids and gymnosperms.
Even from a purely structural perspective, they’re all tall and have wood and leaves. Palm trees and banana trees don’t have woody branches, but joshua trees do. I guess there’s a difference that no monocot tree has heartwood, but you’ll still need a chainsaw to saw through the trunk of a palm tree.
Technically you need another 20 digits if you want to get down to a Planck length. (57 digits in total)
I’m using IPv6 on Kubernetes and it’s amazing. Every Pod has its own global IP address. There is no NAT and no giant ARP routing table slowing down the other computers on my network. Each of my nodes announces a /112 for itself to my router, allowing it to give addresses to over 65k pods. There is no feasible limit to the amount of IP addresses I could assign to my containers and load balancers, and no routing overhead. I have no need for port forwarding on my router or worrying about dynamic IPs, since I just have a /80 block with no firewall that I assign to my public facing load balancers.
Of course, I only have around 300 pods on my cluster, and realistically, it’s not really possible for there to be over 1 million containers in current kubernetes clusters, due to other limitations. But it is still a huge upgrade in reducing overhead and complexity, and increasing scale.
Just in time for midsommar! Yeah, it’s pretty unique. I’ll make sure to drink some today for you 😄
I haven’t really looked into it, but it doesn’t seem like it.
Heres the documentation about having multiple cidr pools in one cluster with the Cilium network driver, and it seems to imply that each Pod only gets one IP.
https://docs.cilium.io/en/stable/network/concepts/ipam/multi-pool/
There’s something called Multus that I haven’t looked into, but even then it looks like that is for multiple interfaces per Pod, not multiple IPS per interface.
https://github.com/k8snetworkplumbingwg/multus-cni
Containers are just network namespaces on Linux, and all the routing is done in iptables or ebpf, so it’s theoretically possible to have multiple IP addresses, but doesn’t look like anybody has started implementing it. There’s actually a lot of Kubernetes clusters that just use stateful IPv6 NAT for the internal Pod network, unfortunately.
Yeah, I wonder if there’s any proposals to allow for multiple IPV6 addresses in Kubernetes, it would be a much better solution than NAT.
As far as I know, it’s currently not possible. Every container/Pod receives a single IPv4 and/or IPv6 address on creation from the networking driver.
I have static IPs for my Kubernetes nodes, and I actually use DHCPv6 for dynamic dns so I can reach any device with a hostname, even though most of my devices don’t have static IPs.
The issue is those static IPs are tied to my current ISP, preventing me from changing ISPs without deleting my entire Kubernetes cluster.
Hurricane Electric gives me a /48.
Site-local ipv6 would work here as well, true. But then my containers wouldnt have internet access. Kubernetes containers use Ipam with a single subnet, they can’t use SLAAC.
1:1 stateless NAT is useful for static IPs. Since all your addresses are otherwise global, if you need to switch providers or give up your /64, then you’ll need to re-address your static addresses. Instead, you can give your machines static private IPs, and just translate the prefix when going through NAT. It’s a lot less horrible than IPv4 NAT since there’s no connection tracking needed.
This is something I probably should have done setting up my home Kubernetes cluster. My current IPv6 prefix is from Hurricane Electric, and if my ISP ever gives me a real IPv6 prefix, I will have to delete the entire cluster and recreate it with the new prefix.
“cubic miles”
Just use “Olympic swimming pools” like the rest of us
You’re not y?