Reconsider general access for the activities.write OAuth2 scope

[grilme99]

Hi team,

With the advent of the Discord Social SDK, developers can now update user presence through the Headless Session API by requesting the sdk.social_layer_presence scope. While this scope is useful for applications fully utilizing the Social SDK, it grants far too much privilege to applications that only want to update presence.

Currently, sdk.social_layer_presence is an umbrella scope that grants several permissions alongside presence updates, including:

• Connecting to the gateway on behalf of a user
• Reading and writing a user's relationships

Forcing developers to request read/write access to a user's relationships just to update presence violates the Principle of Least Privilege. It creates a security risk and results in a poor user experience. Users are very wary of granting "Friends List" access to simple tools, leading to high drop-off rates during the OAuth flow.

I am requesting that the Discord team make the granular activities.write scope available to all developers.

This scope is already used by high-profile applications but is currently unavailable to the general developer ecosystem. Opening this access would allow developers to build presence-focused integrations without over-requesting permissions, improving Discord's security posture and developer trust.