[Leo_Verto]

It's a shame it had to come to this but I can see why Element had to make this choice.

To me it feels like they've ended up in a position similar to Docker Inc. where they've spent years of work and tons of resources building the standards and reference implementations, but missed out on the juicy integration and support contracts.

Docker has turned into the OCI standard and most Kubernetes deployment don't even run containerd anymore. The company has massively rate limited Docker hub and recently increased the pricing again, which has had much bigger impact for end users than this pivot by Element.

I really hope this works out as a funding source for future Matrix development, I don't see how its ecosystem can continue to be developed and healthy without Element.

[koito17]

> most Kubernetes deployment don't even run containerd anymore

I assume you mean moby, which was used via dockershim in Kubernetes until support was removed in v1.24.

I can't find a reliable source, but I believe containerd, followed by CRI-O and alternatives, are the common choices of container runtime for Kubernetes.

https://kubernetes.io/docs/setup/production-environment/cont...

[ffsm8]

It was called plain docker originally, the Moby rebrand came much later and not everyone is even aware that it happened, because plain docker was already much less relevant when they did it (vs k8s, which was already becoming the default by then).

https://www.docker.com/blog/introducing-the-moby-project/