-
Notifications
You must be signed in to change notification settings - Fork 4
Privacy settings #136
Copy link
Copy link
Open
Labels
Priority: MEDThis issue is of medium priority.This issue is of medium priority.Socket ImplementationStatus: TodoThis issue has been approved and needs to be completed/implemented.This issue has been approved and needs to be completed/implemented.Type: EnhancementThis issue contains a suggestion or improvement.This issue contains a suggestion or improvement.
Milestone
Metadata
Metadata
Assignees
Labels
Priority: MEDThis issue is of medium priority.This issue is of medium priority.Socket ImplementationStatus: TodoThis issue has been approved and needs to be completed/implemented.This issue has been approved and needs to be completed/implemented.Type: EnhancementThis issue contains a suggestion or improvement.This issue contains a suggestion or improvement.
Some users may not enjoy the idea of Quickplay collecting large amounts of client data (e.g. settings, UUID, Hypixel location, Hypixel rank, etc.) and sending it to the Quickplay backend. This can be resolved with a privacy setting. This may not require a protocol amendment (SetClientSettingsAction can be used), however it may result in unexpected bugs that need to be resolved within the socket and/or client.
Things that I think can be hidden from the server when privacy mode is enabled:
Things that I think cannot be hidden from the server when privacy mode is enabled:
Since most visibility checks are done client-side (with the exception of current server), this should not have a large impact on what displays and when. An impact will only be had if a new check is introduced server-side only.