7 Commits

Author	SHA1	Message	Date
projectmoon	3d2eb14cd3	Change room in context to origin_room, add active_room. ... The context now knows about origin room (the room where the command was executed), and the "active room," which is the room that the user wants the command to apply to. If no active room is defined, then the origin room acts as the active room. In a public room with the bot, the active room is also the same as the origin room.	2021-05-30 14:18:56 +00:00
projectmoon	49db0062a3	Various improvements to bot responses. ... - Do not display username pill with quoted HTML replies. - Do not attempt to create matrix.to link in plain text replies. - Move plain text formatting responsibility outside of matrix send_message function.	2021-05-26 22:20:53 +00:00
projectmoon	4ae871224a	Remove ExecutionError, as it is unnecessary.	2021-05-26 21:25:32 +00:00
projectmoon	495df13fe6	Do not automatically create accounts; use enum to show this instead. ... Instead of automatically creating a user account entry for any user executing a command, we use an Account enum which covers both registered and "transient" unregistered users. If a user registers, the context has the actual user instance available, with state and everything. If a user is unregistered, then the account is considered transient for the request, with only the username available.	2021-05-26 14:20:18 +00:00
projectmoon	5d002e5063	Add ability to store user active room, with skeleton accounts. ... - Adds a user_state table, currently only with active_room. - A user must have an account to take advantage of state. - Now, all users will get an 'account' even if they don't explicitly register. - Bonus: converts user queries to compile-time checked macros. To support these automatically created "accounts," the accounts table now also has an account_status column, indicating if the user is registered or not (or pending activation--future use). The User model has been updated with extra properties from the state, and the user is now carrried in the Context during command execution. A user is ensured to be created before executing the command.	2021-05-25 22:29:01 +00:00
projectmoon	4557498ac6	Improved command logging, sensitive to secure commands.	2021-05-22 22:17:33 +00:00
projectmoon	34ee2c6e5d	Consider command execution secure when proper conditions are met. ... - If the room is end-to-end encrypted. - If only the sending user and the bot are present in the room. This lays groundwork for sensitive commands like registering a user account with the bot.	2021-05-21 22:28:45 +00:00