[finnn]

signald author here, open to suggestions on that name. As you've noticed, I try to avoid using the word "signal". I do agree that the current name is pretty awkward.

edit: the name for signaldctl. I'm not looking to rename signald at this time

[exikyut]

It's fine. You're borrowing from the systemd/systemctl pattern. That would suggest signald/signalctl, but signaldctl works too.

This being said, looking one level up the "bigger picture" chain "signalprotocold" comes to mind - but then "signalprotocoldctl" would give me a small headache :), and I don't know a good solution there. "spdctl" sounds it would be for a DIMM EEPROM configuration (???), "sigprotoctl" sounds nice if somewhat random, and... ugh, naming things is hard.

[InvaderFizz]

Well, how about beacon.

It also happens that most tlds with beacond are available.

Cursory search on GitHub says you would be pretty alone in your use of beancond as well.

[gaius_baltar]

Sorry for "invading" an unrelated reply, but thanks for your work! I discovered signald an hour ago and I'm really happy about it.

I'm pretty sure that's the way for a better desktop experience with Signal, but I still need to test a few clients. Even before that, with signaldctl and the Python libs alone I already have a way of sending notifications, etc.

[finnn]

:)

[imposterr]

Not that I particularly think there's anything wrong with signaldctl, but for other apps that employ a daemon/control model, I've always found <service_name>d and <service_name>-cli combo to be good naming scheme.

So signald and signal-cli in this case.

[finnn]

well "signal-cli" is already in use by https://github.com/AsamK/signal-cli (which signald is a fork of)

[neltnerb]

I'll assume it's a terrible idea, whisperd and whisperclient are probably too on the nose.

Beacon is pretty great =)

[stock_toaster]

langis (signal backwards).