It ' s California , of course they ' ll cheer for the more progressive option . <| sep |> Not talking about the R I mean I literally have 20 SSJ Goku cards <| sep |> sign me up <| sep |> I would love to see Your Name sinned seeing that it is the most contemporary <| sep |> Chromecast and fuck fast <| sep |> You ' re arguing that a terminal spec should NOT be used to transmit binary data that cannot be easily parsed by the player when displayed in some form . And my response is . WHY ? What is causing you to demand that all data that sent in a terminal layer must be easily interpreted by the player in ASCII or even codepage 437 form ? Why can ' t the terminal spec be used for binary data ? If the player is never forced to see it but alternately could if they wanted for debug purposes then why do we care ? Yes I completely understand that this is the normal purpose for a dedicated protocol . Keep in mind that this discussion is in the context of a required dedicated download client that we control anyway right ? So if we ' re in the context of our own open source client then the only question that remains has to do with how proprietary it is . If it is very proprietary and Nethack specific then it will likely never be used by anybody but Nethack players . Do you wish to define a VT 100 Z client spec that can be used by any Roguelike anywhere or do you wish to define a highly Nethack specific proprietary protocol that will never be used by anybody other than Nethack ?