4 ms·

I spend time in a coding Discord channel, it's a regular many times a day thing for people to paste 1-10 lines of code. With syntax highlighting. That's not pos

I spend time in a coding Discord channel, it's a regular many times a day thing for people to paste 1-10 lines of code. With syntax highlighting. That's not possible on IRC, pasting 10 lines is "spam" and gets you complained at, everyone needs their own syntax highlighter, or the sender needs to bodge uploading to a pastebin site and other people need scripts to fetch them or clicking links waiting for a separate program to open to see them, then they're not inline, the sender can't edit them afterwards. Emoji. Search. Pictures. Screensharing. Voice calling. Video calling. Web clients which can join video/audio calls. Smartphone apps. Push-Notifications. Colours. Embedded inline Office365 documents, in the case of Teams. Meeting invites built-in to Outlook, in the case of Teams. Click thing in Teams, opens in Edge browser with the Edge sidebar open to the Teams chat place where you clicked, for context. Email notifications of things said in Teams chats. Integration with company directory for looking up who people are. IRC is for people whose reaction to those is to complain or sneer about how they don't want them.

xboxnolifes 2y ago
> IRC is for people whose reaction to those is to complain or sneer about how they don't want them. This is the real reason IRC will never achieve wide adoption. The people who use it actively don't want the features that the people who don't do.
- jodrellblank 2y ago
  Don't want the features, and feel superior for not wanting those features: https://news.ycombinator.com/item?id=40813886 https://news.ycombinator.com/item?id=40813886
crtasm 2y ago
I see emoji on IRC every day btw :)
- jodrellblank 2y ago
  I'm sure you do see them, but having encodings consistent between sending client and receiving client isn't part of IRC; RFC 2812 - Internet Relay Chat: Client Protocol[1] says: > 2.2 Character codes > No specific character set is specified. The protocol is based on a > set of codes which are composed of eight (8) bits, making up an > octet. Each message may be composed of any number of these octets; > however, some octet values are used for control codes, which act as > message delimiters. > Regardless of being an 8-bit protocol, the delimiters and keywords > are such that protocol is mostly usable from US-ASCII terminal and a > telnet connection. Mojibake from disparate clients is part of the design; people have had to go outside the standard to make undocumented informally specified variation(s) such as "use utf8". Saying IRC is encoding-agnostic passing 8-bit bytes around, is like saying "I see emoji using TCP/IP every day". (Contrast with HTTP where a client can declare what it accepts in the request headers on a per-request basis, and servers can declare encodings they are sending in the response headers on a per-message basis. Contrast with proprietary Slack where one company codes every client and can make them all behave the same). [1] https://www.rfc-editor.org/rfc/rfc2812#section-2.2 https://www.rfc-editor.org/rfc/rfc2812#section-2.2
  - crtasm 2y ago
    Interesting, thanks. utf8 appears to work out fine in practice though.
  - progval 2y ago
    The current IRC specification recommends UTF-8: https://modern.ircdocs.horse/#client-to-server-protocol-structure https://modern.ircdocs.horse/#client-to-server-protocol-stru... It is also possible for servers to tell clients only UTF-8 is allowed: https://ircv3.net/specs/extensions/utf8-only https://ircv3.net/specs/extensions/utf8-only . This is the default of some server implementations.

xboxnolifes 2y ago

> IRC is for people whose reaction to those is to complain or sneer about how they don't want them. This is the real reason IRC will never achieve wide adoption. The people who use it actively don't want the features that the people who don't do.

jodrellblank 2y ago
Don't want the features, and feel superior for not wanting those features: https://news.ycombinator.com/item?id=40813886 https://news.ycombinator.com/item?id=40813886

crtasm 2y ago

I see emoji on IRC every day btw :)

jodrellblank 2y ago
I'm sure you do see them, but having encodings consistent between sending client and receiving client isn't part of IRC; RFC 2812 - Internet Relay Chat: Client Protocol[1] says: > 2.2 Character codes > No specific character set is specified. The protocol is based on a > set of codes which are composed of eight (8) bits, making up an > octet. Each message may be composed of any number of these octets; > however, some octet values are used for control codes, which act as > message delimiters. > Regardless of being an 8-bit protocol, the delimiters and keywords > are such that protocol is mostly usable from US-ASCII terminal and a > telnet connection. Mojibake from disparate clients is part of the design; people have had to go outside the standard to make undocumented informally specified variation(s) such as "use utf8". Saying IRC is encoding-agnostic passing 8-bit bytes around, is like saying "I see emoji using TCP/IP every day". (Contrast with HTTP where a client can declare what it accepts in the request headers on a per-request basis, and servers can declare encodings they are sending in the response headers on a per-message basis. Contrast with proprietary Slack where one company codes every client and can make them all behave the same). [1] https://www.rfc-editor.org/rfc/rfc2812#section-2.2 https://www.rfc-editor.org/rfc/rfc2812#section-2.2
- crtasm 2y ago
  Interesting, thanks. utf8 appears to work out fine in practice though.
- progval 2y ago
  The current IRC specification recommends UTF-8: https://modern.ircdocs.horse/#client-to-server-protocol-structure https://modern.ircdocs.horse/#client-to-server-protocol-stru... It is also possible for servers to tell clients only UTF-8 is allowed: https://ircv3.net/specs/extensions/utf8-only https://ircv3.net/specs/extensions/utf8-only . This is the default of some server implementations.