Skip to content

Server relies on ID packet to determine client features #387

@mposs00

Description

@mposs00

This is a bug. Client capabilities should come from FL, not ID. This breaks the semantics of ID when the client is not AO2. There is 0 reason we should be parsing this and validating it to be a valid AO2 version.

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