Coops are still about the money. They’re about saving money by sharing resources with fellow workers/consumers, and maintaining democratic control over the company. You’re not going to get rich from a coop (without embezzlement), but you and your coowners will be cutting out the middle man. Obviously, it only makes sense for industries that you’re heavily invested in.

Self hosting can save a lot of money compared to Google or aws. Also, self hosting doesn’t make you vulnerable to DDOS, you can be DDOSed even without a home server.

You don’t need VLANs to keep your network secure, but you should make sure than any self hosted service isn’t unnecessarily opens up tot he internet, and make sure that all your services are up to date.

What services are you planning to run? I could help suggest a threat model and security policy.

Not to mention, fiber is cheaper than copper at this point.

Telecoms are just lazy and don’t want to string up new lines.

Reminds me of what happened when Milosevic tried to decline a ceasefire agreement

humidity shouldnt be a problem with modern ventilation and such large cooling surfaces.

I’m honestly shocked how much of a fuss the participants are making over 22-26° rooms. My apartment is almost never below 25°, even in the winter. Are they somehow going to perform better if it’s 20° and they freeze? Not to mention fucking loud portable air conditioners are. There’s a heatwave going through Sweden right now, and my apartment was up to 30° this afternoon.

Also really defeats the point about not using air-conditioning when all the participants just bring in super-inefficient portable units and then immediately throw them in the trash. I guess it’s good for energy efficiency in the long run though for when these buildings become normal apartments.

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.

Ah fair enough, I figured that since the registers are 512 bit, that they’d support 512 bit math.

It does look like you can load/store and do binary operations on 512-bit numbers, at least.

Not much difference between 8x64 and 512 when it comes to integer math, anyways. Add and subtract are completely identical.

Tons of computing is done on x86 these days with 256 bit numbers, and even 512-bit numbers.

There’s plenty of instructions for processing integers and fp numbers from 8 bits to 512 bits with a single instruction and register. There’s been a lot of work in packed math instructions for neural network inference.

Now do the same for Volvos.

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.

And hack their phones so we can see why they want to spy on everyone else’s phones

It was protected by the ECHR in a recent ruling. https://www.eff.org/deeplinks/2024/03/european-court-human-rights-confirms-undermining-encryption-violates-fundamental

However, Chat Control 2.0 argues that since the spying is done before the content is encrypted, it’s somehow ok. 🙄

As a Swede, no snickering here, it’s very cool to see more geothermal district heating and cooling systems being built.

How do they do cooling with radiators without having condensation issues? I’ve never seen any apartments with district cooling that weren’t specifically built with air handlers for it.

milk is tea

They block IPv6 tunnels too.

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.

Yeah, more accurate dead reckoning is always useful, but you’ll still need some sort of of ground-based or satellite based navigation system if you’re using this for any system that requires any reasonable amount of accuracy.

I’ve been using sudo-rs as a drop-in replacement for sudo, it works well. The codebase is like 1/5 of the size, it drops some of the crazier features of sudo, extremely minimal dependencies, and it’s all written in memory-safe rust. NixOS also has an option for setting the sudo binary to be executable by wheel only, so the attack surface is very small.

https://www.memorysafety.org/initiative/sudo-su/ https://github.com/memorysafety/sudo-rs https://search.nixos.org/options?channel=24.05&size=50&sort=relevance&type=packages&query=sudo-rs