finnn

You can see where bird.makeup sets the headers here[0] (with a distinct lack of user agent) and an issue I filed against the upstream[1] asking them to please set a user agent.

Moxie and Signal didn't do anything other than asking LibreSignal politely to stop using their servers. They didn't "shut down" anything, and they have shown no interest in shutting down signal-cli/signald.

MobileCoin, the cryptocurrency that Signal incorporates and essentially sanctions, uses signald for their bot[0].

the Signal Matrix bridge has hundreds if not thousands of open source users, plus Element One and Beeper users, all using signald and not having any repercussions for years. The only 3rd party Signal client that's caught any flak from Signal that I'm aware of is LibreSignal.

also see: last time this came up[1]

I meant they may ask some clients not to use their servers, but they don't have any enforcement mechanism in place beyond asking them to stop on github.

I cannot speak for moxie or Signal. I can speak for my own experiences, as the maintainer of a fork of signal-cli, and I have never seen any evidence that Signal's servers block signal-cli or my fork. I don't know about signal-cli but my fork clearly identifies itself in the user agent (and another field called the "signal agent") to the server. If they wanted to block me they could.