Is your feature request related to a problem? Please describe.
I want to get the uses of a vanity URL, but there is no function for that.

Describe the ideal solution
Add a function Guild.fetchVanityUses() that gets the uses of a vanity URL, if any.

Describe alternatives you've considered
It is already possible to get vanity invites via `client.fetchInvite(server.vanityURLCod

Summary

sending a discord.File object through Messageable.send() changes the state of the file object.

Reproduction Steps

file = discord.File(io.BytesIO(my_bytes), filename='my_file')
await ctx.send(file=file)  # sends the file properly
await ctx.send(file=file)  # sends the file with zero bytes
await ctx.send(file=file)  # error

Expected Results

Sendi

Recently I've been getting unexpected 429s when executing webhooks at the limit, following the headers appropriately. When these happen, the previous header contains information that causes my application to expect it still has requests left (e.g. X-RateLimit-Remaining: 2), and then the very next request will return an error 429 with Retry-After: 43323 or some similar value typically between 4

Users are copying these samples, because, well, we're providing them as examples. We shouldn't be using ProjectReference to set up the dependencies.

For some odd reason when trying to get the vec of mention_channels from Message, it will return None if there is other text in the message. If there is no text in the message and only a channel mention, then it will return.

The youtube tutorial in the Wiki is deleted and I cant check to see if I have done all the steps correctly

If you can please show me a video of the tutorial, Thank you!

Proof

According to the traffic stats for this repo, people really like to check out the examples - it's third place in the list after the main repo page (i.e. github.com/meew0/discordrb) and the main wiki page.

Given the need to fulfill the role of what is essentially the repo's poster child, the examples are disproportionately spartanic. While there are six of them, they don't show off every aspect of

Our download methods are currently no consistent.
In some places like Icon we have #asByteArray(), #asInputStream(), and #asBufferedImage() but in other places like MessageAttachment we have #downloadAsByteArray(), #downloadAsInputStream(), and #downloadAsBufferedImage().

To the best of my recollection, and as documented, bot developers and community library developers have been encouraged to implement a stateful connection to Discord's gateway to supplement and minimize usage of the HTTP API. In doing so, developers

The number one historical issue with Disco has been a lack of quality documentation. This issue mostly stems from my particular disdain with the Sphinx documentation engine and the lack of consistency with docstrings in Python projects. I originally attempted to build biblio--a custom documentation engine--as a soluti

While the lib doesn't currently support voice, it would still be proper to handle voice state updates. The logic to do so should be here, and the docs for it are here.

The voice server update event should also probably be implemented. A

This is also affected by #275

📢 Suggestion proposed by Profxy (246708789930229761)

What is the title of your suggestion?
what our costumers say

Explain your suggestion more accurately (It's best to give as much information as possible, so that we can implement the suggestion better)
the section "what our costumers say" on the first page of the homepage shouldn't be translated. It's better if they stay in the origin

Hello,

Just wanted to know if you were planning to do either a wiki page or a little documentation website to make the lib easier to use.
If not (which is understandable as this takes time), are you planning to maybe create a discord for the community ?
If such things already exists, sorry that I didn't found them.

Pretty much everything listed as needing documentation needs to be added. As time goes on I fill it out slowly.

discord/discord-api-docs#1574 (comment)