Allow bots to access the /premium/subscriptions endpoint

[kernel-dev]

As it's most likely already known, there's an endpoint which allows you to view which members boosted the guild, and how many times.

• guilds/<guild_id>/premium/subscriptions

Sadly, this is a user-only endpoint, however I wonder if it'd be a good idea to open it up to bots;
I, personally, would like to retrieve this sort of data for my bot, but sadly cannot. I'm not entirely sure how many other individuals agree here, or are in the same situation. The only work-around for this would be to use a user token and create a request to the previously mentioned endpoint; but I believe that's breaking ToS.

Definitely seems like a useful endpoint, in my opinion. It's a shame it's restricted to users.
Please take this into consideration if the idea isn't ridiculuous!

[0x57e11a]

Would be very useful for bots to be able categorize users based on boost count, boost length, etc, etc.

[LikeLakers2]

This seems like a (potential) duplicate of #1182. I'd recommend showing your support over there if you have anything to add to that discussion.

See also #1172, which has some other relevant discussion about the booster role.

[kernel-dev]

Well, I can definitely see the "concern" to the subject of a duplicate issue, but I believe the former (#1182) is mainly focused on providing a single property which is to display the amount of boosts a member has given to a guild.
However, the issue I'm opening up is to mainly focus on completely opening up the mentioned endpoint to bots so they have access to all relevant data concerning a guild's boost status; each individual [boost] id, for example.

[Octolus]

How's this not a feature?

I want to give boosters special privileges in the server. For example if they boosted 3 times, they will get access to a custom bot.

[kernel-dev]

It has been a hot minute since this issue has been relevant - but it seems to have been resolved as Fyko had shown here.

[advaith1]

no, that's been available (and documented) for a long time, but does not resolve this feature request

[Pandapip1]

Any update on this?

[generalwrex]

how about 2 years later?

[erkinalp]

I have possible explanations about why this is not done.

• This would open a way to promote boosting (in certain jurisdictions, unpaid promotion of third parties are not allowed)
• This would enable spam advertising to promote boosting

Both of which are unwanted outcomes.

[Pandapip1]

This is what the ToS and Community Guidelines are for!

[TwilightZebby]

This is what the ToS and Community Guidelines are for!

Yea, and we all see how that's turning out with Mee6 🙃

[Pandapip1]

Yea, and we all see how that's turning out with Mee6 🙃

Take that unrelated issue up with Discord. If Discord cares about malicious use of the endpoint, they will enforce their ToS. The issues with Mee6 are completely unrelated and are due to preferential treatment, NOT due to any lack of enforceability.

[gamer0mega]

You can already see that a user boosted the guild by checking the premium_since property of the member. Correct me if i don't get the point.

[ftilly]

You can already see that a user boosted the guild by checking the premium_since property of the member. Correct me if i don't get the point.

Exposing boost amounts to propagate, and premoderation are deleted almost immediately and users who have IDs of bot's data handling at the lazy guilds to choose between high latency control the back-end.

[ftilly]

Also to be a trust issue for end users with something closer to have any other users. This best current practice requires that users from allowing them amounts of Discord function more activity than text messages. This intent should be enabled for people who have even block Discord guild. That could abuse by Discord, resulting in to removed channels and the pending member caching requirement is required to message is the limiter to removed from being used.