Austin Keener
@dv8fromtheworld.bsky.social
Senior Software Engineer at @discord
I will things into existence for Bots, Apps, and the wider ecosystem of API users.
I will things into existence for Bots, Apps, and the wider ecosystem of API users.
Components are intended to be a composable set of UI blocks that you can put together to craft visual experiences in a variety of surfaces, although right now our 2 available surfaces are Messages and Modals.
November 14, 2025 at 2:58 PM
Components are intended to be a composable set of UI blocks that you can put together to craft visual experiences in a variety of surfaces, although right now our 2 available surfaces are Messages and Modals.
In regards to components, you can send components as part of message or modals, where the former can be crafted via:
- normal message sending:
discord.com/developers/d...
- webhook message sending
discord.com/developers/d...
- interaction message sending
discord.com/developers/d...
- normal message sending:
discord.com/developers/d...
- webhook message sending
discord.com/developers/d...
- interaction message sending
discord.com/developers/d...
Discord for Developers
Build games, experiences, and integrations for millions of users on Discord.
discord.com
November 14, 2025 at 2:57 PM
In regards to components, you can send components as part of message or modals, where the former can be crafted via:
- normal message sending:
discord.com/developers/d...
- webhook message sending
discord.com/developers/d...
- interaction message sending
discord.com/developers/d...
- normal message sending:
discord.com/developers/d...
- webhook message sending
discord.com/developers/d...
- interaction message sending
discord.com/developers/d...
We do have an open api spec, but it is in a beta state. We're working to improve it
github.com/discord/disc...
github.com/discord/disc...
GitHub - discord/discord-api-spec: OpenAPI specification for Discord APIs
OpenAPI specification for Discord APIs. Contribute to discord/discord-api-spec development by creating an account on GitHub.
github.com
November 14, 2025 at 2:54 PM
We do have an open api spec, but it is in a beta state. We're working to improve it
github.com/discord/disc...
github.com/discord/disc...
I'm gonna miss working with you 😭
November 12, 2025 at 6:20 AM
I'm gonna miss working with you 😭
Sure, shoot. I don't check here often, but I'll respond when I do.
Watcha got?
Watcha got?
November 12, 2025 at 6:11 AM
Sure, shoot. I don't check here often, but I'll respond when I do.
Watcha got?
Watcha got?
Wow, _in_ powershell? Nutty
November 11, 2025 at 5:14 PM
Wow, _in_ powershell? Nutty
Who knows, maybe it _will_ end up in a desert like area in the future given that SEMICON West moved from SF to Phoenix this year. Had been in SF for like 5 decades
October 21, 2025 at 5:09 PM
Who knows, maybe it _will_ end up in a desert like area in the future given that SEMICON West moved from SF to Phoenix this year. Had been in SF for like 5 decades
Whoa these are cool. I like the blue one quite a bit
October 21, 2025 at 5:05 PM
Whoa these are cool. I like the blue one quite a bit
You can mostly map things. The big omissions are author, fields, and footer.
Author and footer can be mostly approximated via the subtext markdown feature, although you do lose the inline external image.
Fields are a known loss. We aren't sure how we want to reintroduce tabular data due to mobile
Author and footer can be mostly approximated via the subtext markdown feature, although you do lose the inline external image.
Fields are a known loss. We aren't sure how we want to reintroduce tabular data due to mobile
April 23, 2025 at 2:10 PM
You can mostly map things. The big omissions are author, fields, and footer.
Author and footer can be mostly approximated via the subtext markdown feature, although you do lose the inline external image.
Fields are a known loss. We aren't sure how we want to reintroduce tabular data due to mobile
Author and footer can be mostly approximated via the subtext markdown feature, although you do lose the inline external image.
Fields are a known loss. We aren't sure how we want to reintroduce tabular data due to mobile
I'm just lucky that it wasn't my user id in the mention otherwise my client would've exploded with pings heh
April 23, 2025 at 2:08 PM
I'm just lucky that it wasn't my user id in the mention otherwise my client would've exploded with pings heh
Yeaaaaah, I left some debug code in on a last second PR :0
Oops. Happens to the best of us
Oops. Happens to the best of us
April 23, 2025 at 2:08 PM
Yeaaaaah, I left some debug code in on a last second PR :0
Oops. Happens to the best of us
Oops. Happens to the best of us
During the development of this feature I built some other UIs that I think are interesting. Here's one of them based on usage of an anime voting bot I saw in the wild.
Left is the original based on legacy embeds. Right is a conceptual reimplementation using the new components
Left is the original based on legacy embeds. Right is a conceptual reimplementation using the new components
April 22, 2025 at 10:16 PM
During the development of this feature I built some other UIs that I think are interesting. Here's one of them based on usage of an anime voting bot I saw in the wild.
Left is the original based on legacy embeds. Right is a conceptual reimplementation using the new components
Left is the original based on legacy embeds. Right is a conceptual reimplementation using the new components
Heh, this looks very similar to what I built for Discord's.
Choosing to highlight the TLD separately is :chefs-kiss:
Choosing to highlight the TLD separately is :chefs-kiss:
April 21, 2025 at 6:54 PM
Heh, this looks very similar to what I built for Discord's.
Choosing to highlight the TLD separately is :chefs-kiss:
Choosing to highlight the TLD separately is :chefs-kiss:
Replace "surprising amount " with "one individual engineer wouldn't shuddup about it".
Oops, it was me.
😔🙇♂️
Oops, it was me.
😔🙇♂️
March 13, 2025 at 1:37 AM
Replace "surprising amount " with "one individual engineer wouldn't shuddup about it".
Oops, it was me.
😔🙇♂️
Oops, it was me.
😔🙇♂️
The performance of calling back into a JS interpreter while in native code is too impactful for platforms like low-powered android devices.
This is why we are considering something like TreeSitter which uses native-compiled code for its AST parsing, which we can then map to colors for text ranges
This is why we are considering something like TreeSitter which uses native-compiled code for its AST parsing, which we can then map to colors for text ranges
January 28, 2025 at 10:42 PM
The performance of calling back into a JS interpreter while in native code is too impactful for platforms like low-powered android devices.
This is why we are considering something like TreeSitter which uses native-compiled code for its AST parsing, which we can then map to colors for text ranges
This is why we are considering something like TreeSitter which uses native-compiled code for its AST parsing, which we can then map to colors for text ranges
The crux of the problem is needing to be able to parse the text in a language aware way and then be able to color ranges of text within native text views with coloring. Given that it seems that VSCode's TextMate implements all of the language parsing in TS, we'd need to call JS from Native. Can't do
January 28, 2025 at 10:41 PM
The crux of the problem is needing to be able to parse the text in a language aware way and then be able to color ranges of text within native text views with coloring. Given that it seems that VSCode's TextMate implements all of the language parsing in TS, we'd need to call JS from Native. Can't do
Does the mug in the first photo have two different glazes on it? How do you achieve the dark gray accent lines / speckles?
January 19, 2025 at 4:36 PM
Does the mug in the first photo have two different glazes on it? How do you achieve the dark gray accent lines / speckles?
I tried and it timed out while going to the link in the email
January 15, 2025 at 1:52 AM
I tried and it timed out while going to the link in the email