1 << 23 (APPLICATION_COMMAND_BADGE) that got introduced in #13 is an Application flag unlike the all the other flags that are contained in this repo which are User flags

Flag Name

DISABLED (1 << 41)

Flag Description

User is currently temporarily or permanently disabled.

Extra Info

• [ X ] Flag is documented
• [ X ] I got this flag from this source: https://flags.lewistehminerz.dev/

My Notes

I wrote a script for a Discord bot to return all users and their publicFlags. Several people in a couple of servers I'm in have this flag, and yet they are currently active and not disabled. This must be incorrect.

Flag Name

SOCIAL_LAYER_INTEGRATION

Flag Description

Unknown.

Extra Info

1 << 27 (134217728)

• Flag is documented
• I got this flag from this source: URL

Hello!

I was filling out the "capture the flag" form and came upon the "i have verified my phone number" checkbox. I have verified it before, but i removed it from my account about 2 weeks after and it is not currently linked. Should I check that box?

Flag Name

CERTIFIED_MODERATOR

Flag Description

Discord Certified Moderator

Extra Info

• Flag is documented
• I got this flag from this source: https://discord.com/developers/docs/resources/user#user-object-user-flags

Hi all.

Looking to redo the site. It was very rushed after all in its initial development and is no longer a very good place for actually reading up on the flags. I'll probably redo it using Astro so it's SSGed and no JS is actually required to run it. Logo is more of an optional thing and it's far from my priority, so I probably won't worry about it for the design.

For a redesign, the .json files will stay where they are (/flags/<...>.json) so any integrations that use these files (which I'm aware of a couple) will work fine even after the redesign, although the files will probably be minified in the future. Another thing I want to do is add a new "public" field to flags to document if the flag is exposed to other users (think flags vs public_flags). @Lulalaby has a good table for this already so that's a good starting point.

I'm mainly just here to ask about what people would want from a redesign - how the content should be presented is the biggest issue for me since I am not too sure on the best way of presenting our data. Another thing is, during this redesign, I want to branch out to add the rest of the flag types that aren't documented at present (like #27), so I'd need to know the best way of designing around this (separate pages? one page with a table of contents?).

Hopefully we can get a much more pleasing site out soon, and also drop that tagline that has been sticking around for 3 years. Eugh.

1 << 11 is currently the only flag missing from our list that we know about. Some say it was a reserved flag that was never used, some say it's a mysterious flag that will lead to your death¹!

^{1: no one said this}

Anyway, it would be great if we could document whatever this mystery flag is. Someone already datamined the Discord client and didn't find anything regarding it. Maybe someone else can find it? I don't know. Maybe I missed something.

I was interested in the premium flags object pertaining to what the values were and how to decode it. Does anyone have a table for premium flags or is there some prior documentation?

Thanks.