The signal server project in GitHub isn't updated in 9 months. Have they talked about why they don't do server development in the open?

The Signal servers essentially pass around encrypted blobs from one device to another. Most of the development work is on extending the clients to pass around different types of messages, so there's not much work that needs to be done on the server.

9 months is a long time to go without updates though, especially if you just got a ton of extra users. While I definitely see your point, GP also has a point about development clearly not being open. It's "code available" software, not "open source server" software.

Server code may not tell you what the server is deployed on.

Hence my writing of

> Even if we don't know what services they use

and it merely helping to find

> what language the [server] stuff is written in

I don’t understand how that will help you figure out the equivalent of a post mortem for a service outage.

You said you asked them about their "tech stack and ability to scale". A tech stack consists of frameworks and languages used, which can be found on GitHub, so there's part of your answer.

Indeed I'd be interested in the post mortem here and I also don't expect anything from them (depending on how large this turns out to be, though, and so far it's actually a rather huge outage so maybe we'll get some info after all).

Ah, I meant their infrastructure as well.