investigate lazy guild implementation against channel overwrite changes
I looked over my implementation while refactoring dispatcher and found out that i kinda don't action on that. maybe it's dealt with by the client, since overwrites change, the guild member list used is different as a different id is generated, though #32 isn't implemented, and I don't know if it'll affect behavior or not.