3 ms·

It's based on the Matrix protocol, which you may have heard of. So, yes, it bears more than a little resemblance to Wave by way of IRC, and was built to fix IRC

It's based on the Matrix protocol, which you may have heard of. So, yes, it bears more than a little resemblance to Wave by way of IRC, and was built to fix IRC's problems (lack of identity, poor netsplit tolerance, weak extension support, etc.), and also provide strong capabilities for bridging between protocols, so it doesn't wind up in an xkcd.com/927 type scenario.

kuschku 10y ago
> weak extension support Which definitely doesn’t apply to IRC > lack of identity Which the CAP Account extension allows to provide > strong capabilities for bridging between protocols And a Matrix-IRC bridge that constantly breaks, doesn’t properly handle private messages, and which badly handles IRC extensions?
- qwertyuiop924 10y ago
  IRC bots are a hack, and so much is provided by extensions, that there's no guarantee that your client will support basic features. CAP Account is just that: an extension. It's not inherent to the protocol, and it shows. And I didn't say the present bridges were perfect yet. The project is still a ways from completion.
  - kuschku 10y ago
    > It's not inherent to the protocol, and it shows. IRC extensions are supported by over 90% of clients already, and provide exactly that. In contrast to XMPP is IRC actually renewing itself in production. http://IRCv3.net/ http://IRCv3.net/ EDIT: I can’t answer you right now (you are submitting too fast), so here is my answer inline: > I’ll show the list of extensions both supported by every modern client, and each of the networks you mentioned: > freenode: sasl, account-notify, identify-msg, multi-prefix, extended-join > efnet: multi-prefix > quakenet: none > Hackint: invite-notify, cap-notify, chghost, echo-message, userhost-in-names, account-notify, server-time, account-tag, multi-prefix, extended-join, away-notify, tls, sasl > Snoonet: away-notify, sasl, account-notify, invite-notify, userhost-in-names, multi-prefix, extended-join > Mozilla: sasl, userhost-in-names, multi-prefix > EsperNet: away-notify, sasl, account-notify, multi-prefix, extended-join, tls > Also, support for extensions by server: http://ircv3.net/software/servers.html http://ircv3.net/software/servers.html > And by client: http://ircv3.net/software/clients.html http://ircv3.net/software/clients.html > Any more questions?
    - qwertyuiop924 10y ago
      XMPP is radically different from IRC. And I don't know about you, but I don't see a lot those extensions in use on actually servers (freenode, efnet, quakenet, etc).

kuschku 10y ago

> weak extension support Which definitely doesn’t apply to IRC > lack of identity Which the CAP Account extension allows to provide > strong capabilities for bridging between protocols And a Matrix-IRC bridge that constantly breaks, doesn’t properly handle private messages, and which badly handles IRC extensions?

qwertyuiop924 10y ago
IRC bots are a hack, and so much is provided by extensions, that there's no guarantee that your client will support basic features. CAP Account is just that: an extension. It's not inherent to the protocol, and it shows. And I didn't say the present bridges were perfect yet. The project is still a ways from completion.
- kuschku 10y ago
  > It's not inherent to the protocol, and it shows. IRC extensions are supported by over 90% of clients already, and provide exactly that. In contrast to XMPP is IRC actually renewing itself in production. http://IRCv3.net/ http://IRCv3.net/ EDIT: I can’t answer you right now (you are submitting too fast), so here is my answer inline: > I’ll show the list of extensions both supported by every modern client, and each of the networks you mentioned: > freenode: sasl, account-notify, identify-msg, multi-prefix, extended-join > efnet: multi-prefix > quakenet: none > Hackint: invite-notify, cap-notify, chghost, echo-message, userhost-in-names, account-notify, server-time, account-tag, multi-prefix, extended-join, away-notify, tls, sasl > Snoonet: away-notify, sasl, account-notify, invite-notify, userhost-in-names, multi-prefix, extended-join > Mozilla: sasl, userhost-in-names, multi-prefix > EsperNet: away-notify, sasl, account-notify, multi-prefix, extended-join, tls > Also, support for extensions by server: http://ircv3.net/software/servers.html http://ircv3.net/software/servers.html > And by client: http://ircv3.net/software/clients.html http://ircv3.net/software/clients.html > Any more questions?
  - qwertyuiop924 10y ago
    XMPP is radically different from IRC. And I don't know about you, but I don't see a lot those extensions in use on actually servers (freenode, efnet, quakenet, etc).