Amount Of Server Boosts

[Skillz4Killz]

Hello 👋

Would it be possible to show how many boosts a member has in a server? I wanted to use Server Boosting as a way to unlock VIP features on my bot but I can only reward each user a maximum of 1 server VIP unlock because I can't tell how many boosts they are giving.

Recently, Server Boosting allows as many boosts as you like, this means a user could boost my server 3 times and so I want to allow them to have 3 servers with my bots VIP features. This would encourage more users to give more boosts which means more money in Discord, more cool server perks for me and my users get cool bot perks in their servers. It is a win, win, win.

Only having a timestamp showing when they became a booster isn't really helpful besides telling me that they are boosting. It's basically just a boolean at that point. An integer showing how many boosts a member has given would a perfect.

Thank you.

[NovusTheory]

Just a small comment to add. This could go hand in hand with giving bot access to https://discordapp.com/api/v6/guilds/GUILD_ID/premium/subscriptions as it contains all the boosters for a server and includes a user multiple times if they have multiple boosts applied.

I would like to think of this as unlikely and assume Discord will just add a premium_count to the guild user object.

[msciotti]

Just want you to know this is being discussed internally. We intentionally haven't put this in the API (or in the client) because of some negative behavior we thought could arise, such as people being targeted for boosting/not boosting/how much they boosted. We unfortunately saw some of this behavior in the original launch as well.

Raised this again today—just so ya know!

[fhebuterne]

@msciotti Do you have any news ? I've created a topic on discord forum, some other users and me are very interested by this feature : https://support.discordapp.com/hc/fr/community/posts/360056250092-Add-information-to-see-who-boosted-server-twice-on-UI

[bartico6]

@msciotti Any updates on this?
Also, is giving people additional roles (as a token of gratitude, of course) for boosting a given amount of times negative? Is synchronizing boost status/count to, say, a game server, considered negative?

Could the negative behavior problem be solved by allowing users to hide their boost count (or, even, the fact they're boosting at all!) on a per-server basis, and give bots & admins an endpoint that allows them to view people who have their boost status shown? (this would require the role to be removed/reapplied to boosters when they toggle that setting, though)

Technically speaking the problem of potential "targeting" for the fact of boosting already exists, through:

The sidebar icons

The notifications

in fact the notifications reveal the boost count anyway lol

The role itself

so you could combine opening up the API for querying who has boosted & how many times with allowing people to hide the fact they're boosting completely.

I also am not sure I understand the concern. Is the worry that admins will bother their boosters, or that non-admins will bother boosters?
For the former, it's a difficult issue to solve authoritatively since it should be the user's choice to leave the server if they're being targeted by staff, and honestly it sounds like the kind of thing you should be encouraging. Servers with abusive staff generally die out so it should be a problem solved by way of natural selection.
For the latter, a role permission could be included to toggle ability to "view boosters", allowing admins to set up who can see boost statuses (such as admins, moderators, maybe other boosters?) eliminating the "non-boosters poking fun at boosters for spending money" factor completely.

If the issue is that owners/admins/mods will "beg for boosts" - it's already the case. It's heavily rewarded by the platform so everyone wants it and everyone asks for it.

[stevenobird]

Like @bartico6 mentioned, Server Boosting is quite present in servers that are using it, and boosters are visible in many ways on the client side.

So I honestly cannot imagine why such an information is kept secret on the API side.

[msciotti]

While I appreciate the suggestions for all the granular permissions around visibility of boosting in our API, that is frankly a bit too intensive for what needs to happen here. I think it's also rather important to remember that bots aren't users and don't operate at the same scale. Yes, a given individual could go through the "Nitro Boosting" rank of a single server and bother them for some reason, or the opposite and DM a bunch of non-boosters begging them to boost.

However, you're talking about one person taking a lot of time to do this at meaningful scale. A bot that's in a couple thousand servers could—and I'm speaking purely in worst case scenario hypotheticals—do it all day, every day, for every person in that server (respecting our rate limits, of course).

That being said, I will raise this internally again. It is very unlikely that we put robust permission sets in our API around visibility of boosting. It will either be that we are comfortable exposing it in our API, or we are not.

EDIT: Scratch what I said, I was misreading my own API docs. Considering that we do expose premium_since in the docs for a boolean boosting/not boosting, what I said is rather irrelevant. I've raised it again, though it will be in the hands of the time that works on our Nitro and boosting stuff to decide.

[Octolus]

Looking for this, is it not available?

[AruMoon]

Need this feature

[GolfingSuccess]

I would really like this feature as well. The problem with @bartico6's remark is that Discord doesn't show how many times a user has unboosted, so a bot can't just determine the boost count from those messages.

[DigitalCommodore]

Why is this closed? At the moment, you offer bots partial boost monitoring functionality and a user full functionality. If you were concerned about users being unfairly targeted, that was a discussion for when you guys decided to give a system role, server notification, and a badge to users who boost, wasn't it?

The current implementation is as though someone did the work for users, and wandered off halfway through implementing it for bots.

[GolfingSuccess]

@DigitalCommodore It looks open to me...

[DigitalCommodore]

Oh, hell. That's what I get for getting grumbly before I'm done with coffee -_-

[cheesycod]

This isn't needed. Just look at all members with the boost role. It's harder but it's doable.

[Skye-31]

That only says that they have boosted once. What if a user has boosted multiple times? That information just isn't revealed. Also, at time of this issue creation, there was no guarantee which role was a booster role (before role tags were released).

[bartico6]

This isn't needed. Just look at all members with the boost role. It's harder but it's doable.

Even though the role tag exists to determine "boosting or not", it's already possible as part of the user json (premium_since) as @msciotti said - determining the exact number of boosts from a given user still isn't possible via API, but it should be - that's the point of this issue.

[sudofox]

You should really find another place to express this particular view. This card is not about anonymous boosting. It's about getting the number of boosts, per user, programmatically, information which has never been private in the first place. If you think that Discord should add anonymous Nitro Boosting then by all means, put in a feature request! I won't stop you.

However you are at this point distracting from the purpose of this issue. Such a change to the API would not make any previously private information public. It would enable server owners, who have added their own bots under their control, to poll boost counts for whatever reason they'd like to do so.

[erkinalp]

It's about getting the number of boosts, per user, programmatically, information which has never been private in the first place.

And I am trying to explain you all that retrieving them at human scale and rate and bot scale and rate are not the same things. You get a significant hit in your second order privacy in the latter case.

[HilbertGilbertson]

And I am trying to explain you all that retrieving them at human scale and rate and bot scale and rate are not the same things. You get a significant hit in your second order privacy in the latter case.

I don't see what that has to do with this issue. In any case, you initially used this thread to propose even deprecating the Nitro Booster integration role - are you really going to suggest that wasn't outside the scope of this issue?! Evidently you have a gripe about boosting and privacy (including wanting to remove even the Nitro Booster role), and you are suggesting fundamental changes in the way that boosting operates, which is not the purpose of this thread. As @sudofox so eloquently explained above, this feature request concerns a very small change to allow data that is already public to be read by bots. You are intervening to argue that the data should not be public in the first place, and want changes that go in exactly the opposite direction.

If you want to argue for an overhaul of the way boosting works, deprecation of the integrated role, anonymous boosting and public boosting, etc, then by all means go ahead. You can open your own feature request where you try and justify it. You can even reference this issue if you feel that it is vaguely related. But this is becoming off topic and unprofessional.

Back on to the issue at hand...

I hope that, over a year having passed since the last update from @msciotti, we can receive a follow-up soon. I would very much like to know whether this request has received any further consideration. As I expressed above, and as many here have sought to demonstrate in illustrating their proposed implementations, the practical benefits (of enabling bots to know how many boosts a user has contributed to a guild) really seem to outweigh any speculative harm. Hopefully the relevant team is able to reach the same conclusion.

[charlieTheBotDev]

Just want to cover this because I don't think it was that explicit.

The fact that there is an endpoint inaccessible to bots that has this information means that any malicious use of this information is already possible by simply loading the data client-side or self-botting (yes, this is against ToS but abusing the data would be as well so why wouldn't they do this too?)

Effectively that means that malicious users already have access, yet legitimate users do not - which seems crazy to me.

I think the privacy concern of someone else's bot on my server having access to this data would be mitigated by adding an explicit permission/server intent to disallow their access to the endpoint (as with the likes of 'View Channels' for instance) which would be disabled by default for all existing bots

Considering all this, and the fact it would be such a trivial change to the API, it's a bit weird that this ticket is still outstanding

[erkinalp]

adding an explicit permission/server intent to disallow their access to the endpoint (as with the likes of 'View Channels' for instance) which would be disabled by default for all existing bots

Yes, I defended that, with an additional guild-granular ability to hide boosts on the user's side. But that per-user setting is crucial, otherwise millions of users will leave Discord, observing that their payment history is open to uncontrolled data mining by bots. There is a reason many people, including a computer engineer like me, use cash in many day to day payments.

[sudofox]

@erkinalp I'd like to make you aware that your continued not-relevant comments here are disrupting this thread. While it may seem that we are against your ideas and your principles for privacy, we aren't. The reason why you continue to receive a negative response is that you're posting them in the wrong place.

We understand that you have issues with the core design of Discord Nitro and Boosting, which makes information like whether or not a user has Nitro and how long they've had it available, as well as whether they're Nitro Boosting (via the profile badge), and that the current design of the feature makes these things visible to other users in a way akin to cosmetics or rank on a Minecraft server.

There are many spaces where you can debate this. But what is not up for debate is that these features are already implemented in a way that makes this information already public. Nitro Boosters make up a very small portion of overall server populations. Bots would have to be in all the servers the user is potentially boosting to even form sizable datasets, and the biggest bots already have to go through a specific vetting process for certain data access above x number of servers. The changes requested in this card would not make any difference in what's accessible.

I have one last point to make: the change from "is nitro boosting" to "has x active nitro boosts" does not reveal any payment history. It's just an integer and it is specific to user's relationship with the guild itself. Furthermore, there are many ways to get Nitro that don't involve the user actually paying for them, chiefly the "Gift Nitro" feature which Discord feels is so important that it needs a button directly next to the file/image upload button in the mobile app UI. Also, there's no way to tell which kind of Nitro they have: regular or classic. Same badge for both. Therefore there is no definitive way to tell if the user is paying Discord or not, or even how much they're paying.

Please feel free to continue championing your proposed design for a privacy-centered Nitro. But take it to a forum where it's relevant. That's all we ask.

[kerryphisher]

I would like to know how many times a user has boosted a server.

[erkinalp]

chiefly the "Gift Nitro" feature which Discord feels is so important that it needs a button directly next to the file/image upload button in the mobile app UI

Gifts should also be user specific, and users should be able to disable gift reception, without the gifter knowing.

[GolfingSuccess]

chiefly the "Gift Nitro" feature which Discord feels is so important that it needs a button directly next to the file/image upload button in the mobile app UI

Gifts should also be user specific, and users should be able to disable gift reception, without the gifter knowing.

Those are all valid opinions; however, our point is that you should voice them in a relevant discussion, or create one if there's not one already.

[kerryphisher]

If Discord allowed bot developers to identify how many times a user has boosted a server, we could incentivize that; we would make Discord more revenue.

[wolfdev1]

Yep

[kerryphisher]

These Discord discussions are just graveyards for ideas which should be obvious to a software designer. When Discord is long dead, we'll still be able to come back to these threads and see in clear black-and-white why the company went under.

[TwilightZebby]

These Discord discussions are just graveyards for ideas which should be obvious to a software designer. When Discord is long dead, we'll still be able to come back to these threads and see in clear black-and-white why the company went under.

@akirablaid

Sorry to be that person, but comments like this aren't helpful to anyone. Discord is well-known for actually listening to it's userbase.

May I suggest constructive criticism instead of "this should be obvious". For instance, what don't you like, why don't you like it, and how could it be improved? Or even what do you want, why do you want it, and any ideas for how it could be implemented/behave.

Also, don't forget that things may have a different priority level then others.

If this comes off as a little aggressive, then I apologize as that's not my intentions. :)

[stevenobird]

Has this topic been discussed internally since this issue/thread appeared?
It seems that no one of the Discord team feels responsible for this or does not want that "feature" to happen.
Would be nice to know if this is considered to be added or never to come.

[SCDerox]

Any updates on this?
It would be great to at least know if this feature got declined internally or if it will be added at some point.

[DaInfLoop]

When is this gonna be added? I've seen that users have an endpoint for that in this discussion, but it isn't for bots? May aswell self bot that data (not that I am going to, but some people may do this as a last resort)

[wolfdev1]

Thnks

[badjujubes]

the boost Server Settings page fetches its data from an endpoint that returns all of the boosts and their users and expiration dates, so that endpoint would serve this purpose. for creator tier subscriptions they probably want servers to use role subscriptions instead of boosting.

Is there any chance you'd be willing to explain like I'm 5 how to do this? 😅 I tried checking the Network tab on my server's "Server Boost Status" page, but I'm not really sure how to access/read said endpoint to retrieve this information.

[BuildBot42]

the boost Server Settings page fetches its data from an endpoint that returns all of the boosts and their users and expiration dates, so that endpoint would serve this purpose. for creator tier subscriptions they probably want servers to use role subscriptions instead of boosting.

Is there any chance you'd be willing to explain like I'm 5 how to do this? 😅 I tried checking the Network tab on my server's "Server Boost Status" page, but I'm not really sure how to access/read said endpoint to retrieve this information.

Go to https://discord.com, login, open the Web Inspector, go to the Network tab. Right-click on any server that you have the proper permissions in and that has boosts applied to it, mouse over to Server Settings -> Server Boost Status. Once it's loaded, search the Network tab for "subscriptions" - there should be a request labelled as exactly that to /guilds/{guild}/premium/subscriptionsthat returns an array containing all users that are currently boosting & their respective data - go to the "Response" tab to view this data.

For clarity: this endpoint is not currently supported for bots. If you're hoping to access it programmatically, you're out of luck.

Hope this helps!

[badjujubes]

the boost Server Settings page fetches its data from an endpoint that returns all of the boosts and their users and expiration dates, so that endpoint would serve this purpose. for creator tier subscriptions they probably want servers to use role subscriptions instead of boosting.

Is there any chance you'd be willing to explain like I'm 5 how to do this? 😅 I tried checking the Network tab on my server's "Server Boost Status" page, but I'm not really sure how to access/read said endpoint to retrieve this information.

Go to https://discord.com, login, open the Web Inspector, go to the Network tab. Right-click on any server that you have the proper permissions in and that has boosts applied to it, mouse over to Server Settings -> Server Boost Status. Once it's loaded, search the Network tab for "subscriptions" - there should be a request labelled as exactly that to /guilds/{guild}/premium/subscriptionsthat returns an array containing all users that are currently boosting & their respective data - go to the "Response" tab to view this data.

For clarity: this endpoint is not currently supported for bots. If you're hoping to access it programmatically, you're out of luck.

Hope this helps!

Thank you so much! We have a relatively small server (only about 20-30 boosters), so being able to calculate this manually at least works for us.

I hope in the future Discord finally implements this on a level that bots can access/manage!

[Droid00000]

the boost Server Settings page fetches its data from an endpoint that returns all of the boosts and their users and expiration dates, so that endpoint would serve this purpose. for creator tier subscriptions they probably want servers to use role subscriptions instead of boosting.

Not to be a prick, but will this endpoint ever be accessible by bots? It’s been years since there’s been any “official” response or acknowledgement that this is still being considered.