Make it possible for bots, to check if user has nitro, is in hypesquad, is staff, etc.
Suggestion is simple: Make it possible for Bots, to actually see, if a user has nitro (if yes probably also what kind of nitro), is in HypeSquad (And perhaps what type/house), is a official staff, is partner and what else could be seen as a badge on the users profile.
There is the User object (user structure) which already provides this info. But (at least as I understand it) is that behind a different OAuth2-scope (identify), which can't be used by a bot, or at least only through some changes in code and/or the link?
I know that this could give potential for abuse (like only allow users with nitro or a certain HypeSquad house to join a guild), but lets be honest: What on discord's API doesn't give a potential for abuse (And maybe is already abused?)
This would give Bot-developers a really nice way, to f.e. show custom badges/emotes on a Embed with user-info, or tell others if someone of the mighty staff-team joined the guild (Which could be possible).
Would be cool by one sense, abusable in another. Imagine bots immediately banning anyone who isn't in X HypeSquad house instead of Y.0
This endpoint already exists. See "flags"-1
The issue with that is, that it needs you to have a special 2OAuth setup/link in order to even receive the info (See how it mentions "Identify" in the "Required OAuth2 Scope" area, which according to the OAuth2 page is a seperate setting(?)
My feedback was for making it usable by bots, I updated my description a bit to make it more clear.
Isn't that already the case with bots out there? This would (of course) make it worse, but it wouldn't start this "fight", There are 145+ million users out there (And I have no idea if that already counts bots) and the chance that there are bots which "abuse" certaing things is almost always 100%.0
Already possible. Read the API docs.-3
Oauth2 is "useable" by the bots and ``What on discord's API doesn't give a potential for abuse`` is a really bad argument. There is a reason why it requires an additional scope like for email, list guilds, connections or invitation.-1
I believe this is already possible.-1
Discord added public_flags which is pretty much what I requested, with the exception of specific badges like nitro which is perfectly fine for me.1
They also added premium-type which shows if they have nitro.0
Yes, but bots currently cannot access user profiles. It is documented, but bots cannot use it. Only proper Discord users can access the profile endpoint.The https://discordapp.com/api/v9/users/958158495302176778/profile endpoint can only be accessed by using a user token.The https://discordapp.com/api/v9/users/958158495302176778 endpoint can be accessed by using a user or bot token.0
Please sign in to leave a comment.