Arctic Examples: Discord Does not allow "activities.read" scope for OAuth flow

[uerkw]

On the Discord example for Arctic, it suggests providing the following scopes:

const scopes = ["email", "activities.read"];

However, using the activities.read scope in the OAuth flow will always return an "Invalid Scopes" error in the callback URL.

Reading the relevant Discord Documentation, we can see that for activities.read : "allows your app to fetch data from a user's "Now Playing/Recently Played" list — not currently available for apps". While it is currently not allowed for "apps" with OAuth, I don't believe this scope is necessarily used by Arctic or Lucia for anything, and my application works with using just the identify scope to grab the discord ID and username of the client that is logging in.

[pilcrowonpaper]

The example is just an example, not a recommendation. It's just intended to show how scopes are passed to Arctic.

I'm not exactly sure what "not currently available for apps" means but it seems your app needs to be whitelisted by Discord to use it? (discord/discord-api-docs#1178)