API versioning + API v10 #4510
Replies: 21 comments 35 replies
-
|
Beta Was this translation helpful? Give feedback.
-
|
Funny how the author of this announcement is called typpo :^) |
Beta Was this translation helpful? Give feedback.
-
|
Woah! This comment had me halting for a moment and realize that typpo is the very same person who blessed my youth a lot petter with his Outwar DCAA, hello @typpo and thank you for what you did back then! <3 |
Beta Was this translation helpful? Give feedback.
-
|
Pretty cool news, with all these versions of marked, a new one can get lost quickly. |
Beta Was this translation helpful? Give feedback.
-
|
It has been over three weeks. Why is the change in API version states (v10 added, v8 deprecated) not reflected in the docs as linked in the comment this is a reply to? |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
Did the message content intent became a gateway intent to pass inside the identify payload? if it is, what's the flag? |
Beta Was this translation helpful? Give feedback.
-
|
Could the flag for the Message Content Intent be noted in the announcement? |
Beta Was this translation helpful? Give feedback.
-
|
Additionally, it would be nice if this was added to the documentation |
Beta Was this translation helpful? Give feedback.
-
|
We are still working towards updating documentation to reflect this new release. Expect to see documentation updates soon™. |
Beta Was this translation helpful? Give feedback.
-
|
How soon do you mean when you say soon? |
Beta Was this translation helpful? Give feedback.
-
|
soon™ |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
it was a joke state iirc |
Beta Was this translation helpful? Give feedback.
-
|
it has caused a lot of confusion when it was added and for some reason they refused to change the wording |
Beta Was this translation helpful? Give feedback.
-
|
iirc API v7 was a testing ground for things to merge into v6 back in b1nzy's day. I could be wrong, but that was the general consensus at the time. |
Beta Was this translation helpful? Give feedback.
-
|
it was skipped because people were using it when they weren't supposed to |
Beta Was this translation helpful? Give feedback.
-
does this mean that achievements will stay and will no longer require the dev license? |
Beta Was this translation helpful? Give feedback.
-
|
What's an achievement now 🤔 |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
no, it doesn't. this change brings all localized strings into a consistent format. the old localized string format was a union type, which makes it hard to work with. moving forward localized strings will be separated as first seen with application command localization. |
Beta Was this translation helpful? Give feedback.
-
|
So, is the updated |
Beta Was this translation helpful? Give feedback.
-
|
The command permissions we've discussed are still work in progress, but I would expect to see this field become deprecated once we launch revamped command permissions. |
Beta Was this translation helpful? Give feedback.
-
|
Are command permissions v2 still on track to be released with enough migration time before April 30th? |
Beta Was this translation helpful? Give feedback.
-
|
Command permissions are already in testing with specific test guilds. We hope to have more to share with you all soon™. |
Beta Was this translation helpful? Give feedback.
-
|
Will file uploads with incorrect field names (i.e not files[n]) be rejected on v10? |
Beta Was this translation helpful? Give feedback.
-
|
No; the current release is the full change-set we've targeted for this release. |
Beta Was this translation helpful? Give feedback.
-
What about cdn.discordapp.com ? |
Beta Was this translation helpful? Give feedback.
-
|
Given that isn't addressed here, let's assume the CDN's location isn't moving until they announce it. Legend has it, it's an immovable object. |
Beta Was this translation helpful? Give feedback.
-
|
We have no current plans to migrate off of |
Beta Was this translation helpful? Give feedback.
-
|
Has the changed mentioned in https://discord.com/developers/docs/resources/channel#start-thread-without-message for API v10 been applied? ( |
Beta Was this translation helpful? Give feedback.
-
|
We can followup with the team in charge of threads for clarification, but at first glance it does not appear there was API version logic added for v10 on this route. |
Beta Was this translation helpful? Give feedback.
-
|
After speaking with this team they've decided to delay this breaking change for a future API version. |
Beta Was this translation helpful? Give feedback.
-
This one is actually not required for backward compatibility, as a bot without message content intent will still receive redacted (i.e. content fields set to blank values) guild message objects. |
Beta Was this translation helpful? Give feedback.
-
|
It is a breaking change in the sense that if we required you to specify the message content intent in <v10, and your bot relied on messages, your code would break unless you made changes to it. This is the same strategy we used for Presence/Guild Member intents a couple years ago 👍 |
Beta Was this translation helpful? Give feedback.
-
|
Guild message read access being privileged for bots in more than 100 guilds is already requiring a re-evaluation of bot's data handling at the time of application, which can indeed involve code changes. It is a worthwhile point to make that change in a bot's code base. |
Beta Was this translation helpful? Give feedback.
-
|
I want to make sure that we're on the same page about how the default API is selected and how versions are bumped in the future. Worth noting that v6 has been simultaneously a default and deprecated version for about 1.5 years (#2097), and the default is now being bumped to v10, effectively skipping v8 and v9 (and v7, our beloved). Not a huge deal if users have been explicitly selecting a version and are keeping up with the changes, but that jump just seems kind of abrupt for people who have relied on the default having a meaningful place in the sequence of API versions. Some questions, then: You define what "stable" means here, but not what "default" means. Are these the same thing? In the future, can we expect a schedule of sorts for when individual versions become decommissioned/deprecated/stable/default/available? I don't mean a calendar schedule, but more like "if version |
Beta Was this translation helpful? Give feedback.
-
|
Stable/Default Timelines So for example
Our next review should be ~end of June. At that point, if there is a reason to version bump:
Then, the next quarter (~September)
Again this does not guarantee that availability/default/deprecation would happen on that quarterly cadence every quarter. |
Beta Was this translation helpful? Give feedback.
-
|
Just to add a little bit more clarity between what I said and your
|
Beta Was this translation helpful? Give feedback.
-
|
Looks good to me, thanks for the response. |
Beta Was this translation helpful? Give feedback.
-
|
But why do you must shut API v6 and v7 down? |
Beta Was this translation helpful? Give feedback.
-
|
We've deprecated discord.js v11 (???) and v12 for several months now... you should update your bot to v13 instead, as we will not provide support for such old versions, nor can we guarantee the safety of unofficial forks |
Beta Was this translation helpful? Give feedback.
-
|
also, it is not feasible to maintain code for old API versions forever, you should have switched away from the old API and d.js versions long ago |
Beta Was this translation helpful? Give feedback.
-
|
ok |
Beta Was this translation helpful? Give feedback.
-
|
I'll be migrating my library to this version tonight, with a plan to release an official 10.0.0 too. new versions are always good news! the changes seem small and safe enough to do this (our lib major versions match that of the latest Discord API version). |
Beta Was this translation helpful? Give feedback.
-
|
Another small question, after April 30th rolls around, whats the state of API v8? Does it also get discontinued? |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
Are there any other story channel/SKU related application fields that are considered deprecated and tagged for removal in v11 or is it just application.summary? |
Beta Was this translation helpful? Give feedback.
-
|
Decommission date for API v6 and v7 has been postponed to early 2023. |
Beta Was this translation helpful? Give feedback.
-
|
When v10 will be default? |
Beta Was this translation helpful? Give feedback.
-
|
I updated the post, but we're postponing this for now and will have separate comms when there's more info to share |
Beta Was this translation helpful? Give feedback.
-
|
Should the 4 states be documented here? |
Beta Was this translation helpful? Give feedback.
-
|
We are in middle 2023, but API 6 and 7 deprecation schedule still says "early 2023" with an unspecified date. |
Beta Was this translation helpful? Give feedback.
-
|
was discord creation date mint cryptographic encryption algorithm changed? . since the only documentation , was suggesting a way to decrypt available part to by decrypted which is the first and second section. it does work for the first section (before the first dot) of the token which is the user id decrypted in base64. But the token create date mint which is encoded in base64 -> hex -> discord unix timestamp + token epoch time, doesn't seem to be encoded in this format anymore. |
Beta Was this translation helpful? Give feedback.
-
|
It's not the case anymore, read the discussion of the issue you've linked and you'd know the response. It's never been documented before so yes, it can change at any time and so it did. For your information, base64 is not encryption it's encoding. |
Beta Was this translation helpful? Give feedback.
and others
-
Hey everyone,
We have a few updates regarding API versioning and what to expect over the coming months. As of today, you can begin specifying
v10in your API requests. We are also deprecating API v8. Read more below for what to expect.API states
First, let's clarify the possible states of an API version. There are 4 states:
We recognize that you count on the API to be stable. Deprecation periods will last at least 1 year, unless otherwise noted.
Changes as of today:
Early 2023:
API v10 will become the Default version, and the default version for API requestsPlans for default versions will be communicated in the futureAPI v10 changes
Message Content
Message content restrictions are enforced for verified bots on v10. The full extent of the changes can be found here: https://support-dev.discord.com/hc/en-us/articles/4404772028055-Message-Content-Privileged-Intent-for-Verified-Bots
These restrictions will not be applied by default until after August 31, 2022. The availability of API v10 allows you to opt-in to testing your bot's behavior early.
Specifying the message content intent (
1 << 15) is required on v10. If you are on v9 or lower, you will automatically receive message content if you have been approved, even if you aren't specifying the intent.Other Changes
application.summarynow returns an empty string. This field will be removed inv11nameanddescriptionare now strings, and localized strings are now stored inname_localizationsanddescription_localizations/channels/<channel_id>/threads/activehas been removedattachmentsmust be specified whenPATCHing messages with new attachments. Any attachments not specified will be removed and replaced with the specified listreasonas a body/query parameter is no longer supported, and you should instead use theX-Audit-Log-Reasonheader.embedsrather thanembedv10and higher will no longer be supported ondiscordapp.comWhy not X change?
There were a few other changes that were raised during the v9 lifecycle that we could have brought into v10. We decided to keep the set of changes small outside the message content change. We want developers to fully focus on being prepared for the August 31, 2022 deadline.
Beta Was this translation helpful? Give feedback.
All reactions