Skip to content

Issues Existing Compression Algorithm #18

@infinitytmbots

Description

@infinitytmbots

The currently used ZSTD compression has been causing issues parsing insanely large (but essential) data from the web-socket. My bot has a guild with more than 400 channels and complex permission setup. The server data received via guildCreate event triggered on Ready was being trimmed no matter what.

  • I tried raising the read and write limits of the websocket. Didn't resolve the issue
  • Tried switching to accepting zlib encoding and changed the compression to zlib algorithm and this resolved the issue.

Perhaps an option in the gateway.toml to select the compression algorithm? Or a complete switch to zlib? Any of the above, I'll be more than happy to open a pull request with the changes.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions