Conversation

Notices

1. Embed this notice
   nyanide :nyancat_rainbow::nyancat_body::nyancat_face: (nyanide@lab.nyanide.com)'s status on Tuesday, 03-Jun-2025 15:23:51 JST nyanide :nyancat_rainbow::nyancat_body::nyancat_face:
   It says you shouldn't assume everyone uses ASCII
   
   ..then what the fuck should I do?
   • Embed this notice
     Tyler (tyler@nicecrew.digital)'s status on Tuesday, 03-Jun-2025 15:25:12 JST Tyler

     in reply to
     Utf32 moment
     nyanide :nyancat_rainbow::nyancat_body::nyancat_face: likes this.
   • Embed this notice
     nyanide :nyancat_rainbow::nyancat_body::nyancat_face: (nyanide@lab.nyanide.com)'s status on Tuesday, 03-Jun-2025 15:25:56 JST nyanide :nyancat_rainbow::nyancat_body::nyancat_face:

     in reply to

     Or, it doesn't? Where the fuck did I hear the initial thing from?

     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. Because of IRC's Scandinavian origin, the characters {}|^ are considered to be the lower case equivalents of the characters []\~, respectively. This is a critical issue when determining the equivalence of two nicknames or channel names.
   • Embed this notice
     T man :sex: :puffgiga: :puffpowerroll: (theorytoe@ak.kyaruc.moe)'s status on Tuesday, 03-Jun-2025 15:26:54 JST T man :sex: :puffgiga: :puffpowerroll:

     in reply to
     @nyanide is this from ircdocs.horse?
     nyanide :nyancat_rainbow::nyancat_body::nyancat_face: likes this.
   • Embed this notice
     nyanide :nyancat_rainbow::nyancat_body::nyancat_face: (nyanide@lab.nyanide.com)'s status on Tuesday, 03-Jun-2025 15:27:38 JST nyanide :nyancat_rainbow::nyancat_body::nyancat_face:

     in reply to

     • T man :sex: :puffgiga: :puffpowerroll:
     @theorytoe no a few years ago i read the rfc for c->s communication and i read that somewhere. i don't remember where
   • Embed this notice
     nyanide :nyancat_rainbow::nyancat_body::nyancat_face: (nyanide@lab.nyanide.com)'s status on Tuesday, 03-Jun-2025 15:28:31 JST nyanide :nyancat_rainbow::nyancat_body::nyancat_face:

     in reply to

     • T man :sex: :puffgiga: :puffpowerroll:
     @theorytoe sorry about the last post
     
     https://datatracker.ietf.org/doc/html/rfc2812
   • Embed this notice
     翠星石 (suiseiseki@freesoftwareextremist.com)'s status on Tuesday, 03-Jun-2025 18:16:05 JST 翠星石

     in reply to
     @nyanide You default to UTF-8 and optionally add a function that detects if a retarded encoding is used.
     nyanide :nyancat_rainbow::nyancat_body::nyancat_face: likes this.