Notes

Add ‘Reason’ request thing

I think a good way to do this is a wrapper request type that injects it

Webhook endpoints

Audit log model & endpoints

Allowed mentions

Things to test

Test using text-short and intern for certain strings

CANCELLED Shards need some way of making requests (get gateway, etc)

[X] Instead we just pass the gateway url to shards, it never changes, so w/e

Function to log out the bot, waiting for all stuff to end, etc

we’ll need some control messages that tell the client to enter a loop of waiting for all shards to signal that they are closed.

Shard shutdown process?

Send shutdown signal to shard
Shard shuts down and sends a control message with it’s own thread to the client stating that it is closed?
Client removes shard from the set of shards

Move from lists of objects to maps of id => object

Partial data

Presence info

linky: https://discordapp.com/developers/docs/topics/gateway#presence-update

Allow options for presences to be discarded

Pretty much nobody cares about presences on a bot but presences take up a lot of data (Turns out they don’t lol)

Share user data

instead of having a copy for each user object discord gives us. This is probably a much better optimisation that discarding presences.

Migrate from Transformers and MTL to Free monads

should be fun

KILL Use barbies for data that updates (w/ magic defaulting stuff for aeson idk?)