I’ve been finding Zulip quite helpful. It’s threading model is great and they overall focus quite a bit in the project coordination use-case. You can either self-host it or pay for their managed hosting (which is free for open-source projects), and you can add a plugin to make static HTML pages of streams (aka channels) in order to make stuff indexable and searchable (and iirc this is getting polished and built into Zulip’s core).

If you care about accessibility, email is still the best choice — it’s mostly text-focused, doesn’t need an account (besides what is universally seen as the most basic Internet identity), truly decentralized and has mature tooling. I just haven’t found a really good mailing list archive web UI. HyperKitty is good, but isn’t quite there for me. lists.sr.ht is neat, but lacks a lot of features. Above all, indexability and searchability (from inside the UI itself) is key.

musl isn’t vulnerable, as per https://fosstodon.org/@musl/112711796005712271

The exploit isn’t that practicable, since it takes a very long time on 32 bit systems, which are ever rarer to see.

Last time I tried starship (a few years ago), it was pretty bad, very sloppy performance, not async, at least on fish. I ended up sticking with the simple, yet effective hydro. Maybe I can give starship another try, but honestly don’t know if I even need all those bells and whistles…

It’s not because of features, since fish has tons of stuff as well and is super snappy. Someone pointed out most of those extra features are implemented in zsh itself, rather than in C, like core features.