Problem

Still has a lot of the same underlying issues discord has. It’s not indexable being the biggest. The reality is that services like stack overflow or an issue tracker like bugzilla, or your local git services issues section or discussion section, hell even something like discourse or even mailing lists, just work better. If someone made an im service that could be indexed by search engines and the like, now we’d be talking. Opensorce design and discussion doesn’t really benefit that much from closed ecosystems and end to end encryption in most cases.

I guess though at least with matrix someone could make a service that acts as a client and indexes content from a list of channels or something…

Discord, matrix, slack and telegram are where documentation goes to die in the current state of things though.

You can configure software rescaling using xrandr and some scripts… But that can cause a massive amount of jank with anything that requires a degree of pixel accuracy

Kubernetes uses cri-o nowadays. If you’re using kubernetes with the intent of exposing your docker sockets to your workloads, that’s just asking for all sorts of fun, hard to debug trouble. It’s best to not tie yourself to your k8s clusters underlying implementation, you just get a lot more portability since most cloud providers won’t even let you do that if you’re managed.

If you want something more akin to how kubernetes does it, there’s always nerdctl on top of the containerd interface. However nerdctl isn’t really intended to be used as anything other than a debug tool for the containerd maintainers.

Not to mention podman can just launch kubernetes workloads locally a.la. docker compose now.

Try using an alternative dns. Some isps DNS servers don’t know how to direct a .zip tld

There are some efforts going on XDA around the phone. Definitely not the most well supported though. Also this thread around getting lineage to run on it.

https://gist.github.com/schoeller/904611a4baa1bae4107a4e3748e4746e