Ascrod
Ascrod
There seems to be a bit of confusion over what the client should do if it receives an STS upgrade policy over an insecure connection via `CAP NEW`. It's not...
Currently, Ambassador only supports receiving a single `CAP ACK`/`CAP NAK` line in response to a `CAP REQ` command. We should not only be able to handle multiple `ACK`/`NAK` responses at...
Add negotiation for the `setname` extension, add a `SETNAME` command and response, and ensure the user's realname gets updated properly. Shouldn't be difficult, but looks like it depends on #72....
https://ircv3.net/specs/extensions/standard-replies http://ircv3.net/registry Adds a number of generic FAIL and WARN responses for a variety of commands.
https://ircv3.net/specs/extensions/labeled-response A new type of `batch` used for correlating server responses with client messages.
Ambassador has the capability to support automated download and install of updates, similar to other UXP applications. The update backend needs to be set up to support AUS for Ambassador.
Now that the [Message IDs spec](https://ircv3.net/specs/extensions/message-ids.html) has been ratified, support for the msgid extension should be added.
Networks can have a displayName attribute, but this is not exposed in the networks editor.
Some recommendations given by the [Strict Transport Security](https://ircv3.net/specs/extensions/sts.html#user-declared-sts-policy) spec include allowing users to add custom policies and remove existing policies. I think this can be easily done by adding a...
This has been present for a while, but I'm formally documenting it now. Currently the extension build script produces an XPI with bogus modified dates on the contained files. This...