Skip to content

ISUPPORT value escaping/unescaping #27

Description

@DanielOaks

I’ve always sorta ignored it as unsupported but if servers are sending values escaped that way (esp for spaces etc) it makes sense to have consistent implementations of it and all.

note to self: don’t mandate converting all utf-8 chars to the escaped forms, I could def see servers just using the encoding opportunistically for mostly stuff like e.g. space that’s not possible to represent b/c protocol limitations and junk, e.g. https://github.com/inspircd/inspircd/blob/6cfabb0/src/server.cpp#L176-L182

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions