This is a nonexhaustive summary of the DDevs Q&A stage. Most of the points below are paraphrased for brevity. Ephasis is my own unless explicitly stated, and my opinions on certain things may shine through. Please refer to a VOD of the stage for the exact wording from the Discord Developers.
- App Discoverability (partially released)
- making it easier to find useful fun bots.
- Part of this was the "Add to Server" Button.
- Verification is not required for adding the button.
- Tags!
- All opt-in. If you aren't ready, don't feel pressured.
- Now is the best time to do some house cleaning and prepare your bot.
- Thank you Ian and Mason
- Form Interactions!!!!!! (Upcoming feature)
- Notion Doc + Demo
- At launch will only support the "text input component"
- Supports a short input field, and a larger text area input.
- It displays in a modal window.
- Thank you devsnek!
- Scheduled Events (recently released)
- Notion Doc + Demo
- Thank you heymoo!
- rip my calendar bot
The following points are answers to questions asked by the community. Questions can be found in the VOD and will not be listed here. All points are listed in order they came up in.
- If you have open support tickets for intents and/or verification, please check them, they've caught up a decent bit and waiting for lots of replies
- DDevs will be frozen for 15 mins 11/23/21 for 15-30 minutes in the morning. They are restructuring the server to improve overall support.
- Discord continues to improve on communication with bot and lib devs. However, because DMD is much smaller (750 total members vs 100k in DDevs). Large bot devs and lib devs do get to give feedback on upcoming features. However, not every feature gets tested by lib devs or DMD. The idea is that they talk directly to the people impacted most by the feature or change, its just not possible to have everyone test something.
- About invite link tracking, see previous answer from last stage Q&A (linked below)
- A "bot insights" page would be helpful, but there is not yes/no to whether they will ever add that. But they like the idea of it.
- Select menus may be getting auto complete at some point. Its a matter of getting it into existing code.
- The 4k character limit on application commands will (likely) be getting bumped higher "sometime soon". There is no word on how much higher it will be though, as the vast majority of developers do not hit this limit.
- "modals" for bots are coming, see the form interactions demo for more info. Its designed so they can easily built ontop of and expand it.
- A "sandbox" mode for bot developers is something they are thinking about and looking into. They understand it is highly desired but make no promises.
- Intents queues are getting shorter now that the large influx of requests have died down. It is unlikely that the intent deadline will get moved.
- Removing/adding users from an event's RSVP isn't a binding function, as those users could still join the event unless their permissions are changed. If users do not have access to the host channel, they will not see the event.
- Text input componenets will not be possible inside of messages, it will only be possible in modals. (it would be really bad UX if chat kept moving and your text box kept going up)
- Text input/form modals will be able to be launched from buttons, it is an interaction response.
- They are improving existing features and adding new ones. The bots API team is large enough now where they can focus on multiple things. There are many other teams of devs working on each feature.
- Eg: Ian and Mason are not the developers responsible for scheduled events, but they are coordinating with those devs.
- They will be doing a pass on interactions errors to make them more user friendly!!!! (no more cryptic errors soon^tm)
- A date/time option type is something Mason really wants, but first they must get the "must have" features out, like better slash commands permissions.
- There's various "cache issues" they plan on addressing.
- Slash command localization is being actively worked on
- "localization" they mean translations for showing localized commands/options/descriptions/etc.
- localization for responses is something they are looking into, but have to talk to their privacy team as exposing user's locales could become a problem.
- Thanks infinitestory
- Thanks Mason, rip all the automod bans.
- Discord does not officially endorse or curate any libraries, python devs will need to find a replacement library they deem adequate for themselves. Not all libs are made equal.
- IPv6 support for the API is "tentatively planned" but GCP (Google Cloud Platform) has really bad IPv6 support and is the major roadblock.
- Jake says its a bit more complicated in chat, so maybe this will come up again in a more formal way.
- Context menus will be coming to mobile "soon". Probably after the new perms system is in place. maybe.
- About new command perms system: Currently top level commands are all that support perms. Subcommands and subcommand groups don't have IDs, which is the major limiting reason for not having perms support.
- Improved developer teams and permissions for the dev portal will be coming eventually. (such as restricting who can see the token). Part of their "developer success" mindframe they keep mentioning lol.
- HTML widgets will never happen due to the dangers of XSS attacks. There will likely be a better way of doing this (maybe an embed overhaul?)
- "fuzzy matching", Substring matching, not even displaying disabled commands is all planned, but the permissions system needs to come first.
- Bug hunter badges will "probably not" be given to API bug reports.
- Mason might have shot himself in the foot with this one: v10 might be coming before the end of the year? or at least a limited version so that message intent restrictions can be tested by bot devs before the intent is enforced at the end of April.
As always, big thank you to all the discord developers for your hard work!
Here's a recording of the event, visually formatted a little more nicely than the livestream: https://www.youtube.com/watch?v=e5m_Sx9zyb0