mirror of
https://github.com/discordeno/discordeno.git
synced 2026-06-04 09:50:07 +00:00
* add guild safety | closes #3020 * Adds approx guild count | closes #3078 * Team member permissions | closes #3105 According to current documentation DiscordTeamMemberRole#Owner does not have a value anymore, in this commit it still had so it is included to be changed by a later commit * Default thread ratelimit | closes #3216 * Entitlements and SKUs | closes #3219 The entitlements events needs testing for the typing * Typing endpoint docs update | closes #3222 * Add guildScheduledEventId to CreateStageInstance | closes #3228 * Add listSkus helper I did forget it in the commit before * Update Application Endpoints | closes #3230 * Update documentation | closes #3233 * fix starting a thread in forum | closes #3234 & closes #3036 * Add fired events on get widget endpoint | closes #3235 * Add fired events on get widget endpoint pt2 | closes #3236 * Update SKU and Entitlement fields | closes #3238 * Split permissions for expressions and events | closes #3249 * Make GetEntitlements#excludeEnded more specific | closes #3251 * Fix thread/forum channel docs regression | closes #3252 * Another description change for GetEntitlements#excludeEnded | closes #3253 * Document applied_tags on Execute Webhook | closes #3265 * Fix entitlement event types
Discordeno Rest
A standalone and server-less REST module with functionality of REST, independently.
- Easily host on any serverless infrastructure.
- Easy to use and setup with Cloudflare Workers (FREE for 100K requests per day!)
- Freedom from global rate limit errors
- As your bot grows, you want to handle global rate limits better. Shards don't communicate fast enough to truly handle it properly so this allows 1 rest handler across the entire bot.
- In fact, you can host multiple instances of your bot and all connect to the same rest server.
- REST does not rest!
- Separate rest means if your bot for whatever reason crashes, your requests that are queued will still keep going and will not be lost.
- Seamless updates! When you want to update and reboot the bot, you could potentially lose tons of messages or responses that are in queue. Using this you could restart your bot without ever worrying about losing any responses.
- Scalability! Scalability! Scalability!