SteamOS is immutable, you always get the same update no matter what you were running before. I think the only files that can get out of sync are in your home folder.
(Justin)
Tech nerd from Sweden
SteamOS is immutable, you always get the same update no matter what you were running before. I think the only files that can get out of sync are in your home folder.
This looks super useful! Would be interesting to see this as a systemd service built into NixOS, so my gaming machine could always have this running without any manual steps.
Nice to see that other companies are finally trying to make a phone that can actually compete with the fairphone. Still not as repairable as the fairphone though, and its unacceptable to have a locked bootloader.
I guess that makes sense, but I wonder if it would be hard to get clean data out of the per-token confidence values. The LLM could be hallucinating, or it could just be generating bad grammar. It seems like it’s hard enough already to get LLMs to distinguish between “killing processes” and murder, but maybe there could be some novel training and inference techniques that come up.
I thought confidence levels were for image recognition? How do confidence levels work for transformer LLMs?
Get a fairphone so you don’t have to ship out your phone when it breaks, you can just repair it yourself with a screwdriver.
It’s a bubble
FreeOTP+ is amazing, originally developed by Red Hat before it was forked.
I prefer my activity graph in blue.
Yeah, the Jellyfin app is nice.
I was a bit frustrated that I couldn’t connect to my Jellyfin for a while on my Google TV. It turns out that Android 12 doesn’t support modern HTTPS certificates, and it was failing with a HTTPS connection error. I had to go and downgrade my certificate from the 2020 Let’s Encrypt CA to the 2015 Let’s Encrypt CA, just to get it to work again. It’s super frustrating that the android version on is so old that it doesn’t support fucking HTTPS certificates from 2020.
My Google TV lags out on subtitles with Jellyfin. It also just lags out in general sometimes and I have to restart it.
Nah, fuck Google TV. The current one hasn’t received an update since Android 12 from 3 years ago, it’s slow as balls and lags out playing videos, and is completely filled with ads. It actively tries to prevent you from remapping buttons and home screen if you actually want to use something else besides Youtube and Netflix. They still sell this thing at full price, even though they clearly abandoned it years ago.
I wish there was more development on Kodi, because the Android TV ecosystem is awful.
Bill their insurance for your lilies. Driving is a privilege and drivers should take responsibility for their mistakes while driving.
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.
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.
If I wanted a device with a plastic screen and a fragile hinge, I’d carry around a Nintendo DS