Skip to content

Instantly share code, notes, and snippets.

Embed
What would you like to do?

The Future of discord.py

If you're looking for a tl;dr, you can check the FAQ.

Greetings. If you don't know me, I'm Danny. I'm the core (and sole) maintainer of the discord.py library. Contrary to popular belief, I am actually not a Discord employee. In fact, I'm not even a professional programmer. In reality, I'm a medical professional who works at my local hospital. Despite all that, I do enjoy programming as a hobby and have worked on discord.py on my own free time.

I've been working on discord.py for about 6 years – a rather significant portion of my life has gone into maintaining this software library completely for free. I have never accepted donations. I have never asked for donations. This library has been my passion project, born completely out of a desire to see more bots on Discord written in Python. Over the years, many users of my library have told me that discord.py changed their lives. It empowered them to challenge themselves, create fun things, and find new opportunities. As someone who has always valued educative, open-source projects, it means so much to me to know that discord.py has had a positive impact on people's lives.

Unfortunately, today marks the end of my involvement in the project. Therefore, effective immediately, I will be stepping down as maintainer of the project. I asked the contributors that I trust if they wanted to take over the project, but no one accepted. Essentially, this is a unanimous decision that the discord.py project will be ending. The code remains open, so if someone wants to fork it and work with it, then they are free to do so. However, mainline development will cease as of today.

I want to assure you that this was not a decision made lightly. My hope is that this document explains my thoughts and the process leading up to the decision. I've also written an FAQ if you just want a quick rundown.

Grassroots Movement

I joined Discord on August 10th 2015. I had friends who recommended Discord to me, and we wanted to move our tournament operations from IRC/Skype over to a new platform due to excessive grievances with those platforms. The first time I used Discord I was pretty impressed; however, for me to move on to it, we needed an API for my bots to function. Unfortunately, at the time, there was no "official" API. Luckily, I had found an API wrapper by the name of node-discord and used it. This API wrapper was very minimal, only containing a debug event that dumped the gateway messages (at the time, v2) and a message event that was special just for messages. This experience got me really interested in figuring out how the API worked. I made my bot, R. Danny, the very next day (August 11th) and invited it to the r/Splatoon server.

I wasn't completely satisfied with the node-discord package nor with using EcmaScript 5, so I took it upon myself to start reverse engineering the API myself using Python. At this point in time, all the early members of the bot and API ecosystem resided in a server called Discord Developers, a different server, however, than the one that goes by the same name today. In this server, we had a lot of Discord enthusiasts and Discord employees, much like today's newer Discord Developers server. Of these people, there were people like izy521 (the creator of the aforementioned node-discord) and Voltana. We were talking about the Discord API and reverse engineering it until eventually all of us like-minded individuals made our own server called Discord API, owned by Voltana. This happened on August 13th, very soon after my own registration.

I continued working on my API wrapper, aptly named discord.py, along with the others who had made their own libraries such as Discord.NET, discord.rb, discord.js, discord4J, etc. Together, we reverse engineered the API over the next few months with no documentation to help us. Our little ecosystem thrived and lots of bots were made. Eventually, Discord themselves wrote a blog post detailing our adventures to get more people to use our libraries. There was a lot of hope and excitement about the future of Discord bots. We were promised many things! The future was going to be bright; we were going to get slash commands, webhooks, "channel observers", proper voice support, etc.

As time went on, Discord realised that the traditional approach of inviting bots by invite crawling was problematic. To combat this abuse vector, Discord decided to ramp up their interest in the API and made official Bot accounts that could only be invited via OAuth2 and not through the traditional invite scraping mechanism. This was considered a good change for privacy and started the hopeful beginning of Discord investing in their API. We were promised many exclusive features for bots, though our first and only feature at launch was the ability to join voice channels across many servers. The official bot API was released on April 8th 2016.

Neglect

When Discord unveiled their official API back in 2016, many promises were made about features that would be implemented. Unfortunately, most of the things we were promised never ended up materialising. When we asked the Discord employees about the state of the API, they always mentioned that they lacked the development resources required to work on the API and that it made no business sense to prioritise or work on the API platform. This was completely understandable since Discord was, at the time, a small company with a lot on their plate. However, this lack of priority meant that the API languished over the next 3 years. There was growing frustration within the Discord bot community that we weren't being listened to.

Our Discord API server was originally a place where Discord employees and library developers could discuss changes with one another. Our server was not without drama, nor was it perfect. Some Discord employees left due to this drama, and some never spoke much to begin with. Despite all of this, our Discord API server was the central communications hub between Discord employees and library developers. It was the main place where library developers could gain insight into upcoming changes and provide feedback. Over time, the number of Discord employees willing to engage with us library developers dwindled down to two: Jake and b1nzy. We often joked that the two of them were our last hope, as they were the only Discord employees that showed any genuine interest in listening to and acting upon our feedback. Unfortunately, b1nzy left Discord and Jake became increasingly busy with other areas of the app, so our disconnect with the internal Discord team only continued to grow.

It wasn't until around November 2019 that Discord started focusing more of their resources on their bot development platform.

The Discord Infrastructure Server

While our communication suffered, a different, more private server was getting more attention. This server was colloquially known as "dinfra", short for "Discord Infrastructure". Originally, the purpose of this server was to share infrastructure status with the bigger bot developers to give them a heads-up on when things might be turbulent. However, the goal of this server morphed into being a semi-official way for big bot developers and Discord employees to communicate about the future of the platform.

It should be noted that this server did not have many library developers within it, so we were mostly blind to what went on in that server. Only two library developers were invited and only because they also helped with the development of big bots. They were not there for their role as library developers. Discord employees gradually began to discuss API changes in the Discord Infrastructure server instead of in our Discord API server. Discord no longer kept us library developers up to date on proposed API changes, or gave us much of an opportunity to provide feedback. Luckily for us library developers, we had a few "moles" in the Discord Infrastructure server who were willing to exchange information with us so that we could obtain information on upcoming changes we would need to accommodate.

One such change was the introduction of a feature called guild_subscriptions, which was a way to reduce the bandwidth of a large bot by opting out of PRESENCE_UPDATE and TYPING_START events. These events typically made up around 95% of a bot's bandwidth and CPU usage, and it was a common feature request to remove these events from showing up in the gateway event stream. Unfortunately, this boolean toggle came with the caveat of also turning off member-related events, and it was undesirable for a lot of bots. A better system needed to be made. This system became known as intents.

Privileged Intents

Around December 2019, there were discussions about a new feature named intents in the Discord Infrastructure server. The goal of this system was to have a more granular approach in disabling events that so many bot developers had hoped for. This change would, presumably, be backwards compatible with the way things were done at the time. Unfortunately, at the same time, there were growing concerns with a user-bot ring that made a website and scraper known as "dis.cool", which farmed user information.

Discord presumably saw this growing user-bot ring as a liability threat and introduced the concept of "Privileged Intents" and discussed the plan with the Discord Infrastructure server, again without consulting library developers about it. My mole in the Discord Infrastructure server then gave me a gist of the original plan for privileged intents. It became clear that this was not the feature that we had been requesting for years, but rather that they were added restrictions that were created due to a false equivalency between user-bots and real bots.

At this point, I had asked the Discord employees what intents were, and they retorted by asking me where I had heard of such a feature – implying its secrecy. Hoping to not give away my now primary source of information, I did not indulge too much information on the source. However, eventually the Discord employees divulged and gave us a quick rundown of the basics of the concept. The next day, they gave us the same gist and talked to us about it.

The original specification of intents only had PRESENCE_UPDATE as the privileged intent. For "large bots" over 100 servers, this would block your ability to join more servers unless you explicitly requested approval from Discord or turned off the intent. At the time, the whitelisting process would amount to a checkbox and a text box that you would fill out to give Discord a rationale on why you needed it, optionally attaching a video showing your bot's usage of the feature.

Most library developers and contributors were not happy with the changes, since the way bureaucracy historically was handled at Discord would mean that the bot would silently break while waiting for a response from Discord. At the time, the large bot sharding system that bots in over 250,000 servers had to apply for was already behind, so there were growing concerns about the effect bureaucracy would have on our bots. We were promised that the system would be fine and that the bureaucracy would not have a negative effect.

There were significant arguments from both sides over whether the privileged intent system accomplished anything. Most library developers felt the changes were misdirected and targeted the wrong type of bot. The threat model was based on user-bots being bad actors, and not regular bots, while the changes targeted regular bots. We also felt that it was easy to sidestep the restrictions by just having a bot ring, similar to what is now done today with user-bots.

Discord repeatedly mentioned that the 100 server threshold would have minimal impact and that most bots were not past that limit. To us, large bots are bots well over 100 servers and into the 100k+ territory. At the time, the PRESENCE_UPDATE event was heavily overloaded, providing not only presences and statuses but also user level updates (such as name, avatar, and discriminator) as well. We were told that before the change went live that they would split it, and that was indeed done in v8 of the API, 10 months later.

After a lot of discussion with the Discord employees with them telling us that they were listening to our feedback, they decided that the GUILD_MEMBERS intent was going to be privileged as well. The GUILD_MEMBERS intent is the intent that controls whether you get member information over the gateway and is the heart and soul of how member level events are dispatched via libraries. This intent is also required for any local caching of members. At the time, there weren't enough events that provided the member data, so this meant that usability of every library across the board would suffer. The Discord employees maintained the opinion that this change would be a net benefit and that the bureaucratic aspects of it would only be two text boxes and checkboxes that anyone could fill out.

There was a lot of uproar over this addition, not just within the Discord API server, but also on GitHub. To this day, that GitHub pull request has the most discussion out of all the issues and pull requests for the repository. This was because, at the time, member data was necessary for a large amount of functionality within the API, such as checking permissions and moderating. Likewise, the Discord employees claimed that the blowback to the bureaucracy would be minimal and that all the bots would be verified within one day. They also claimed that in the future, member data should become unnecessary. The deadline for conforming to these changes was October 27th 2020. The date of the introduction of this intent was February 3rd 2020.

They assured us that they were listening to our feedback.

Verification

After the large amount of discussion involving privileged intents, taking place over the course of around 3 months, most of the library developers, contributors, and Discord employees were drained from the conversation. As a result, after this, communication with us went essentially radio silent. We hadn't spoken to any Discord employees about anything, except a sneak peek of the allowed_mentions functionality early in February, slightly after the initial blowback.

We didn't find out what Discord planned on doing until they unveiled their plan for the future in a blog post on April 7th 2020. In this blog post, the Bot & API Team unveiled their future vision for the platform by showcasing Figma examples about how they hoped to have bots integrated within the ecosystem. There were many concepts shown, such as context menus, buttons, and ephemeral messages. Many of us were finally excited for the changes to come.

Unfortunately, along with the news about the future of the platform came a caveat about additional restrictions to the platform. No longer would we have to fill out just a regular two text and checkbox form, but instead an entire questionnaire would need to be filled out. On top of this, a government-issued ID would need to be provided in order to verify your bot to receive a verification checkmark on it, along with a profile badge (that was later discontinued). It no longer became possible to get whitelisted for the privileged intent without going through the privacy-invasive verification system. It was no longer possible to have your bot join over 100 servers at all without going through this verification system.

Discord claimed it would help with security and privacy by preventing malicious bots from growing and obtaining sensitive data. The library developers responded that it wouldn't help since malicious bots had to be invited and the crux of malicious bots were, and still are, user-bots. Not to mention that in the previous proposal, disallowing the so-called malicious privileged intents would still allow your bot to grow past 100 servers. The final proposal revealed by the blog post had made it so joining any server past 100 would require verification using a government-issued ID regardless of whether you had privileged intents disabled or not.

Since there was a lot of pushback on this topic, I made a form to get opinions from the developer ecosystem at the time and received around 1600 responses. I had planned to share it with Discord with hopes of maybe changing their mind on the concept or giving them insight into how developers felt, but they told me that my sample size was too small to be considered. Anyone with a passing knowledge of statistics would know that a sample size of 1600 is not insignificant. Nevertheless, most people who did the survey did not enjoy the idea of sharing their government-issued ID to verify their bot:

Bot Developer Survey 1

There was a lot of data concerning how bot developers felt about the change that I ultimately couldn't present to the Discord employees due to them not wanting it. At around this point in time, most of my motivation was waning. I was against the verification system at its core, since I considered it invasive and unnecessary. When asking an innocent question to Mason, the Project Manager of the Bot & API team, about whether my bot could connect to the gateway without being verified, he responded rudely and called me a "martyr" with an unnecessarily threatening tone:

Mason calling me a martyr

Bureaucratic Disaster

Following the intention to verify bots in the ecosystem, the support staff was immediately overwhelmed with the requests, causing their previous 5-day SLA promise to completely fall apart. The entire Bot & API Team had to work together to ensure that they could meet the demand of people verifying their bots. However, despite their best efforts, they were behind consistently for multiple weeks, even months, throughout the entire year of 2020, and this still continues to this day in 2021.

Discord had originally used the "Verified Bot Developer" badge as an incentive to get people to be "recognised" for their efforts within the ecosystem. According to them, this led to an influx of people applying for verification for the sole purpose of the badge. Eventually, they revoked the badge entirely and changed the badge name to "Early Verified Bot Developer". By not removing the badge instead, this had the consequence of feeding into the account black market. The resulting outrage from the bot developers who did not get a badge after the arbitrary cut-off was large enough that Discord employees rewrote history and handed out mutes for people who were just asking for the badge. They called this behaviour "badgeposting".

Badgeposting

History being rewritten

Discord consistently made promises all throughout 2020 that they were going to meet their fabled 5-day SLA. Despite Discord blaming badges for congesting the verification queue, the problem was not solved. I do not personally see a future where this consistent 5-day SLA happens. Despite hiring more support staff to handle the queue, it is still a month behind and is only going to get worse as more people will need to re-apply for their intents request in the following months before the deadline.

Slash Commands

Around July and August 2020, the Discord employees started talking to the people in the Discord Infrastructure server about the possibility of Slash Commands finally coming to Discord. This feature was one that had been in the talks since the very beginning of Discord's history, so some people were hyped it was finally coming. Unfortunately, at around the same time, Discord employees were hinting that message content would be removed or restricted.

Discord Infrastructure Leak

After my mole shared these images with me, I decided to share them with the remaining library developers in our private server. We began to see the introduction of Slash Commands as a way to destroy our old work. At this point, Slash Commands were not actually released. They were mainly in the development phase. However, we figured that when Slash Commands would be introduced to the public, that they would remove message content along with it.

Shortly after, the people in the Discord Infrastructure server got an early access beta for the implementation of Slash Commands. My mole also gave me the gist (not publicly available) explaining how the system was going to work. The Discord employees did not share this gist or information with us until later. When they finally shared the gist with us, they planned to have a meeting with us about how they wanted the system to work. I did not participate due to it taking place while I was at work. The library developers who participated said they shared a lot of feedback for how they wanted Slash Commands to work. Most of this feedback ended up being discarded.

When the Slash Commands beta reached the public phase, a lot of the general public ended up repeating the same criticisms and feedback that the library developers and the big bot developers had shared with the Bot & API team. After some amount of pressure from the community, they did finally implement some changes, though permissions remained a massive pain point. Fundamentally, Slash Commands had a fatal flaw: they weren't tied to a user. This meant that traditional permissions did not function with Slash Commands. For traditional bots, the administrator of a server could block specific bots on a per-channel basis by blocking the Read Messages permission. For a Slash Command bot, this would no longer possible since Slash Commands bypassed all forms of permissions.

We were told that the permissions system would improve over time, though this never ended up materialising. The ability for a Slash Command (aka an Interaction) to bypass the @everyone permission wasn't fixed until May 2021, 6 months after it had already been reported.

Message Content Privileged Intent

Around early June 2021, the top 8 most popular library developers were contacted regarding a special meeting about a topic that was important to all of us in the ecosystem. Knowing what we knew about the message intent, we figured that this would be the last chance we would get in order to defend the ecosystem from breakage and hopefully get them to change their minds on the entire thing. The meeting was bound by an NDA, which made us reluctant to sign it, but since we believed and were told that this would be our final chance to get a seat at the table for this change, we all agreed with the sole purpose of convincing the developers that this direction was a bad idea.

Unfortunately, due to being legally bound by this NDA, I cannot share too many details. However, I will mention that the morale from all the library developers fell quite fast.

All of us library developers were against the change for message content to become a privileged intent. It falls under the same bureaucratic issues that regular privileged intents suffer from, except with more devastating consequences. A lot of current bots in the ecosystem are faced with a choice of either getting rewritten to comply with changes I believe to be unnecessary, or to die. Discord seems to believe that this change is for the better – but no alternative path was explored or brought up. Instead, they opted to deploy the nuclear option and are hoping to fix the problem that way. Discord also believes that most bots will fully migrate over within the timeline given. I do not believe that this will be the case.

Future Direction

Discord has a lot of things planned in order to make the transition easier for users in the future. I'm not sure whether they'll actually finish all these planned improvements between now and the deadline. Historically, they've only managed to finish these changes a month before the deadline kicks in. Rather than improving the system before forcing it onto users, they have decided to announce the changes first and then promise on good faith that they will implement the necessary features to make the transition smooth. This gives bot developers no time to actually accommodate their bot for the changes, in case a feature they depend on for the migration doesn't exist yet.

Discord has already began rushing features in a sloppy and hasty manner. One of the newer features, context menus, has had a lot of feedback from many library developers and bot developers asking for the type to be overhauled and split to prevent library breakage and make the API more intuitive to understand. Despite this narrow feedback being provided by most users in the private beta for the feature, it has been explicitly ignored with the Discord employees claiming that they just wanted to get something out quickly.

Minn's response to night

I do not believe in waiting on promises for something to be better, when historically these promises have been empty. I do not think the situation will radically improve by April 2022 and do not think this change is worth the everlasting impact it will have on the ecosystem. Unfortunately, this decision is final, and the only thing I can feasibly do at this stage is to watch from afar. I do not have the motivation to keep up with an ecosystem I no longer believe in. I wanted a rich bot ecosystem to thrive and flourish, for bots to reach their full potential, yet Discord has repeatedly decided that limitations are a better route. This is why I have decided to step down as maintainer of this project. My involvement in discord.py and the API was always fuelled by passion and hope. These recent changes have drained me completely of both of those things.

FAQ

I imagine there are going to be a lot of questions from people who want the nitty-gritty.

Why are you stopping development?

My motivation to work on Discord has been dwindling over the past year, since the verification system was introduced. Persistent tone deafness, deadlines, lies, gaslighting, and rapid changes without proper consultation by the Discord employees make it hard to have the motivation necessary to work with the frequent changes and the limitations being placed on me.

To me, the message content privileged intent signals the end of the creative freedom and grassroots hacking us library developers all believed in. The control is now inverted and things are being built around Discord's limitations. No longer will bots thrive with a sandbox limited only by your imagination, but instead Discord is now the sole gatekeeper of approved use cases. The future of Discord bots relies solely on the interaction system; things have to be explicitly written and supported by Discord employees, with creative solutions being put aside. I wouldn't be surprised if in the future, the entire gateway API becomes restricted and deprecated, with the only recommended way remaining to create a bot being entirely interaction or HTTP based. I have no real hope for the future of Discord bots.

However, I don't want to give the impression that the things Discord is building are not cool. They are indeed very cool. Things like buttons and UI extensions are features that we've been wanting since 2016, and it's great to see them in the platform. It's just that it's coupled with a tough pill to swallow that damages the ecosystem as a whole. A price I'm not exactly willing to pay.

What happens now?

Development will cease and the repository will be put into a read-only mode.

What can I do about this?

Unfortunately, there isn't much you can do to stop this train other than telling Discord your opinion on the changes. The thought of the ecosystem breaking has caused me a great deal of stress and mental anguish. I've spent the better half of the past 2 months attempting to convey the distress I feel to various Discord employees to no avail. Discord seems to believe that everything will be fine in 9 months time, but I do not subscribe to this thought process.

What's going to happen to my bot?

This change is radical, even if I was removed from the equation. Discord expects all bots to migrate over to Slash Commands by April 2022 – whether I do anything to help or not. My proposed API I had for Slash Commands is incompatible with the current code for the commands extension due to the two systems being fundamentally different in paradigm. This means that no matter what path I would have chosen to take, a vast majority of library users would have needed to rewrite their code anyway.

It should be noted that Discord wants all bots over 75 guilds to migrate over to Slash Commands in the foreseeable future. If you want to apply for the message content intent, you cannot use it for command handling purposes; they will explicitly deny you the intent. Therefore, effectively everyone must move over to Slash Commands for their bot to function.

Discord Employee's Statement on Message Content Intent

Kady's statement on Message Content Intent

I want my bot to continue working!

During the Developer Q&A session on August 4th, Mason, the Project Manager of the Bot & API team, encouraged you to rewrite your bot since it's "easy" and "dope".

Question from the Q&A

Uh, popular libraries. So, we obviously do not have control over third party libraries. They are third party. Um, we try to work with them very closely to keep them informed of changes, uh and to answer their questions about implementation and API and consistencies and "Hey does this API suck or not". Uh, Slash Commands have been in an open developer beta since December of last year. Changes are not happening until an additional 9 months from now. Which will make it 1 year and 4 months slash 16 months if I know how to do math correctly since Slash Commands were first released. Um many libraries do have support. Some have unofficial forks. I will also say that for those intrepid developers they are pretty well usable without libraries but I know that that is a much sort of bigger task to undertake. Um but if you haven't checked out using Slash Commands over HTTP and outgoing webhooks, it's pretty dope and really easily scalable.

Therefore, if you want your bot to continue working you have a few options:

  1. Implement the slash command system yourself. The library (v2) provides on_interaction to help you do this, and all the endpoints are technically in bot.http.
  2. Implement the slash command system using the raw API.
  3. Wait for a competing discord.py fork to arrive.
  4. Rewrite your bot using a new library or in a different programming language.

Won't things be fine in April 2022? There's enough time!

Discord has repeatedly stated that they believe things will be fine by April 2022:

Kady's statement

However, the reality of the situation is that a significant number of libraries do not implement Slash Commands. The following is a table of support:

Library Implementation State Notes
discord.py Not Implemented
Discord.NET Not Implemented
disgord Not Implemented
discordjl Not Implemented
Dimscord Not Implemented
DSharpPlus Not Implemented
DiscordPHP Not Implemented Implementation no longer works
Sleepy Discord C++ Partially Implemented Unstable/Unreleased
Discordia Partially Implemented Unstable/Unreleased
Eris Partially Implemented Unstable/Unreleased
discord.rb Partially Implemented Unstable/Unreleased
discordgo Partially Implemented Unstable/Unreleased
nyxx Partially Implemented Unreleased
Ackcord Partially Implemented Unreleased
discord.js Implemented
JDA Implemented
Discord4J Implemented
Javacord Implemented
Serenity Implemented
Twilight Implemented
nostrum Implemented
Kord Implemented

These are libraries that implement it in any capacity, whether in a master branch or in another branch. Discord is expecting not only for the remaining libraries to implement the entire Slash Commands functionality, but also for all the users to migrate by the deadline. People have other responsibilities that don't revolve around Discord's ecosystem, so requesting all these users to do this is absurd.

Discord will give us messages that mention us, that means everything will be better... right?

Unfortunately, no. This is a small bandage over a very large wound. In reality everything bad about the message intent, as mentioned earlier, still applies despite receiving messages that the bot is mentioned in. Even in this utopia where bot developers maintain their message content commands, by virtue this means that users will all have to relearn the bot prefix, which will be bad for usability.

Can I take over the library for you? I can maintain it!

Unfortunately, I do not plan on giving maintainership status to those I do not trust. There is a security issue at play here that I do not feel comfortable with, where an unknown third party could upload malware targeting a bunch of Discord users. It should be noted that I did ask everyone who I was willing to give this library to, and they all declined, respected my decision, and agreed with me that they did not like the direction Discord is going.

You are, however, free to fork the project yourself and implement the improvements that you seek.

Why not implement Slash Commands?

In the simplest words: it's not fun. It's not particularly hard to implement slash commands for me, and I already had a mostly working, yet woefully incomplete, local copy made back in May 2021. However, my motivation to continue working on it is pretty much non-existent at this point. Slash Commands represent a change in direction within Discord that I fundamentally do not agree with. It is unfortunate that this feature was rushed out the door in order to add more restrictions to the platform.

Note that my Slash Command implementation was completely different from the discord.ext.commands implementation since the two models are strictly incompatible. So even if I had released my implementation, most users would have had to completely rewrite their bot to support it.

What happens to the discord.py server?

Ideally, nothing. I don't plan on doing anything to the server and it can remain as-is. The library still functions and there's still a lot of code out there written in discord.py. More importantly, the server holds a special place in my heart with a community I'm proud of and I see no reason to burn it to ashes.

What about the Discord API server?

Same thing. Nothing will happen there.

What's going to happen to R. Danny?

Due to the message content intent happening in the future, my bot will more than likely die since it won't be able to moderate. If you want to know what my bot means to me, I wrote a separate write-up on the topic when I was discussing this with Discord staff.

Would you ever consider picking the project up again?

I'm not sure. This decision came from multiple years of grievances from the Discord employees that would just be too much for me to detail in this document. I don't think they'll be fixed or be any better in the future, but only time will tell.

If it weren't for the direction Discord decided to take, I would have loved to continue working on discord.py. I actually really enjoyed working on this library and there were many things I would have liked to explore should time have permitted me to do so. However, underneath everything that the library does is the corporate entity that has repeatedly caused me these grievances that I've amassed over the years. It's hard to separate the two.

My question isn't here!

My bad. If more questions pop up during the announcement I'll add them back here, or you can just ask me directly in the discord.py server and I'll try to answer.

I'm really mad at you!

Sorry.

Acknowledgements

I'd like to thank the following people for all the help and support they've given me over the years, in alphabetical order.

  • aj. Thanks for being the most responsive Discord staff I've ever been in contact with. Your willingness and proactivity when working with us was unparalleled and much appreciated.
  • Bryan Forbes. Thanks for taking the time and effort to type hint the library initially. It was of great help.
  • Gary. Thanks for being a supporter in the discord.py server and for being so kind to everyone in the server and to me. I greatly appreciate it.
  • Hornwitser. Thanks for providing early design feedback for discord.py and untangling the spaghetti in the initial dispatch code.
  • Ian Mitchell. Thanks for listening to my incoherent rants and frustration and trying to make things better.
  • Ian Webster. Thanks for actually being kind enough to communicate with us when things went way south.
  • Imayhaveborkedit. Thanks for being the go-to voice wrangler all these years when I couldn't be bothered.
  • Jake. Thanks for actually being our pillar and maintaining the sanity in our Discord API server. Without you, we would have lost our vanity and many more things would have been worse. We'd often say that without your presence our server would cease to exist.
  • LeoV. Thanks for being there early on and helping design the logo for the documentation.
  • "Mole", you know who you are. Thanks for shedding light into the inequality that us library developers faced.
  • NCPlayz. Thanks for being one of the only other persistent contributors to the library. Without you, implementing some features would have been too taxing to do alone.
  • spoopy. Thanks for maintaining the code early on and providing invaluable feedback.
  • Stanislav. Thanks for being our go-to contact early on in the API days. It was fun.
  • The discord.py community. Thanks for being you.
  • The other library developers. Thanks for sticking together through all the nonsense. Without our unity I'm pretty sure I would have quit long ago.
  • The Red-DiscordBot community. Thanks for being kind and respectful to me. The feedback you guys gave when working with the command framework was invaluable to me.
  • The various contributors for discord.py. Thanks for improving various things throughout the library; even the most minor contribution has a large impact.
  • The various helpers in the discord.py server. Thanks for taking on a bulk of the hard work which usually goes unappreciated.

And of course, thanks to you for reading through all this.

Until next time.

@rsandfield

This comment has been minimized.

Copy link

@rsandfield rsandfield commented Aug 28, 2021

Thank you for bringing Discord.py this far. You rock, and it sucks that you got thrown around like this. Take care.

@korygill

This comment has been minimized.

Copy link

@korygill korygill commented Aug 28, 2021

Thank you for sharing and all your efforts over the years. I just recently found/needed/used discord.py and it's awesome. Sad to hear the story as you tell it and how the Discord team is treating the developer community. All the best to you in the future!

@jdimpson

This comment has been minimized.

Copy link

@jdimpson jdimpson commented Aug 28, 2021

Yeah that really sucks. Discord is doing what twitter did several years ago: locking down their (somewhat) open system, which will have a similarly deleterious effect on creativity. I'd be doing the same thing if I were in your situation.

@spectrapulse

This comment has been minimized.

Copy link

@spectrapulse spectrapulse commented Aug 28, 2021

It's sad to see it end like this. I've already felt like there was going to be friction with Discord's latest decision. But this was not what I expected.

I appreciate what you and all the maintainers have done all these years. It's sad that all good things come to an end.

Thanks for everything. You'll be missed.

@Column01

This comment has been minimized.

Copy link

@Column01 Column01 commented Aug 28, 2021

I appreciate all the work you've done for the community, I am optimistic that Discord might see this and realize how poorly they've handled all this. Sadly I doubt it will do much in the grand scheme of things. Thanks for all you've done for the python community! <3

@despedite

This comment has been minimized.

Copy link

@despedite despedite commented Aug 28, 2021

Quite a shame it had to end this way, but I've got to commend the balls it takes to get out this sinking ship that is the relation between Discord and the library (and bot) makers. Thanks for the voluntary (!!!) work on this project, it's changed a ton of people's lives in one way or the other.

@cabalex

This comment has been minimized.

Copy link

@cabalex cabalex commented Aug 28, 2021

discord.py was the basis of my first and major Discord bot, and I'll never forget how much fun it was to code. It's so intuitive, and I'm amazed you did it all for free. Thanks for everything, and best of luck in your future endeavors! :)

@Aens

This comment has been minimized.

Copy link

@Aens Aens commented Aug 28, 2021

This is a sad moment but not an unexpected one. When businesses stop listening to feedback it eventually turns out on developers working on software features that nobody wants. I've seen TeamSpeak die because of that and I don't know if Discord will die eventually because of that. There is always new competitors around and people migrate to those that give us a better experience (common sense).

Anyway, I appreciate what you did with this library, Danny, and I hope you have a good life, you totally deserve it. Take care.

@Callama

This comment has been minimized.

Copy link

@Callama Callama commented Aug 28, 2021

Thank you, Danny.
Discord.py gave me the opportunity to better myself -- and it did just that. I've learned so much these past 2-years by just using your library - and I'm saddened to see you go, but I know it's what's best for you. Good luck with whatever you choose to do next!

@knabb215

This comment has been minimized.

Copy link

@knabb215 knabb215 commented Aug 28, 2021

You haven't let anyone down, mate. Discord did. You tried your best and made an amazing library.
I only discovered discord.py a few weeks ago after trying out an awesome bot written by an equally amazing dev. I've spent the past few weeks learning about this library, and it seems it's all in vain - all because of some poor corporate decision making.

Thank you for all you've done for the Discord developer community.

To the Discord employees who directly resulted in the death of this library: Tell me, what good has come of this? How will this help improve your platform? Was it worth it?

@tairabiteru

This comment has been minimized.

Copy link

@tairabiteru tairabiteru commented Aug 28, 2021

Discord.py was not my introduction to programming, but working with it has allowed me to reach new heights. Heights that I never thought I would. To say that Discord.py has been influential in my life would be a gross understatement.
Thank you for all you've done, and take care.

@4gboframram

This comment has been minimized.

Copy link

@4gboframram 4gboframram commented Aug 28, 2021

Rip discord.py :(. Have a good break. Even though I wasn't that active in the community, discord.py has a place in my heart. It was the reason I ended up starting programming. One day I just wanted to make a discord bot, and discord.py was the first thing I saw. I bet many others have had the same experience.

@curation-bot-guy

This comment has been minimized.

Copy link

@curation-bot-guy curation-bot-guy commented Aug 28, 2021

I'm sorry for how unsympathetic the discord team was, and I fully respect your decision. This library has helped me and likely many others in so many ways, and I'm so grateful for all the work you've put into it in the past years.

@TehBrian

This comment has been minimized.

Copy link

@TehBrian TehBrian commented Aug 28, 2021

I completely agree with your viewpoint, and I would’ve made the same decision had I been in your shoes. Thank you for all of the work that you put into this project over the years. I know that both I and many others greatly appreciate it.

@majordoobie

This comment has been minimized.

Copy link

@majordoobie majordoobie commented Aug 28, 2021

I have learned so much because of this library. I dedicate my current position as a professional developer to discord. It taught me how to work with servers, databases, interact with users, docker, and so much more. So many concepts that I can bring to other languages too. Thank you for your hard work!

@lukadd16

This comment has been minimized.

Copy link

@lukadd16 lukadd16 commented Aug 28, 2021

Thank you for the in-depth summary of events, it really puts things into perspective and makes me even more appreciative of the work you and the other library devs have put into bringing bots to the masses. It's really disappointing to see the current direction Discord is taking with the API, and I totally respect your decisions to step down. Best of luck in your future endeavours.

@Zahariel

This comment has been minimized.

Copy link

@Zahariel Zahariel commented Aug 28, 2021

I found discord.py because I needed to integrate a previously-existing Django website with Discord. Discord.py fulfilled this need; not well, because of the age and poor design of the Django site, but I managed it eventually. I will very much miss it. Honestly I don't know how the bot and system I'm maintaining is going to continue at this point; I'm certainly not going to rewrite the website in something else, just to have the privilege of rewriting the Discord integration using a different library.

@0xAB51NTH

This comment has been minimized.

Copy link

@0xAB51NTH 0xAB51NTH commented Aug 28, 2021

Thanks for those years of contribution to bot developers, I'm pretty sure discord would not be the same if you were not one to help it grow.
Discord Devs back again at fucking up stuff, congratulations discord! Please make yet another redesign of app.

@hrolfurgylfa

This comment has been minimized.

Copy link

@hrolfurgylfa hrolfurgylfa commented Aug 28, 2021

I used this library for my first personal project that I only did because I saw a need for a program and I found it fun to do in my free time. It really encouraged me to continue my studies and constantly continued to practice no matter if school has been in session or not. Having this library around has made me a far better developer than I would have been otherwise, and it really has changed my life.

Thanks for all of the hard work on this library, from Iceland and the LPD VRChat Community.

@RossSmyth

This comment has been minimized.

Copy link

@RossSmyth RossSmyth commented Aug 28, 2021

Hey Danny. You probably don't remember me (if you're even reading this) as I haven't poked my head into the API server for many years, let alone been active. I just want to say that I really appreciate everything that you have done for the API community. I started programming with discord.py back in 2016 and hacked on it, messing around with the library, reading how it worked, changing it. And here I am, I just graduated from college this Summer and now I do software development, primarily in Python, professionally. It all started with you and your effort giving me inspiration to do something fun. I really can't thank you enough, and I wish you the best in your future endeavors.

@aghogwarts

This comment has been minimized.

Copy link

@aghogwarts aghogwarts commented Aug 28, 2021

Idk if you will see this but I just want you to know that it's your library that kicked back my interest in programming. I've had learnt py but casually before but when I knew there was a bot library for python I started creating my first discord bot. I just wanna say thanks and I hope you get through this. I ofc can't know what you exactly are feeling but I can assure it's not easy closing something of our creation which was a massive success. Hope you're alright

@BBArikL

This comment has been minimized.

Copy link

@BBArikL BBArikL commented Aug 28, 2021

Respect! Thank you for all your hard work that enabled thousands to create and learn through Discord.py. The move of Discord is really disgusting and I hope the userbase will find a way to pressure the company to revert on some terrible decisions they made or to move to more open platforms. Discord.py enabled me to create a bot that I really liked and that teached me so much. Again thank you for making / maintaining and defending Discord.py all these years and I wish you the best for the future!

@ultrabear

This comment has been minimized.

Copy link

@ultrabear ultrabear commented Aug 28, 2021

Thanks for the work over the years, despite the amount of times ive been annoyed by some specific of the library, its a really well made async library and bots I have made would not have been possible without it

I dont know the future of my bot cause of this, this is discord refusing to listen for the hundredth time, and the result of that

@w4rum

This comment has been minimized.

Copy link

@w4rum w4rum commented Aug 28, 2021

I have said this to quite a few people in the past: Discord.py is the best library I have ever worked with. No other library, especially API libraries, have ever come close to the usability and robustness of Discord.py. For me, writing Discord Bots started out as "just another hacky script that uses whatever-the-fuck API" and then, because I enjoyed working with Discord.py so much, became my favourite area of programming.

I am incredibly sad to see it come to this, especially since I have never before looked behind the curtains of this library and I did not expect things to look so discouraging. I always assumed that the interaction between the Discord Devs and you was going great, because, well, you made it work. This library going down is pulling the rug out from one of my bigger hobbies and I really hope that Python-based Discord bot development doesn't become as tedious as I've seen it in other programming languages.

Thank you so much for creating and maintaining Discord.py for all these years. I hope you find another amazing project that you can work on with the same passion as Discord.py. Godspeed, Danny.

@nerdguyahmad

This comment has been minimized.

Copy link

@nerdguyahmad nerdguyahmad commented Aug 28, 2021

I feel devastated to hear this and can't believe this. Discord really is going fast. I really enjoyed making bots. It was fun but Discord ruined the fun by taking the "freedom" from the developers.

Danny, Thanks for making discord.py. Thanks for all the effort you put in making this great library! You are indeed great. Much love for you! <3

It's not your fault. It's Discord fault. Sadly, Discord today lost a large community of developers.

@BobDotCom

This comment has been minimized.

Copy link

@BobDotCom BobDotCom commented Aug 28, 2021

As much as I hate to see discord.py go...

Sounds like you made the right decision. Discord hasn't seemed cooperative just from what you've conveyed in the past, and I can't imagine being in your position and having them not listen at all.

Best of luck with whatever else you end up doing with your life, and I'm sure we all agree that if discord ever opens up to all of the feedback they've been getting, we'd love for you to pick up the project again :).

@gerth2

This comment has been minimized.

Copy link

@gerth2 gerth2 commented Aug 28, 2021

huh. Sub-optimal to say the least. Far less because of discord.py being abandoned, and much more because of the API instability that seems to be driving it.

It's a bad move on Discord's part: Not career ending, but it opens a chink in their armor: if someone else wants to take their market share, all they have to do is provide a nice stable API, and they'll have a differentiating advantage for developers. This does indeed trickle down to consumers.

Thank you to Imayhaveborkedit, Rapptz, and all the developers!! Your work provided very real value to an FRC team, especially during covid when our meetings were hybrid, and we were able to extend discord to better meet our team's needs. You've helped to educate students, and helped me to personally grow as a developer! Best of luck as you go forward, and I hope our paths cross again!

I still owe ya'll a beverage of your choice if we meet in person. Hold me to it.

@Aya-Komichi

This comment has been minimized.

Copy link

@Aya-Komichi Aya-Komichi commented Aug 28, 2021

Thank you for these insights and the information, time for me to rethink my life choices on discord.

As for public bots these days, seems people are better of running away from such plans. If this is bad, just imagine what is coming after April 2022.

@CipherFox

This comment has been minimized.

Copy link

@CipherFox CipherFox commented Aug 28, 2021

Over the years, many users of my library have told me that discord.py changed their lives. It empowered them to challenge themselves, create fun things, and find new opportunities. As someone who has always valued educative, open-source projects, it means so much to me to know that discord.py has had a positive impact on people's lives.

This doesn't do you enough justice IMHO.

@SeparateRecords

This comment has been minimized.

Copy link

@SeparateRecords SeparateRecords commented Aug 28, 2021

It absolutely sucks that it's come to this but I think it's impossible to not understand where you're coming from. You've put a lot of hard work into this library over so many years and without this I'd have never gotten into programming back in 2017, so thank you. Good luck on your future projects!

@Tobotimus

This comment has been minimized.

Copy link

@Tobotimus Tobotimus commented Aug 28, 2021

Hey Danny, thanks for everything. I started tinkering with Discord bots in early 2016, namely Red-DiscordBot, whilst I was studying Computer Engineering at university. I learnt so much from this experience, so much more than I learnt at uni, and my full-time job today as a software engineer owes a lot to your efforts in creating such an amazing library. Much of what I know today about library design, API design, and Python programming came from using discord.py and occasionally deep-diving into your code. Whilst I was a core developer of Red, your tranquility and wisdom whenever we asked for your help was much appreciated.

All the best for the future <3

@Anubhav1603

This comment has been minimized.

Copy link

@Anubhav1603 Anubhav1603 commented Aug 28, 2021

I started programming by d.py directly, I still remember how I annoyed u by copying the code directly and then asking ,and Umbra making fun of me but that helped me to clear my basics and now from earlier I am able to write commands and program myself,it's really heartbreaking that you are stepping down 😢,but gl with your life ahead Danny,keep growing ,reach more high heights in life🙂,Again ty for your amazing work!

@Tobotimus

This comment has been minimized.

Copy link

@Tobotimus Tobotimus commented Aug 28, 2021

Your efforts in library documentation was also amazing. Writing good documentation is such a valuable skill, and much of what I know about it comes from your tireless work on the discord.py docs.

@nbelakovski

This comment has been minimized.

Copy link

@nbelakovski nbelakovski commented Aug 28, 2021

I just want to say, good for you! And I don't mean that in a snarky way or anything like that at all. Stopping development on something like this is not an easy decision and it makes me happy to see someone put their foot down and prioritize themselves. Thanks for sharing and best of luck to you :)

@KrishnanS2006

This comment has been minimized.

Copy link

@KrishnanS2006 KrishnanS2006 commented Aug 28, 2021

This is extremely sad. I have used and loved Discord.py for so long, and it just feels like everything is coming to an end. I am scared what will happen with the library in general, and although I completely understand the reasoning behind this, it just makes me cry on the inside. I hope this will be a lesson to the developers at Discord, to hopefully understand and implement changes in demand, and hopefully you can continue working on Discord.py in the future! This was a great experience, and I truly appreciate your hard work thus far.

@Robertrover811

This comment has been minimized.

Copy link

@Robertrover811 Robertrover811 commented Aug 28, 2021

Thank you so much for all the hard work that you put into dpy, it has been really great to work with and I'm sad to see it go. I helped me become a better programmer and I am eternally grateful for all the work you put into it

@vic-yush

This comment has been minimized.

Copy link

@vic-yush vic-yush commented Aug 28, 2021

It's unfortunate that Discord has managed to create such a disconnect between them and the third party developers that pour their heart and soul into creating tools that bring users to their product and keep them there. Yet, when you look at their track record of tone-deaf decisions and failure to keep promises, the lack of trust, or rather the lack of faith, that emerged as a result was only to be expected.

With that being said, the decision to step down from developing discord.py, while unfortunate, is something that I don't think anyone could reasonably blame you for. Using the API has always been an enjoyable experience (self-induced code errors notwithstanding), so I do not look forward to having to rebuild my bot with a different API in the future, but I will always have you to thank for providing the platform to get me into Discord bot development in the first place. As for my bot, it'll be fine. Probably.

Thank you for everything you've done and all the work you've put into discord.py. I wish you the best in all your future endeavours.

@Topkinsme

This comment has been minimized.

Copy link

@Topkinsme Topkinsme commented Aug 28, 2021

Thank you so so much, Danny.<3

Many years ago, I got into using discord only because a friend showed me a very cool bot. I wanted to make something like that, and that's how I got into learning dpy and python itself. Without dpy, I doubt if I would even be using discord so much. A big part of who I am and what I do as a hobby is due to dpy.

Thank you so much for your contribution, which has enabled so many of us to get into programming.
I wish you good luck in your future endeavours. :D

@denzven

This comment has been minimized.

Copy link

@denzven denzven commented Aug 28, 2021

Thank you Danny for this amazing wrapper in python... i started my print("hello world") and stopped with python... it was discord.py that actually helped me keep motivated and found a ton of friends through discord and learnt a ton of new stuff in python like classes ,funtions ,making modules a lot lot more..

Sad to see this happen.. and the atrocities of discord d.py was and will always will be my favorite library from discord bots.. i hope soon in the future.. discord mends its info and gives importance to the devs and cooperates with them and see discord.py and you come back

thanks a ton for everything.. and see you soon :sadcat:

@KokoseiJ

This comment has been minimized.

Copy link

@KokoseiJ KokoseiJ commented Aug 28, 2021

Have been consistently feeling that something was definitely not going in the right direction regarding their API system, but this gist made things so much clear for me.
Thank you for all the hard works you've been done for the past 6 years. The sole existence of your library fuelled my life with motivation for months and months. Godspeed.

@ravener

This comment has been minimized.

Copy link

@ravener ravener commented Aug 28, 2021

Damn that's sad, although I moved to discord.js a long time ago, discord.py was what got me started, when I didn't even know what programming was. I thank you for your effort on this and best of luck in whatever you want to do next.

@nikitalita

This comment has been minimized.

Copy link

@nikitalita nikitalita commented Aug 28, 2021

Have been consistently feeling that something was definitely not going in the right direction regarding their API system, but this gist made things so much clear for me.

It's the same direction that every single social network API has gone in: Make the API very open initially to attract developers to your platform, then gradually scale it back to facilitate monetization.

@KokoseiJ

This comment has been minimized.

Copy link

@KokoseiJ KokoseiJ commented Aug 28, 2021

Have been consistently feeling that something was definitely not going in the right direction regarding their API system, but this gist made things so much clear for me.

It's the same direction that every single social network API has gone in: Make the API very open initially to attract developers to your platform, then gradually scale it back to facilitate monetization.

which is what I was being worried about, sad to finally see it being rotten inside for a long time without us even knowing. this just leaves me with another reason to believe that community-driven things are indeed superior in the end...

@luigiMinardi

This comment has been minimized.

Copy link

@luigiMinardi luigiMinardi commented Aug 28, 2021

Thanks for all the work in these past years. And thanks for show to all the community how the things are happening behind the scenes. I hope that this gist spread in the community and someday discord changes its mind on how to communicate with its API users and library devs and how and when to update their API like this.

@Dacydl

This comment has been minimized.

Copy link

@Dacydl Dacydl commented Aug 28, 2021

Thank you so much Danny for giving us an amazing library and a community to us! I'd like to say that please if you can continue the library with us yes sure! I'd like to help you, but please take care of your health too! Have a good day, Danny 💟💝

@Taarek

This comment has been minimized.

Copy link

@Taarek Taarek commented Aug 28, 2021

Thank you for everything you've done, my friend. 💜

Es_SQ7eXMAQe09T

Image drawn by; https://twitter.com/MeiLi_8

@ILiedAboutCake

This comment has been minimized.

Copy link

@ILiedAboutCake ILiedAboutCake commented Aug 28, 2021

Thank you for your efforts over the years Danny, can't blame you for this decision. Your library helped me actually learn Python beyond one off scripts.

Personally your library helped me defend from spam and abuse Discord turned their eyes on and provided 0 tools to solve, and still don't provide first-party years later even in servers with 25,000+ members. As a developer and server admin I have always felt like a second-class citizen on the platform.

@SpiderMath

This comment has been minimized.

Copy link

@SpiderMath SpiderMath commented Aug 28, 2021

Have been consistently feeling that something was definitely not going in the right direction regarding their API system, but this gist made things so much clear for me.

It's the same direction that every single social network API has gone in: Make the API very open initially to attract developers to your platform, then gradually scale it back to facilitate monetization.

which is what I was being worried about, sad to finally see it being rotten inside for a long time without us even knowing. this just leaves me with another reason to believe that community-driven things are indeed superior in the end...

Same here, I am pretty shocked with Discord's Attitude here. I had always been inspired by Discord, with its transparency and freedom, but looks like it is pretty shit inside. I wish we could actually have a proper company, who would care about its Developers and feedback a bit more. It is as if they don't care about them!

@SpikeViper

This comment has been minimized.

Copy link

@SpikeViper SpikeViper commented Aug 28, 2021

Thank you for everything you did for the Discord community. I personally know what it's like to deal with Discord at its core and how they gaslight and ignore the community - my community arguing with them ended up in us losing almost everything and now developing our own new platform. I wish you well in your future goals and your journey, and want you to know it's not your fault and to not feel bad about stopping the project. It was a great service to provide to everyone, and nobody is entitled to your work if you feel it's time to stop.

@An0nyma

This comment has been minimized.

Copy link

@An0nyma An0nyma commented Aug 28, 2021

o7
Your work inspired me to make my own fun bot and to do random stuff with friends (with limited discord.py knowledge), and thanks to your amazing library I was able to do it in my favorite language; Python. I wish you the best, and thanks for everything!

@TheOnlyWayUp

This comment has been minimized.

Copy link

@TheOnlyWayUp TheOnlyWayUp commented Aug 28, 2021

<3 Thanks for everything, I personally learnt a ton and grew as a developer after working with your library and the constructive criticism I got from the dpy community, it was a great experience and I hope Discord makes some changes, good luck o7

@eslachance

This comment has been minimized.

Copy link

@eslachance eslachance commented Aug 28, 2021

o7

Even though I haven't used d.py at all, I've known it to be an awesome solid piece of work. You did a great job creating and maintaining it up until now, and I'm sad to see you go. But I fully agree with your assessment of Discord's relentless onslaught towards bot devs and library maintainers, it's felt like they're killing all of us slowly but surely.

I stopped working with bots about a year ago, and part of that was for the same reasons you're dropping it all now - except we didn't even have the insight that you were privy to.

Take care of yourself, stay safe and happy!

@13steinj

This comment has been minimized.

Copy link

@13steinj 13steinj commented Aug 28, 2021

Thank you for your work, however-- this is not a proper move. I understand that no one you trust is willing to maintain it, but this is how projects die. Forking is not how people take over projects, only how they make duplicates.

I urge you to try and find some way to trust others, at least someone with a larger name in the python community, that you can donate this project and keys to, rather than just leaving it up to forks. The major issue is the dead package name on pypi.

@RandomGgames

This comment has been minimized.

Copy link

@RandomGgames RandomGgames commented Aug 28, 2021

I'm sad to see it go, but I wish you the best. Gotta do what you gotta do. I've had a blast using this as a platform to learn more about python and coding in general. It's a shame it's come to this as it's not your fault. I wish you the best, as I hope others do too. I'm just sad to see my bots will simply break eventually ;( it was fun while it lasted.

@jaymo1011

This comment has been minimized.

Copy link

@jaymo1011 jaymo1011 commented Aug 28, 2021

Time for us to all move over to matrix!
Element is a pretty good matrix client for the now but the best thing is, matrix is open source so someone could make a Discord look-alike to make everyone feel more at home. (Oh, and bot clients are just normal user accounts, makes everything a 100x more simple)

As was once said: It's time to ditch Discord, Skype and TeamSpeak, Matrix is here!

@Phyxsius21

This comment has been minimized.

Copy link

@Phyxsius21 Phyxsius21 commented Aug 28, 2021

Have been consistently feeling that something was definitely not going in the right direction regarding their API system, but this gist made things so much clear for me.

Pretty much this, fucking insane honestly.
Thanks for all your hard work!

@Marseel-E

This comment has been minimized.

Copy link

@Marseel-E Marseel-E commented Aug 28, 2021

Thanks for all you've done, Honestly I don't blame you for taking this decision as I know you were forced to. Its sad that Discord doesn't give library developers what they deserve as they're a big part of Discord's success. Personally I only installed discord because I wanted to try coding, and discord.py was the reason I'm where I'm today. Take good care and have a wonderful rest of your life 👋

@Orangestar12

This comment has been minimized.

Copy link

@Orangestar12 Orangestar12 commented Aug 28, 2021

R.Danny is actual Discord history. We've known for a long time Discord's stopped caring about the guys that really made it palatable and successful in its early days but this is truly the biggest stab in the back from Discord's developers.

I hate this stupid service.

From one Danny to another, fare thee well. Hope to see you doing something with an ecosystem that supports your efforts somewhere else.

@CryticalAce

This comment has been minimized.

Copy link

@CryticalAce CryticalAce commented Aug 28, 2021

As sad as it is to hear. I wish you the best of luck with your future endeavours. You're library has had a monumental impact on my knowledge of Python development and there are many things I wouldn't have learnt if it weren't for you, for that, I thank you.

All the best mate.

@Mifdy

This comment has been minimized.

Copy link

@Mifdy Mifdy commented Aug 28, 2021

Same here, I am pretty shocked with Discord's Attitude here. I had always been inspired by Discord, with its transparency and freedom, but looks like it is pretty shit inside. I wish we could actually have a proper company, who would care about its Developers and feedback a bit more. It is as if they don't care about them!

This comes as absolutely no surprise to me. Their arrogance and lack of professionalism here matches perfectly what I've experienced in practically every encounter I've had with them since 2015. If you think their attitude regarding the API is bad, try talking to them about user safety, particularly that involving children. They play dumb and eschew responsibility every step of the way.

@nicholas-miklaucic

This comment has been minimized.

Copy link

@nicholas-miklaucic nicholas-miklaucic commented Aug 28, 2021

Sorry to hear that this is happening, but it seems like you've done all that you can be reasonably expected to do. I don't know why Discord would make the life of someone doing their work for free harder, but that's what happens I guess. Best of luck in future endeavors!

@branchBreaker

This comment has been minimized.

Copy link

@branchBreaker branchBreaker commented Aug 28, 2021

No sane person should get mad at you because of the circumstances. Although I must say I have never used discord.py let alone written my own Discord bot, you have helped many others program their own (while helping others at your local hospital,) and you have my respect for that.

In the beginning, it seemed that Discord was this rad platform that was unlike any other. Nowadays, it's yet another platform with plenty of feces behind the scenes.

I wish you the best in your future.

@TKDKid1000

This comment has been minimized.

Copy link

@TKDKid1000 TKDKid1000 commented Aug 28, 2021

In all honesty, besides communicating with some long distance friends, discord is more a place where I code, learn to code, and find others that code. You made a huge impact into discord, and python in general. There is such a huge void now that you stopped this library. Discord really needs to think more about us small bot devs, and less about making useless ui updates, and locking things behind paywalls.

@typicaldev1

This comment has been minimized.

Copy link

@typicaldev1 typicaldev1 commented Aug 28, 2021

Thank you for everything. Back in 2017 i was playing on a minecraft server called "DenisCraft" (it got renamed to MXMC though), and someone sent invite to a discord server. I clicked on the link and registered, and this application was amazing. Soon, when i got used to it, i wanted to make my own bot. But all my experence in programming was only web programming. I neved used python or node.js. But my friend recommended me this library. I didn't knew anything about Python, but back in that time i was very dumb and started to do something with this library. Soon i got used to this library and i got somewhat experienced in Python. Thanks to it, now i know node.JS, Rust and Python and i have my future as programmer

Thank you, Danny, for this library. This library gave me knowledge in Python, and if it did not exist i would never know about programming.

@TKDKid1000

This comment has been minimized.

Copy link

@TKDKid1000 TKDKid1000 commented Aug 28, 2021

Despite people probably not liking this, you definitely made the proper choice. As you said, you (and most of us devs here) like ourselves a good challenge to solve. With the old api, things were much more open, and we had to get creative with our solutions. Like using reactions as buttons and making paginated guis. Discord is not just suggesting, but outright replacing, creativity! I don’t ser it fair. You were totally correct, you library was built on creative solutions to stuff. Discord's vision is making all bots dull, and boring, and exactly the same.

@kofu145

This comment has been minimized.

Copy link

@kofu145 kofu145 commented Aug 28, 2021

Just another “thanks danny” coming by, have used the library for years and I’m sad to see it go; reading the blog makes me infuriated as well. I first started using d.py years ago and it was one of the first libraries I actively developed my python knowledge with - a big portion of my github consists of private repos of discord bots. This library is one of the main reasons I have stuck with this hobby of mine and it’s a big contributor to what I foresee is my career so I really couldn’t state how great this has all been, thank you so much and best of luck for whatever comes next.

@JamesParkDev

This comment has been minimized.

Copy link

@JamesParkDev JamesParkDev commented Aug 28, 2021

Thank you for this post!

During verification for bots I knew as soon as they stopped black market will open and sell discord accounts. While getting verified (back while it just started) I did tell them about my views, but they were also ignored.

I was not against verification as you stated, but just as that gov id was too much.

I do agree with all/most of your views, and I'm sad that discord became was place like this. And this is also the reason I stopped actively developing bots.

I wish you the best, and only hope that discord will change for the good.

@BokChoyWarrior

This comment has been minimized.

Copy link

@BokChoyWarrior BokChoyWarrior commented Aug 28, 2021

Creating a discord bot was a large step in my personal development as a programmer, and I cannot thank you enough for the library, and everything else behind the scenes.

I wish you all the best in the future, and know you made the unfortunate,but correct decision.

@hoopandango

This comment has been minimized.

Copy link

@hoopandango hoopandango commented Aug 28, 2021

Thanks for everything. My interactions with discord.py have been little, but I still appreciate the amount of effort that was put into making and documenting it. The type of workflow and mentality is what I loved about the internet, and it's sad to see it fading away. I wish you all the best for any future endeavours.

@laughingclouds

This comment has been minimized.

Copy link

@laughingclouds laughingclouds commented Aug 28, 2021

Thank you Danny, I started by making a discord bot as my very first project when I started learning programming (and it was quite recent). It has helped so much and I learned so much. I also remember going through RoboDanny's source code trying to learn and understand stuff very recently XD, and now this happens...

As the first ever library that I learned about and used, it has a special place in my heart. Thank you again and best of luck.

@Reevak05

This comment has been minimized.

Copy link

@Reevak05 Reevak05 commented Aug 28, 2021

I read your entire message. You've been a core part of the Discord bot community for years, and the community wouldn't be the same without you. Thanks for all your hard work, Danny, and I wish you luck and success with all your future projects.

@Herbstblatt

This comment has been minimized.

Copy link

@Herbstblatt Herbstblatt commented Aug 28, 2021

Thank you very much for your hard work, Danny. Building discord bots with the awesome library you created was fun, and I am feeling sad right now, however I understand, that not you, but Discord should be blamed for these things happening. I wish you all the best in the future. ❤️

@auxiliary-character

This comment has been minimized.

Copy link

@auxiliary-character auxiliary-character commented Aug 28, 2021

I wasn't familiar with your library prior to this post taking off in /r/programming, but thank you for everything you've done, and thank you for standing up for yourself. I'm so mad at everything Discord has done. That really seems to be the direction our world has been heading in lately... But please, take care of yourself!

@mdashlw

This comment has been minimized.

Copy link

@mdashlw mdashlw commented Aug 28, 2021

Nothing lasts forever. Neither is the motivation to comply with the limits of creative freedom fundamental to the bot platform. And so is the desire of those who limit that freedom. Justice will prevail, they say. But will it? How many more developers must quit, how many more bots and libraries must ceace to exist? Thank you Danny for discord.py, contributions to the platform, and all. ❤️

@Aranfielder

This comment has been minimized.

Copy link

@Aranfielder Aranfielder commented Aug 28, 2021

Thank you so much for your work over the years and I’m so sorry to hear of its end.

I have a small discord bot that relies on discord.py to run. The way he is supposed to interact means that slash commands is not a viable option for him. I am actually pretty distressed to be given his death date. I’m rather attached to my scripted bot child. ;)

I has no idea discord.py was volunteer-run, disgusted to learn that you were never funded by Discord for something that as become so intrinsic to the communities it hosts. Most (if not all) Discord users have something they use that relies on discord.py to enable their communities to thrive. I’m also infuriated to hear how actively hostile Discord devs have been to their own community and the people who have SHOWN them the possibilities they have, and the successes they’ve had with bot integration to the platform until now! They should have been working with you, not against you.

It doesn’t seem like they’re acting in the interest of the community or the users at all. Their ego has grown to a point where they believe they are too big for people to find an alternative. This will be their downfall.

I wish you all the luch in your next project. You clearly have a high drive and self motivation and I'm sure you will find success wherever you go. Unlike the devs at Discord.

@MrPixelized

This comment has been minimized.

Copy link

@MrPixelized MrPixelized commented Aug 28, 2021

Thanks for your great work on this! The decision is completely understandable.

Much of the open source sphere is switching away from Discord generally, what is your stance on that? Will you continue using their service for personal communication?

Take care!

@iamalicecarroll

This comment has been minimized.

Copy link

@iamalicecarroll iamalicecarroll commented Aug 28, 2021

Danny, thank you for everything you did for Discord bot development, who knows what would it look like without you. It’s sad that Discord lost one of the best people I know of. Don’t worry, you did your best and nobody blames you. Danny, you’re awesome ♥️

@SystematicError

This comment has been minimized.

Copy link

@SystematicError SystematicError commented Aug 28, 2021

Hi Danny,

I never usually comment on Github much but I just want to say a huge thanks to you for making discord.py so far, It was the drive that pushed me fully into the world of programming and software in general. Thanks a lot ❤️

Hope you stay safe out there :)

@FireHead90544

This comment has been minimized.

Copy link

@FireHead90544 FireHead90544 commented Aug 28, 2021

Take care Danny.
Thanks for everything you have done.
I myself hate these chages implemented by discord, taking over the message content is just same as "you will get a banana but only be able to eat it's peel".
Still nvm, again great thanks for supporting this huge library, your contribution will always be in our hearts. Take care, Danny 👋

@aNOOBisTheGod

This comment has been minimized.

Copy link

@aNOOBisTheGod aNOOBisTheGod commented Aug 28, 2021

I've never leaves comments on github, but now I just wanna say thanks for everything. Discord.py has made my summer cause it is easy to use and I can write cool bots using it. If it wasn't for you, Danny, Discord.py wouldn't be so cool.

Thanks for everything)) 🦄

@BA-24

This comment has been minimized.

Copy link

@BA-24 BA-24 commented Aug 28, 2021

From a person who learnt Python mostly thanks to discord.py and now being employed writing actual programs for an actual company, thank you for putting down the time and effort so people like me can have fun and toy around with something like this

@azgoodaz

This comment has been minimized.

Copy link

@azgoodaz azgoodaz commented Aug 28, 2021

I probably will get a lot of flack for this. But you should think about contacting Guilded Support and work with them with their API.

They recently got bought by ROBLOX, so funding is there to support and create a much better API compared to Discord. Just something to think about.

@maddiethecafebabe

This comment has been minimized.

Copy link

@maddiethecafebabe maddiethecafebabe commented Aug 28, 2021

discord.py is how i got into coding in the first place and probably spent all of 2018 with tinkering with bots. Now 3 years later I enrolled into uni to study computer science. Thank you for everything, you changed my life <3

@sks316

This comment has been minimized.

Copy link

@sks316 sks316 commented Aug 28, 2021

As an avid user of discord.py, thank you for all the work you've done for us. Hearing this hurts a lot, but I completely understand your reasoning and am immensely disappointed in Discord and their lack of communication, as I'm sure everyone else is.
Still, using discord.py and studying code written in it was the way I learned much, if not all, of the Python that I know, and the Discord bots I've written with that knowledge and this library are some of my favorite projects that I've worked on. It's sad to see it go, and if nobody forks it and Discord goes ahead with their breaking changes, I'll be forced to surrender and stop developing and supporting my bots forever. I don't think I'll ever be able to forgive Discord for this.
Once more, thank you for all the work you've done for us, and thank you for letting us piggyback off your creation for all this time. I wish you luck in your future endeavors.

PrincessLillie

@SauceyRed

This comment has been minimized.

Copy link

@SauceyRed SauceyRed commented Aug 28, 2021

Thank you for everything you've done. discord.py is what I used to practice Python after I had made a few basic things with it, I've made many bots that I've never released and probably never will, but they're fun to make. Anyway, hope you feel better now that you're moving on from this. Have a nice day!

@Arthurdw

This comment has been minimized.

Copy link

@Arthurdw Arthurdw commented Aug 28, 2021

Danny, thank you for creating discord.py and providing the tools for us to interact easily with the discord API. Dicord.py made me learn python and more programming languages, because of that it has permanently changed my life.

I fully understand and respect your decision.

@dragonostic

This comment has been minimized.

Copy link

@dragonostic dragonostic commented Aug 28, 2021

Thank you for putting up with everything and all your hard work. Discord.py was my introduction to coding, and has been an absolute joy to work with over the past couple years. It really did change my life in a positive way, and I had so much fun.

Thank you so much, I have a ton of respect for what you have done and your decisions for the future.

@Rexogamer

This comment has been minimized.

Copy link

@Rexogamer Rexogamer commented Aug 28, 2021

Your work has helped SO many bot developers over the last few years. Thank you for all our hard work, and I'm so sorry it had to end like this. (Discord has really given me vibes recently of not listening to feedback, so I can't say I'm surprised.)

@Jestemkioskiem

This comment has been minimized.

Copy link

@Jestemkioskiem Jestemkioskiem commented Aug 28, 2021

This library literally changed my life forever. It made me fall in love with Python and turned me from a minimal wage worker into a professional developer for 3 years now. I'm so, so sad to hear this, although I don't blame you. I just wish others could get the same opportunity that I did, learning to code doing something they find really fun.

Thanks for everything

@Crdguy

This comment has been minimized.

Copy link

@Crdguy Crdguy commented Aug 28, 2021

Thank you for everything. Like many others have said discord.py really got me into programming with Python, and I have learned so much from it. I can only hope now that other libraries take a similar course of action and try to get Discord to listen to their community.

@SpeedyCraftah

This comment has been minimized.

Copy link

@SpeedyCraftah SpeedyCraftah commented Aug 28, 2021

My message is probable noise with the amount of other messages but I 100% respect your choice. Discord hasn't been on our side for a long time now and someone that could have a big impact had to step up and say something. Discord bots aren't fun for me to develop anymore due to the vast amounts of api breaking changes and deadlines like were some dog that have to do things before a deadline. As a decently sized bot developer I have recently considered the choice to stop developing and hand over control to someone else because I can't be asked to deal with these issues with little to no benefit. Stay safe!

@SLiV9

This comment has been minimized.

Copy link

@SLiV9 SLiV9 commented Aug 28, 2021

Thanks Danny for all your hard work. When I had to port a small one-server bot for our indie game, I picked discord.py without knowing much about it, and it was a breeze! One of the best experiences I've ever had picking up a new library/framework.

@CrumblyLiquid

This comment has been minimized.

Copy link

@CrumblyLiquid CrumblyLiquid commented Aug 28, 2021

Thank you Danny and all the maintainers of dpy for the effort that went into dpy and it's community and made it what it is today.
Your library was my first real introduction to programming and I've had great time working with it.
I'm sad to see you go but I 100% respect and support your decision. Best of luck to you in your future endeavours! <3

@LBlend

This comment has been minimized.

Copy link

@LBlend LBlend commented Aug 28, 2021

Thank you Danny and all the other contributors for creating this amazing library. Making Discord bots with it was my gateway to programming and has forever changed my life. I now have a part time job as a developer and I am currently pursuing a degree in computer science.

Hadn't it been for this library's existence, I would probably be in a completely different place in my life now. So thank you for changing my life and thank you for your hard work! And thank you to the discord.py community for helping me out in times of need.

I wish you all the best in the future! <3

@FFrost

This comment has been minimized.

Copy link

@FFrost FFrost commented Aug 28, 2021

Your work inspired and impacted me and so many others. With discord.py, I was able to learn a lot and improve by working on my own shitty bot, for which R. Danny was a constant inspiration. Thank you for giving us these tools.

@ondrej008

This comment has been minimized.

Copy link

@ondrej008 ondrej008 commented Aug 28, 2021

Thank you for your library. I think Discord will be die in 2022 because they do shitty things for community, so in close future there will be a lot of Discord alternatives.

They will not die, even though they ban people for no reason, and ban entire servers that are partnered with discord for no reason, it only affects a small portion of their users.

@Sakiut

This comment has been minimized.

Copy link

@Sakiut Sakiut commented Aug 28, 2021

Finally finished reading! 🥵

I’ve been using Discord.py since the very beginning, I almost learn Python with this lib. I’m very sad that you chose to stop here but I truly understand how you feel and the reasons which leads to this decision.

I’m as well a v1 hypesquader and we have seen the same shift from the Discord staff, who have considered our feedback less and less over the years.

Thanks for all the work you’be done, you actually changed my life. Please take care ❤️😉

@stijm

This comment has been minimized.

Copy link

@stijm stijm commented Aug 28, 2021

Thanks, Danny. Your library is one of the most worked-out, elegant and intuitive libraries I have ever seen. If it weren't for discord.py, I wouldn't have learned asyncio, sqlalchemy and much more. You helped me a lot in coming up with solutions. Take care, mate.

@r3cebarnett

This comment has been minimized.

Copy link

@r3cebarnett r3cebarnett commented Aug 28, 2021

Danny,

Thank you for the incredible effort, passion, and skill that you have shared with the community over these years with this library. It's disappointing to hear the direction that Discord is going and how they've treated the 3rd party development community as a whole. It's quite ironic that an application such as Discord that thrives on communities rejects their own communities. Please take it easy, I have nothing but respect for you and your decision. Much love.

@BobGoldham

This comment has been minimized.

Copy link

@BobGoldham BobGoldham commented Aug 28, 2021

Anyone ever notice how all of Discord's support tickets regarding anything inconvenient (or just in a category that's usually not a nice on for Discord to handle) immediately get replied to by a bot, two times in a row, always the same 2 messages, then they stop responding?
They blatantly ignore user-feedback, do not care about their community AT ALL and abuse the monopoly they have to keep people on their platform.

"Thank you for contacting Discord(TM), your feedback is important to us." :)))

@TheRookie14

This comment has been minimized.

Copy link

@TheRookie14 TheRookie14 commented Aug 28, 2021

Thank you for all your hard work over the years. I'm beginning to slowly hate Discord because of decisions like this - I hope this project stays afloat one way or another.

Thank you for everything Danny. I wish you good luck with all your future endeavours.

@benfoster04

This comment has been minimized.

Copy link

@benfoster04 benfoster04 commented Aug 28, 2021

Danny, while I have caused a few issues in the past, the most I can say is sorry and thank you for everything you have done. Without the library you have created, I personally wouldn't be where I'm at right now with programming. You created the connection between a platform and language which a lot of people are familiar with. Without the library allowing peoples creativity to thrive, I don't believe the platform would be where it's at without you and of course to the vast amount of contributors to the library. I'm deeply sorry that Discord has driven you to this decision.

I wish you the best as a medical professional and any path you wish to take in the future. You are an inspiration to many, never forget that.

@anselal

This comment has been minimized.

Copy link

@anselal anselal commented Aug 28, 2021

i am really sorry about all this. discord is indeed evil. The verification process is a PITA and the verifiers are very rude.

don't know what I am going to do. I own a bot which I dedicated a lot of hours to build, I am trying to get a job as a professional discord bot developer using your library... things are to looking so good for me... rewriting the bot in another language is not an option. I hate JS and I am getting sick when I browse code in Java... 🤮

@DodoLeDev

This comment has been minimized.

Copy link

@DodoLeDev DodoLeDev commented Aug 28, 2021

Thank you so much for this incredible library, which gave me a real passion for developing in Python!
I've spent so many hours to discover all that was possible to do with Discord.py!

Just, thank you so much for this, Danny!

@cnnn666v2

This comment has been minimized.

Copy link

@cnnn666v2 cnnn666v2 commented Aug 28, 2021

Well, I never really tried d.py, I am more familiarized with d.js
Altho they implemented slash commands, I'm not going to use it. My bot is a small project (made with aoi.js that is a wrapper for d.js) and after april 2022 guess it'll die :)

It's sad that this library is going to die since i have a friend that uses it for his own bot. Good luck in the future <3

@Andre601

This comment has been minimized.

Copy link

@Andre601 Andre601 commented Aug 28, 2021

Thank you for this Post Rapptz.

It inspired me to make my own one directed at Discord: discord/discord-api-docs#3731
(Gist in case the above link doesn't work anymore: https://gist.github.com/Andre601/a51e1e5927f394864afc6b21cc5feef0)

@Triodes

This comment has been minimized.

Copy link

@Triodes Triodes commented Aug 28, 2021

Thank you for bringing discord.py to life. I had a blast writing my little bot and am still proud of its added value. Making it would not have been possible without you. I wish you all the best and hope you find some other place where your passion for programming can come to fruition!

@mte0

This comment has been minimized.

Copy link

@mte0 mte0 commented Aug 28, 2021

Man, i really want to thank you for all the time youve put into this, im also mad and sad because python is the only language i really know.
It is truly sad to see the direction discord is taking. thank you, discord.py was a part of my life too stay strong (come back too pls)

@KrazyKirby99999

This comment has been minimized.

Copy link

@KrazyKirby99999 KrazyKirby99999 commented Aug 28, 2021

@Rapptz, I am the author of the simplematrixbotlib package, which contains a python library inspired by discord.py . If you have any suggestions or would like to contribute, I would be welcome and thankful for any help. Simple-Matrix-Bot-Lib Repo Thank you for the time and effort that you spent working on discord.py

@briancullinan

This comment has been minimized.

Copy link

@briancullinan briancullinan commented Aug 28, 2021

I like the intents API and I like privileges, and I like the new slash command API, it looks nice. Can't wait for them to introduce surveys. lol. Maybe no one wants to work on discord.py because you're a negative Nancy. Keep your security problems to yourself if you don't want to share responsibilities.

@AvgZing

This comment has been minimized.

Copy link

@AvgZing AvgZing commented Aug 28, 2021

Thank you for everything; I really hope discord will eventually pay attention to its community when they say things, whether it's global emotes, the new design, overcorporatism, or this absolute mess. They used to, vaguely, listen to people... that's gone, and it sucks. Thanks for speaking about it.

@Hunter2807

This comment has been minimized.

Copy link

@Hunter2807 Hunter2807 commented Aug 28, 2021

Well it's really sad seeing Danny quitting discord.py development, but tbh this library was the only reason I started learning Python... I was a complete beginner that time, and this lib and the discord.py community helped me learn Python and write my first Python code... I still remember, when I was new to the server, I didn't even knew how to call a function, but thanks to the amazing community, now I am well versed with Python... I didn't really contributed to discord.py library, but I can say that this library literally changed my life... Thanks to Danny for such a good library and sad that u gotta quit just cz discord don't want to listen to the developers community and carry on with their decision... Of course, everything u wrote above is heart breaking, but it's also understandable that bad decisions are the reason this library is going once and for all.... I hope discord fixes their decision and we can see this library rise again... This community has given me soo much, but I never really got a chance to give something to this community... Seems like I really missed my chance...

Thanks for taking this step, so that many bot devs' eyes are opened, and they see the real discord, and not just useless reasons...

@delbonis

This comment has been minimized.

Copy link

@delbonis delbonis commented Aug 28, 2021

This is what happens with centralized network services, especially ones operating under a startup-like model. They become large enough and the best interests of themselves start to diverge from those of the userbase.

We need decentralized alternatives that put users in control.

@tilda

This comment has been minimized.

Copy link

@tilda tilda commented Aug 28, 2021

i said this already in your dms, but thank you so much for your work. without this library i would probably be in a much worse state than i am now. i'm not kidding when i say d.py changed my life.

it's unfortunate that discord has the audacity to not listen to the developers its platform basically depends on, but ah well, what can you do about that. i'm just glad i got to experience working with it.

once again, thank you danny ❤️

@Daru-Coding

This comment has been minimized.

Copy link

@Daru-Coding Daru-Coding commented Aug 28, 2021

i just started programming in python and the first thing i did was making a bot ... first project.
Thank you for making discord.py and maintaining it till now.
Thank you for your effort and all u did.
Sorry to hear this.
Also and i respect your decision.
Looking forward to your next projects if you will make ones and good luck with.

@pieromqwerty

This comment has been minimized.

Copy link

@pieromqwerty pieromqwerty commented Aug 28, 2021

Jeez, I never used Discord.py that much, but holy shit is it bad to see a great project go. I hope one of the forks created carries on with help from the community, and hopefully the community as a whole can keep this project alive.

@dangreene0

This comment has been minimized.

Copy link

@dangreene0 dangreene0 commented Aug 28, 2021

Thank you so much Danny for all you work! Over a year ago I started making a discord.py bot and it taught me programming!
Thanks to your wonderful API I was able to learn how to program and have become very confident in my ability.

I hope no matter where your life takes you its a good one!
Thank you so much!
E8XNUxjXoAALSM3

@NeloBlivion

This comment has been minimized.

Copy link

@NeloBlivion NeloBlivion commented Aug 28, 2021

Jesus christ, when I first heard Discord would be completely locking out regular message-based commands in favour of slash commands I think we all immediately realised this wouldn't end well. It's a shame it had to end this way due to Discord's incredibly half hearted approach to the API and its maintainers.
DPY has been such a joy to work with for the past 3 or so years, so it's absolutely heartbreaking to see it (officially) come to a stop here. Nevertheless, good luck on your future work Danny; I'm sure you'll make it to higher places.

@Scartzz

This comment has been minimized.

Copy link

@Scartzz Scartzz commented Aug 28, 2021

I've just read through everything and I'm absolutely with you in all Points. I think it's absolutely crappy the way Discord goes with it and I can't understand it. I use discord.py for all my Bots and love it.

Thank you so much Danny for all of your work! ❤️

@svemat01

This comment has been minimized.

Copy link

@svemat01 svemat01 commented Aug 28, 2021

Thank u so much for everything you've done Danny. Without discord.py, I wouldn't be so heavily invested in coding as I am today. I'm sad to see your decision to stop, but I fully understand your decision from how discord treated you and the other of the discord lib devs.
And again, thank u so much for everything ❤️

@Superlasek

This comment has been minimized.

Copy link

@Superlasek Superlasek commented Aug 28, 2021

Really sad about all of this.

This library was the reason for me to pick up and learn python. I made a bot as a school assignment for my university. I was very happy to show my classmates and friends what can be done with discord.py and since then I have not stopped learning, thank you very much Danny for everything you did for the community, take care 🎇

@jonathanSimonney

This comment has been minimized.

Copy link

@jonathanSimonney jonathanSimonney commented Aug 28, 2021

Thank you very much for all the work you did.

Did I miss something, or could your library keep being used as long as the bot stays in less than 100 servers , because I got the impression with your description that all the privilege asking part and bureaucratic handle were only for getting your bot past 100 servers threshold.

Still agreeing with all your analysis and fear of the lack of communication from the discord devs, this sucks.

Best of luck for your future.

@terminalnode

This comment has been minimized.

Copy link

@terminalnode terminalnode commented Aug 28, 2021

discord.py was my first project that was bigger than hello world and some random scripts, and it's a very big reason why I decided to walk the path that made me a professional developer. It's sad to see it go, but we had a good run. Thanks for everything.

@Zejammydodger

This comment has been minimized.

Copy link

@Zejammydodger Zejammydodger commented Aug 28, 2021

Thanks for everything Danny, it sucks to see things turn out this way. discord.py helped me so much over the past year, ive learnt so much from it. truly incredible work

and discord, should you ever see this, sort your shit out.

@HeroGamers

This comment has been minimized.

Copy link

@HeroGamers HeroGamers commented Aug 29, 2021

A genuine thanks for all your work and efforts that you've poured into the library and the community over the years. After reading your gist though, I understand and agree with your decision, and wish you the best of luck with everything that might head your way in the future <3

Thanks for a great library, a library that I have loved throughout the years that I've used it, even though I've had slight troubles with it, which wasn't even due to discord.py at all, but due to the limitations and changes on Discord's end.
All of my frustrations go towards Discord, it's truly sad to see things go in this direction.

It's been great to have you, Danny <3

@shahriaarrr

This comment has been minimized.

Copy link

@shahriaarrr shahriaarrr commented Aug 29, 2021

This is catastrophic news in the world of programming. It is really unfortunate that this library is not going to be developed. I hope this library will be upgraded again. I call on the text community again to participate in the development of the project as much as they can

@ExtraConcentratedJuice

This comment has been minimized.

Copy link

@ExtraConcentratedJuice ExtraConcentratedJuice commented Aug 29, 2021

discord is sucking some real shit to get the dev of the most used wrapper for their api to call it quits
i hope some better replacement for this platform comes along; fuck discord and their lazy and out of touch api dev team and their shithead trust and safety team

@PanIntegralus

This comment has been minimized.

Copy link

@PanIntegralus PanIntegralus commented Aug 29, 2021

Thank you for helping me develop my first bots on Discord. We are actually using one on my friend's server. It's so sad that Discord transformed in an evil corporation that is rude to the people that is really important for its platform. Take care.

@laughingwater

This comment has been minimized.

Copy link

@laughingwater laughingwater commented Aug 29, 2021

I wont be where i am right now if this api did not exist, you made my coding journy start, because of you now i know python and am learning c#, i never thought that something could get me this far, but its sad to see you go forever, but i just want to thank you for everything you have done :D

@julien040

This comment has been minimized.

Copy link

@julien040 julien040 commented Aug 29, 2021

I've never used discord.py but it makes me sad that this project is gone.
I know a lot of people who have discovered programming while creating bot. And the library they were using was discord.py

You've made people learning code, they may be discovered a passion.
You should always think about that.

Good luck for the future

@Craftplacer

This comment has been minimized.

Copy link

@Craftplacer Craftplacer commented Aug 29, 2021

I guess time to ditch Discord sooner or later and go back to IRC, as being the only solid protocol with the community busy building IRCv3.
(or maybe even Guilded.gg if that ever turns out to be a better Discord replacement)

@ItsDrike

This comment has been minimized.

Copy link

@ItsDrike ItsDrike commented Aug 29, 2021

I completely support your decision about this, I'd probably do the same considering how careless discord is. Ideally we should just switch open-sourced chat applications, such as Matrix, the only problem there is that it simply doesn't have enough users, but that would mean no stupid restrictions like these, and if there were a bad decision, community could always fork. Well, I wish you them best!

@Dusk-Argentum

This comment has been minimized.

Copy link

@Dusk-Argentum Dusk-Argentum commented Aug 29, 2021

I started learning Python thanks to d.py, and was able to make some great strides in learning how to program thanks to it. Unfortunately, this has left me with having a bunch of niche knowledge that probably won't apply to anywhere else, but it's still knowledge that you and the contributors to d.py have helped make accessible to me. Thank you! Discord is a much better place thanks to your efforts.

I hope wherever you go next is a place where you can be heard and appreciated.

@AkshuAgarwal

This comment has been minimized.

Copy link

@AkshuAgarwal AkshuAgarwal commented Aug 29, 2021

Thanks a lot for everything you worked on for us! ❤️

One of the most hardworking person who cares about their community, unlike discord. All the hard work you did for us can never be recreated by discord. Also thanks for sharing all the story with us.

Take care and good luck for your Future 😄

@jemand771

This comment has been minimized.

Copy link

@jemand771 jemand771 commented Aug 29, 2021

I'm in p a i n

I didn't know about most of the changes you mentioned, especially message content becoming a privileged intent. This actually makes me really mad (not at you of course) since some of my bots heavily rely on that for other things than just plain commands. Let's just hope that "everything will be fine in april", which is, at best, unlikely

Thanks for everything you've done for us as a community, take care ❤️

@kzhuworshiper

This comment has been minimized.

Copy link

@kzhuworshiper kzhuworshiper commented Aug 29, 2021

rip discord.py. I'm so sorry to hear about this but as always all good things have to come to an end. Although Danny has stopped contributing to the discord.py library I wish the best for his mental health overall and make sure he gets enough sleep/ better health overall. Thank you Danny for everything you did, discord.py will always be one of my favorite libraries.

@Itz-Hyperz

This comment has been minimized.

Copy link

@Itz-Hyperz Itz-Hyperz commented Aug 29, 2021

I never used Discord.py, I was sent this article by a friend. I'm a DiscordJS user, but I know that this library is huge. This is really gonna screw alot of bot devs out there with the way Discord is going. It makes me worry about what library is next...

@BradonZhang

This comment has been minimized.

Copy link

@BradonZhang BradonZhang commented Aug 29, 2021

Thank you for all the work you've done. Using discord.py was my first experience with Python, and it taught me quite a bit. I've since gone on to use Python in many aspects of my professional and personal life, including writing a bot which (while I was still developing it) was added to 4000 servers - WAY more than I could have ever anticipated.

I'm sad to see the slash commands being forced like this, and I understand why it's hard to keep motivation working on this project under these circumstances. I hope a fork of the project is made from a competent and caring developer so that this project can continue.

Best of luck to you, and thank you for everything. ❤️

@macdja38

This comment has been minimized.

Copy link

@macdja38 macdja38 commented Aug 29, 2021

It’s absolutely unbelievable to me that there’s no way to stop a user bot that joins your server from dming everyone with scams / ads…

(Just having DM non admin server members be behind the member verification level would fix a lot of this) or that I can’t set my DMs to require phone verification…

But now some bots will be restricted from seeing message content…

Thanks for everything you’ve done for the discord bot community, your opinions have always been well thought out and valuable!

@maddoxdragon

This comment has been minimized.

Copy link

@maddoxdragon maddoxdragon commented Aug 29, 2021

this library was my primary reason for learning how to code in the first place as well as an incredible learning resource thanks to the thorough documentation. thank you so much for your work danny, it was remarkable while it lasted and it's a massive shame that discord keeps heading in this direction. i wish you the best of luck in your future projects!

@timmypidashev

This comment has been minimized.

Copy link

@timmypidashev timmypidashev commented Aug 30, 2021

Uhm, well, woke up today to this little surprise but hey, life is life man. Anyway I really appreciate how much work you have put in to the lib Danny. Stumbling upon your work has changed my life, personally and in my developer journey. I have learned much, and have grown from many mistakes and questions I've asked in #help lol. I really hope and look forward to your next open-source project, as I know it will be a success under your maintenance.
With ❤️ 𝓣𝓲𝓶𝓶𝔂#6955

@W1L74680

This comment has been minimized.

Copy link

@W1L74680 W1L74680 commented Aug 30, 2021

Thanks for helping me in my projects! I have a lot appreciated working with discord.py for a year. I hope you will let the API alive so we can continue using discord.py before April 2022. I’m sad that this library is going to be unusable in a few months, but I’m glad I grew up with it.

Love from Canada, W1L7

@kameko

This comment has been minimized.

Copy link

@kameko kameko commented Aug 30, 2021

I don't use discord.py, I'm a .NET developer, but as a developer, I completely empathize with you. A software company that doesn't support developers is doomed to failure. Look at Apple, they can never get market share over Android because they treat developers like dogs, they actively bully developers and that's why iOS is a spartan wasteland of apps, with apps getting taken down by Apple or their developers every week.

I'm already using Matrix with some friends, I'm trying to get my other friends on Guilded and I'm going to demo out Revolt later. Discord is scary, they've banned by friends for simply being a server doing illicit things, not even actually doing those things. They're as bad as Twitter now, I want nothing to do with them.

I hope something good comes along, I hope Guilded or something like it gets popular, maybe you can make the new hit python library.

@YourFavoritePerson

This comment has been minimized.

Copy link

@YourFavoritePerson YourFavoritePerson commented Aug 30, 2021

The presence update/server member privileged intents have notes on the discord developer portal that they only need verification after 100 servers. Is this message content intent going to work the same way or is this going to be ALL bots regardless of how many servers they are in?

@igrisqq

This comment has been minimized.

Copy link

@igrisqq igrisqq commented Aug 30, 2021

I may not initially know who the developer of the discord.py library is, but I am very grateful to you and admire you. Thanks to your many years of work (not only yours, but also the developers of other libraries.), The development of bots has developed very much. We researched a lot, we found a place to implement our ideas. It was fun and interesting.
It's sad that this situation has turned out and you stop working. But in any case, thanks for your many years of work, efforts, faith.

@GarvitSinghh

This comment has been minimized.

Copy link

@GarvitSinghh GarvitSinghh commented Aug 30, 2021

Thank you so much for everything Danny. You really have no idea how many people's lives you have changed with discord.py. There are a ton of people I know too. Discord.py was definitely the library I read the most about and invested the most time into too.

We all have a ton of respect for you for maintaining the library alone for so many years while being a Medical Student/Professional.
The whole community wishes you all the very very, very best and very good luck for all your future endeavors.

You've brought joy to so many people, hope it all multiplies and comes back to you!

@SomethingGeneric

This comment has been minimized.

Copy link

@SomethingGeneric SomethingGeneric commented Aug 30, 2021

Thank you for everything Danny. Discord.py got me into learning Python and Computer Science. It's a shame that Discord decided to out all the library developers in this roundabout way.

Best of luck with all your other endeavors!