Integration limits too restrictive for activities

[mxcabre]

Description

I manage a large server with over 30,000 members, where voice activity is highly active. To meet the demand for various activities, we manually added 30 different activities to avoid relying on external applications USE_EXTERNAL_APPS.

However, this has led to three significant issues:

1. Manual Setup Challenges
   Adding activity integrations manually (non-bot) is cumbersome and time-consuming.

2. Integration Management Issues

   • The "Integrations" panel in the server settings becomes cluttered as integrations pile up.
   • Third-party bots can't manage integrations beyond their own, making configuration more complicated.
   • The user experience is poor, with no way to filter or organize bot-related activities.

3. Integration Limitations

   • The 50-integration cap is too restrictive, preventing us from adding more trusted activities.
   • Enabling the "External Apps" permission is too risky for large community servers. Members often find creative ways to misuse external apps and activities they create.
   • Bots have no control over activities launched in voice channels, making it impossible to moderate or block inappropriate activity launches.

Steps to Reproduce

N/A

Expected Behavior

Adding activities should not count towards the integration limit. Most activities do not have additional slash commands.

Current Behavior

The 50-integration limit is restrictive and prevents us from adding new activities.

PS: While 50 may seem like a lot and initially felt generous, it quickly becomes insufficient on a server with 300 different active voice members daily, each preferring different activities. With 15 bots already on the server, the integration cap is reached much faster than anticipated.

Screenshots/Videos

No response

Client and System Information

N/A