Besides Telegram and WhatsApp, Yoake also connects to a real IRC server, over a direct TLS/TCP
socket (not a separate worker thread like the other two networks) - tested against
irc.azzurra.org. For the actual login (Connect dialog, adding/removing a server) see
Connecting to Telegram, WhatsApp and IRC.
Unlike Telegram and WhatsApp (a single account each), on IRC you can add and stay connected to
multiple servers at the same time, exactly like real mIRC: each saved server gets its own independent
Status window, with its own connection, its own channels and its own
/connect//disconnect commands.
Yoake's scripting engine (aliases, popups, on join/on part/on kick/
on nick/on topic/on op/on deop events, timers, identifiers,
color codes) was modeled from the start on real mIRC's behavior - which is why on IRC it often works
more faithfully than on Telegram/WhatsApp, which can only approximate concepts (channel, op, voice,
topic) that don't really exist on those networks. See Scripting for the full list of
aliases/events/popups, and Commands for the full command list.
@) and voice (+), topic./list, /whois, /hop, /me, /ctcp - see
Commands for the details of each./mode: +o/-o (op/deop) and +v/-v (voice)
really do update the status in the nicklist (the same on op/on deop events already
documented in Scripting also fire here) - other mode letters (+b,
+m, +i, etc.) are silently ignored, without a real per-server CHANMODES table./dcc chat (direct socket-to-socket chat), /dcc send (file
transfer with real progress) and sharing stickers/images in channels via a CTCP announcement - see the DCC
section in Commands for details./whois's "on channels: ..." reply) is
clickable to join it, just like real mIRC.No message history. Unlike Telegram and WhatsApp (which keep a history on their own servers, retrievable by reopening a chat), a real IRC server doesn't store messages: what you see is only what arrived while the window was open and connected, exactly like real mIRC.
DCC SEND: sending only, never receiving an arbitrary offer. You can send a file with
/dcc send, but there's no way to accept/download a file someone else offers you with their own DCC
SEND (no "/dcc get"). The sticker/image sharing in channels (see Commands) stays
automatic, but it's limited to 200KB and only works between two Yoake clients.
DCC over IPv4 often needs a manually forwarded port. Without a public IPv6 address, a DCC (chat or file) toward someone outside your local network often fails behind NAT/CGNAT (typical of mobile connections) - this isn't a Yoake bug, it's a limitation of how a direct socket-to-socket connection works without a relay server in between.
Limited MODE support. As noted above, only +o/-o/+v/-v
are interpreted - other channel/user modes have no effect here.
See also Connecting to Telegram, WhatsApp and IRC for the connection dialog,
and Identifiers and functions for $network.