ln-s.net has been dead for over half a year now; both their website homepage
and any previous shortened links return an HTTP 503. Thus, it isn't very
useful to leave this broken command lingering around...
The current message ("xyz isn't on any non-secret channels or is using a channel-list hiding umode.") is long and awkwardly worded.
This also removes an extra period from showing up at the end of the output.
String.re uses first('regexpMatcher', 'regexpReplacer'). If the args
provided to String.re are not a matcher and are longer than a single IRC
message (e.g., from a nested command), then regexpReplacer would never
be tried. A too long error should be handled the same as running out of
args while trying to find a valid regexp.
Signed-off-by: James McCoy <vega.james@gmail.com>
It's probably not so important, but I don't like them being in any
strange random order. Of course having English first would make sense as
it's the default, but I still prefer alphabetical order.
Since the keyid should always match the master key, regardless of
whether there's a subkey or not, reduced this to simply make keyid be
the last 16 chars of the master key's fingerprint.
Changes one line and adds six to do this:
* change keyid = verified.keyid to be keyid0;
* added an if/else check to see if it's the subkey or master key; and
* then set keyid according the result of that check;
* then continues as normal.
Closes#1046
I used Admin for sources of what languages are supported as it's usually
recommended to start translating from there (first plugins, then core).
Replacement code which might work to enable advanced keys with signing
subkeys to be correctly handled by the bot by associating the subkey
with the relevant master key.
Signing format still only clearsigning, the key details are more
important and auth via encrypted token and decryption is likely to be
more reliable anyway as there is far less chance of some other protocol
messing with the signed content. Effectively no chance, though the odd
corrupted packet here and there is still possible. Whereas with
clearsigning it can be broken by all manner of rewriting in
transit (which happens often enough with signed email as it is).
See also Issue #1045 for greater detail of what needs to be fixed and
what is to be done about it.
