You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, Discord has two concepts in it's API: status (online/offline/dnd/idle/invisible), and activities (" is playing a game", etc.). Together these are referred to by Discord as the user's "presence".
Internally we mostly refer to Discord's "status" as a "presence", except in a few spots we've started to call it "status" again.
Especially confusingly, we consistently refer to Discords "activities" as a "status", which now collides with our own internal concept called "status", which makes parsing through this logic especially difficult.
These should be reconciled into a single concept, likely matching the Discord provided names as that will match both the API documentation for Discord itself and discord.py's documentation.
The text was updated successfully, but these errors were encountered:
Currently, Discord has two concepts in it's API: status (online/offline/dnd/idle/invisible), and activities (" is playing a game", etc.). Together these are referred to by Discord as the user's "presence".
Internally we mostly refer to Discord's "status" as a "presence", except in a few spots we've started to call it "status" again.
Especially confusingly, we consistently refer to Discords "activities" as a "status", which now collides with our own internal concept called "status", which makes parsing through this logic especially difficult.
These should be reconciled into a single concept, likely matching the Discord provided names as that will match both the API documentation for Discord itself and discord.py's documentation.
The text was updated successfully, but these errors were encountered: