The irc middleware needs a bit of a refactor. It is currently massive, and should be split into more files with their own logic.

Considering a plugin system

const AwayPlugin = (client, dispatch) => {
  client.registerEventHandler('away', onAwayEvent);
  client.registerEventHandler('back', onBackEvent);

  const onAwayEvent = e => {
    const { nick } = e;

    const uid = client.getUidFromNick(nick.toLowerCase());
    this.dispatch(
      setUserlistUser(uid, {
        nick,
        away: true,
      }),
    );
  };

  const onBackEvent = e => { ... }
}

Implement the typing client tag specification

timestamps currently doesn't display the proper 24-hour clock format.

should also add a setting for 12-hour clock.

With KiwiIRC not seeing much further development and nice IRCv3 compatible IRCd like ergo chat (with build in websocket support) available, having another modern webclient would be quite cool.

How far did development go? Any test instance?

Is ircv3 chat history supported?

Thanks!

See Considerations for loading client-provided URLs (such as images for a some good points on this.

as per subject.

If connecting through a /channel/:channel or /message/:nickname path the client crashes and burns. This is due to an assumption that these exist.

Idea:

Introduce a /reply command that functions like:

/reply <nickname> <message>

That would simply reply to the last message by nickname.

Pros:

• easy reply capability for simple q&a type threads

Cons:

• regular clients without threading support would display the message in the regular buffer

Some sites, such as wikipedia, has a url that shows as .jpg, but is actually a html page containing the image. These show up as broken due to not being loadable by

To handle this, perhaps we should create a custom component that hides the image if it is broken (using the onerror event on elements).

Key bindings are important, so lets use common keybindings:

• alt + up / down - move up/down channel/dm tree
• alt + shift + up / down - move up/down unread channel/dm tree
• ctrl + k - open channel list
• ctrl + shift + y - set away/back
• ctrl + b - bold text
• ctrl + u - underline text
• ctrl + i - italic text
• ctrl + shift + x - strikethrough text
• ctrl + return - send action

Unread indicators should display the amount of unread messages in the sidebar. When in a channel, it should display a marker since the last read message.

Using labeled-response and echo-message we could implement delivery notices.

From the labeled-responses spec:

Client: @label=pQraCjj82e PRIVMSG #channel :\x02Hello!\x02
Server: @label=pQraCjj82e :nick!user@host PRIVMSG #channel :Hello!

Defining a message as "sent" when you send it, and "delivered" when the server responds could be useful for users to see if their messages are being delivered (and as a way to check if messages have been altered, displaying the altered version in the client).

One of the nice things thats possible is to store the last x messages in localStorage.

This way the next time a user visits the webpage, the old conversation history could be shown. Paired with the chathistory spec it could give users a bit more of context.

Some questions arise from this though:

• What if the history data stored is old and obviously obsolete?
• Should the history be shown in different ways depending on where it comes from?
• How many messages should be stored by default, considering theres a 5MB limit on localStorage?

At the moment, we do not automatically scroll to the bottom of the buffer.

Support some basic Markdown syntax:

• Italics with *text* or _text_
• Bold with **text** or __text__
• Strikethrough with ~~text~~
• Monospace blocks with `text`

Settings are currently not being handled at all - they should be dispatched and sent to the store.

The client should notify users (given their settings are so) of important events.

• Notify on @mention
• Notify on all messages
• Notify on private messages

As subject.

One network in the network list causes the dropdown to be hidden. The behaviour should be that this will be the default chosen network. This is not happening now.

Supporting themes would be nice, so I've started a small refactor to do this using styled-components at the heart. This also means that I'm removing most of the CSS files and using styled-components instead.

Things needed to support themes:

• switch styling of components over to styled-components
• provide a theme context
• settings to change theme

App.js gives this nifty little error:

React Hook useEffect has a missing dependency: 'history'. Either include it or remove the dependency array react-hooks/exhaustive-deps

Adding history to the dependencies causes an infinite rerender loop, due to history being mutated and causing a rerender.

as stated.

Bug in slate 0.47.* that causes toggleMark to not split text on toggles.

Currently TextFormatter do not support colors. See colors.

• Should colors be CSS defined?

Messages are currently sent to the buffer id instead of channel.

A lot of the message type components really do the same thing, with little to no difference between them, for instance JOIN, PART and QUIT.

I think refactoring this logic into larger components will be beneficial to keep complexity low.

Automatically linkify messages, favoritizing a https schema for links of the type github.com.