During a refactor the guild.Upsert somehow got removed and I didn't notice it
because my test account was synced. So to avoid this in the future we output
the number of guilds the database knows, the number discord says we have and
then how many the database has after we purge guilds the user has left.
refs #8
guilds status will list the guild names, their ids, and whether or not the
guild is bridged.
guilds bridge <guildID> will bridge the guild with the given ID. If you add the
--entire flag, it will create a portal for each channel on the guild.
guilds unbridge <guildID> will stop bridging the guild with the given ID and
remove all portals for that guild.
Refs #8
This isn't exactly the same as the puppet bridge, basically it removes the
puppetID from the url and just works against the logged in user.
There is a known errata right now where some times all channels aren't left
when unbridging a guild. I figured it's more important to get some more testing
on this while I try to figure that out in the mean time.
Also when you call /guilds/:guildID/joinentire, it joins each channel serially.
I tried to make this concurrent but I maxed out the rate limit. We can do this
in the future, but again, rather get this into everyone's hands sooner rather
than later. I also did the same thing with unbridge and had to revert for the
same reasons.
Refs #8
This was caused by some early attempts at not replaying messages. That was
fixed by tracking messages explicitly but these early returns with no logging
were never removed.
Fixes#23
This commit also points to my fork of discordgo which makes it look like the
official client which is the only way to get the actually contents of a dm
when not authorized as a bot.
* The bot now properly joins the management room
* The management room is persisted in the database
* Welcome/help messages are sent in the management room
