Add database table to keep track of chat mapping #2
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
For now we could avoid adding an extra database, and can store all relevant state in the deltachat database. This is super flaky for several reasons, so we will run into a load of problems later:
A table to map an outside chat to a relay group would help a lot to keep things consistent.
We could also have a table to remember which group is the crew group; the way this is guessed right now allows malicious users who were verified with the bot once to hijack the crew group (though not silently).
It might also make sense to have a directory with assets (e.g. user and group avatars), and a database table could keep track of the file locations / to which chats/users they belong.
Another table might keep track of config options, e.g. the prefix for relay group titles.