yes, I run my matrix server 24/7. I’m not really the expert on this, but I believe the way federation works on matrix is that downtime means that users on that instance will not be able to see/write messages, but users on other messages will still be able to write messages, which will later be picked up by the crashed instance when it comes back up. Not sure how it affects rooms.

Right, and wouldn’t the rings be pretty fragile considering how long they are? So it would probably have similar bioactivity as like olive oil.

Not really. I mostly used Element, but I also tried fractal which seemed decent.

The tough thing is that the supported features are changing rapidly, so what might be a good client one year might be out of date the next year. I also had a lot of issues with Element randomly logging me out on my self-hosted server :/

I wish Matrix video calls worked better so it could take over

Space elevator companies seem to think that materials exist that are strong enough, just that they are not long enough.

https://www.isec.org/space-elevator-tether-materials

Very much layman conjecture, but my assumption is that this material is stronger than carbon nanotubes and graphene.

Paper link: https://www.science.org/doi/10.1126/science.ads4968

Any law that prevents me from counterfeiting money is an intolerable encroachment on my right to free speech

It would probably be strong enough, but not viable to manufacture.

it’s very lightweight though, so it could reduce plastic usage by mass, by reinforcing plastic/other materials.

There’s also no reason why polymers need to be made out of oil: See PLA, cellophane, viscose, etc.

molecular chainmail

14 yo’s were 6 when Trump’s first term started

The EU and its allies is bigger than Trump’s rogue oligarchy

now this is shitposting

Oh definitely, everything in kubernetes can be explained (and implemented) with decades-old technology.

The reason why Kubernetes is so special is that it automates it all in a very standardized way. All the vendors come together and support a single API for management which is very easy to write automation for.

There’s standard, well-documented “wizards” for creating databases, load-balancers, firewalls, WAFs, reverse proxies, etc. And the management for your containers is extremely robust and extensive with features like automated replicas, health checks, self-healing, 10 different kinds of storage drivers, cpu/memory/disk/gpu allocation, and declarative mountable config files. All of that on top of an extremely secure and standardized API.

With regard for eBPF being used for load-balancers, the company who writes that software, Isovalent, is one of the main maintainers of eBPF in the kernel. A lot of it was written just to support their Kubernetes Cilium CNI. It’s used, mainly, so that you can have systems with hundreds or thousands of containers on a single node, each with their own IP address and firewall, etc. IPtables was used for this before. But it started hitting a performance bottleneck for many systems. Everything is automated for you and open-source, so all the ops engineers benefit from the development work of the Isovalent team.

It definitely moves fast, though. I go to kubecon every year, and every year there’s a whole new set of technologies that were written in the last year lol

emulation is only legal if you pay Nintendo to steal open-source code for their emulator as a service subscription

Norway has much nicer benefits and lower cost if living than California

American doorbell cams are the new Russian dashcam. Only main difference is that American doorbell cams are directly connected to the cloud/police.

Ah, ok, yeah seems very custom. I guess it must predate Ingress.

No problem, good luck!

Ah, but your dns discovery and fail over isn’t using the built-in kubernetes Services? Is the nginx using Ingress-nginx or is it custom?

I would definitely look into Ingress or api-gateway, as these are two standards that the kubernetes developers are promoting for reverse proxies. Ingress is older and has more features for things like authentication, but API Gateway is more portable. Both APIs are implemented by a number of implementations, like Nginx, Traefik, Istio, and Project Contour.

It may also be worth creating a second Kubernetes cluster if you’re going to be migrating all the services. Flannel is quite old, and there are newer CNIs like Cilium that offer a lot more features like ebpf, ipv6, Wireguard, tracing, etc. (Cilium’s implementation of the Gateway API is bugger than other implementations though) Cillium is shaping up to be the new standard networking plugin for Kubernetes, and even Red Hat and AWS are starting to adopt it over their proprietary CNIs.

If you guys are in Europe and are looking for consultants, I freelance, and my employer also has a lot of Kubernetes consulting expertise.

ah ok