API versions & deprecations update #4657
Replies: 12 comments 29 replies
-
|
Unless my understanding of the timings is wrong, does this mean versions seven and eight will decomission at the same time? Not positing this as a negative thing, but just curious how the extension affects things. Basing that assumption on this from the original announcement: |
Beta Was this translation helpful? Give feedback.
-
|
I agree |
Beta Was this translation helpful? Give feedback.
-
|
I am not yet sure what the idea behind this commissioning strategy is? Why are blackouts a favorable strategy? What's the use of this choice? So far the only thing I can see behind it is a large number of confused developers. |
Beta Was this translation helpful? Give feedback.
-
|
My understanding is that it's a wake up call for those who have ignored previous correspondence around soon to be decommissioned APIs. You can only send someone so many emails, but a disruption of service gets everyone's attention. |
Beta Was this translation helpful? Give feedback.
-
|
@jgayfer is correct here. We have chosen this strategy because blackouts are way to help developers understand that they are on unsupported versions without just pulling the plug abruptly. We consider this approach to be best practice. If you have any more questions about decommissioning, happy to clarify. |
Beta Was this translation helpful? Give feedback.
-
|
If that was the strategy you were going for, could you at least initially send a message to the bot developer(s) reminding them to upgrade their rest/gw versions if they've been active on it recently? That way they can at least plan ahead to upgrade instead of facing unexpected outages (as much as they deserve it) |
Beta Was this translation helpful? Give feedback.
-
|
Oh nvm didn't read that far down the post sorry! |
Beta Was this translation helpful? Give feedback.
-
|
If you're a developer who gets affected by the planned blackouts, then that's on you as a developer for being ignorant of API updates. |
Beta Was this translation helpful? Give feedback.
-
|
Honestly I don't really get why this decision has been made, the people that haven't updated yet won't update in a year either. The decommission was getting rid of a lot of selfbots and stopping to support outdated and unmaintained applications and it's apparently a bad idea? From my point of view, most developers who have not updated yet won't update until their bot stops working, and this deprecation update will just make them update their bots months later. Versions like discord.js v11 (uses API v7) have been deprecated for years now, and developers have had the option to update for quite a while. I agree that direct message notifications are needed when doing something like decommissioning an API version, but what's the point of extending the deadline in this case, when API v7 has been the "Doesn't look like anything to me", that lib devs got told off for using last year by API devs? EDIT: yeah i was really tired that day, i understand now |
Beta Was this translation helpful? Give feedback.
-
self-bots are possible in API v8/v9 (I didn't try tho) & also the last version of Discord app that supports Android 4.1-4.4 is 9.x.x which uses API v6
Discord app that supports Android 4.1-4.4 is 9.x.x which uses API v6 & there is no problem in basic usages of Discord like sending/receiving messages and doing voice calls. I do know that it doesn't support new features tho There isn't any known patches that makes Android 4.4 able to install newer apps even if it exists it will require rooting/sideload/custom recovery. Currently the app works just fine in most features & it's not that unstable too viewing a profile of a user who uses the new Discord username system without a discriminator won't crash the app you'll see the username properly |
Beta Was this translation helpful? Give feedback.
-
|
and also the existence of old API versions doesn't even create issues to most of other users/developers. v6 is working just fine & just not adding newer Discord features like threads is only supported in API v9+ so discord devs didn't need to spend unnecessary time to implement threads on API v6. if you want newer discord features in the API using newer API version is enough without sending v6 to heaven (because it takes unnecessary times adding or fixing newer features on v6) & breaking old but still used systems that needs Discord API v6 |
Beta Was this translation helpful? Give feedback.
-
|
Will the message content privileged intent be enforced on v7? Will we need to have applied and been approved for it in order to receive message content? |
Beta Was this translation helpful? Give feedback.
-
|
Yes; no code changes will be necessary but you will need the intent enabled in the dev portal. |
Beta Was this translation helpful? Give feedback.
-
|
What is happening to Gateway v6 and v7? The docs claim that HTTP and Gateway are versioned separately, but that doesn't seem to have been true lately, such as gateway v7 and api v9 being released solely to make the API and Gateway have the same version number. discord.py and old versions of discord.js use API v7 but Gateway v6. |
Beta Was this translation helpful? Give feedback.
-
|
Correct me if I'm wrong, but aren't intents required on Gateway v7? The docs aren't clear as they don't document v7 at all. |
Beta Was this translation helpful? Give feedback.
-
|
To my knowledge they're only required on v8 and upward. |
Beta Was this translation helpful? Give feedback.
-
|
I actually hadn't gotten any notification at all about the v6 shut down (which my bot 100% relies on). A month ago when I happened to come across a relevant issue on GitHub while I was looking into another feature to add and realized I needed to upgrade everything. I would've expected the bot owners be contacted directly while there's still time to upgrade, rather than me having to monitor GitHub or a Discord server's messages. It's ok, I should be off v6 in time as I've been migrating things over, but direct communication via a Discord DM would be ideal IMO. |
Beta Was this translation helpful? Give feedback.
-
|
I'd assume that was the original plan, but that they'd contact you closer to the decommission date. Not exactly the best if their bot has a large codebase but the original post in this discussion does mention contacting users directly whos bots are still using older API versions. |
Beta Was this translation helpful? Give feedback.
-
|
I would've preferred to be contacted promptly after the decision is made. There's no reason for them to wait. |
Beta Was this translation helpful? Give feedback.
-
|
Discord should have stuck to their guns on this, imo. Bot authors need to keep their bots maintained. |
Beta Was this translation helpful? Give feedback.
-
|
I completely agree, especially since I myself have been busting my ass for the last 6 weeks to move a bunch of bots over for a client before the deadline only to find out there was no need to rush. |
Beta Was this translation helpful? Give feedback.
-
|
What do you mean by "temporarily unavailable"? Will it send out 500 status codes to any requests to v6 for some time? |
Beta Was this translation helpful? Give feedback.
-
|
When DMs get sent out to affected folks, can the DMs please include which application/bot the DM is referring to? As an owner of multiple bots, the system DMs I receive often do not make it clear which one they are referring to, which makes tracking down issues rather inconvenient. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for your wonderful insight that I should just know... Given that I should just know, then notifications and the blackout period would also be rather pointless in their entirety... |
Beta Was this translation helpful? Give feedback.
-
As a developer, the onus is on you to ensure your work is up to date with current standards. Sure, Discord may choose to specify in correspondence which token has been recently used on an affected API version but ultimately, it's YOUR responsibility to know YOUR code.
You've just hit the nail on the head and exactly the reason why the blackouts are going to be used. They're intended to wake up the developers who clearly don't care enough about what they're doing or their work to keep up to date with standards. This is also why you'll find a lot of people, me included, that are rather annoyed that we took the deprecation warnings seriously and after spending time and effort bringing some of our older projects up to current spec before the deadline, we find out that Discord has decided to go soft to cater for the lazy and the ignorant. |
Beta Was this translation helpful? Give feedback.
-
I'm sure your intent is good, but it's just comes off rude. People have lives outside of Discord, and there are some people who run bots for smaller communities or friend groups but might not keep up-to-date with everything that happens in terms of discord development and new API versions. While I can completely understand the frustrations of working on moving everything over only for it to not matter for a while longer, it's something you can use as an opportunity to make sure everything is actually up to spec and not just done because the decommission is coming. Not everyone is a seasoned bot developer who keeps tabs on everything. Learn to respect the smaller devs. |
Beta Was this translation helpful? Give feedback.
-
|
I operate one of the top 30 bots on Discord, and I rarely touch it, been using v6 of the API till I started migrating to v10. I'm able to continue to enjoy the project because it's such a low commitment. |
Beta Was this translation helpful? Give feedback.
-
I'm a small dev, I've only been messing around with Discord development since the start of Covid because I was bored. In fairness I guess I perhaps take more interest in a project's development than a lot of other people do, and I of course don't mean any offence to those that want to say spin up a simple bot for their friends in their private Discord server. My comment was pointed more directly at the type of person who I was quoting on the basis that, lately at least, Discord have been pushing a lot of smaller changes that require increasing API versions to be used to get access to them. I'm referring to things like application commands, message components and modals for instance. If you're interacting with the Discord API(s) then you're either doing so directly and as such would absolutely need to know what API version you're using or using a framework like Discord.JS in which case their documentation, guides and their support server all get very hands on about which version of the API each version of their framework uses with their own attempts at getting people to move forward and update their code. For what it's worth, I don't know anybody who messes around with Discord development who hasn't ended up getting sucked in deeper and let a small one or two command bot turn into a beast of an application that requires an understanding of things like API versions etc. But again, I may just be relying on my own experiences too much. |
Beta Was this translation helpful? Give feedback.
-
|
May I ask which emails or notifications, since I got none? |
Beta Was this translation helpful? Give feedback.
-
|
they haven't been sent yet, hence the future tense |
Beta Was this translation helpful? Give feedback.
-
|
Okay, thank you |
Beta Was this translation helpful? Give feedback.
-
|
If you have a bot on v6 or v7 you should work on updating it rather than waiting for a notification/mail from discord |
Beta Was this translation helpful? Give feedback.
-
What status code will requests to any endpoint return during a blackout; will it just be 404s or will a http code like 410 be used? |
Beta Was this translation helpful? Give feedback.
-
|
Is it still happening on May 3? there's barely been anything about this since this day. |
Beta Was this translation helpful? Give feedback.
-
|
that was referring to May 3 2022, and it was superseded by #4725. There is not currently an ETA for v6/v7 decommission. |
Beta Was this translation helpful? Give feedback.
-
|
what will happen to old version of Discord apps which was released before API v8 was released which supports Android 4.1+. will they stop working? and also I prefer old version of Discord PC client used in 2019 (it doesn't mean client modification, official old version) it uses API v6 and if I make a proxy server which forwards API v6 requests to v8 the client crashes when viewing guild member profile and inline replies don't show at all because API v8 has a message type 19 while v6 has type 0 personally I really nead API v6 |
Beta Was this translation helpful? Give feedback.
and others
-
Greetings fellow developers,
An update on decommission plans for old API versions:
We’ve gotten some questions around what decommission looks like, so here are some details:
In addition to the above, we're planning direct outreach to bot owners who are on any deprecated version of the API, even before decommission periods begin. See #4510 for information on what to expect for newer API versions :)
Thanks to all community members for their feedback and input on this issue!
Beta Was this translation helpful? Give feedback.
All reactions