Now that we rely on the schedule being available on every startup (not just for building), I propose we add a caching mechanism so that the bot can handle a single fault in loading the cache from the original source.
Stacked PR Chain: rei:wedf/a
PR
Title
Status
Merges Into
#130
Allow disabling IRC bridge by not configuring one, to prevent crash
-
#131
Fix !schedule view falling over with long schedules
#130
#133
(Draft) Try to disconnect the Conference bot from being so reliant on Pentabarf (best effort)
#131
#132
(Draft) Add a JSON schedule loader
#133
#134
(Draft) Fix some misc bugs
#132
#135
(Draft) Disable features relating to Q&A if desired
#134
#136
(Draft) Refactor the backends to be called backends
#135
#137
(Draft) Use a custom 'locator' state event rather than m.room.create.
#136
#138
👉 (Draft) Add a schedule cache as a fallback for if the original schedule goes offline
#137
#139
(Draft) Add a status command to get some information about the bot and its situation
Now that we rely on the schedule being available on every startup (not just for building), I propose we add a caching mechanism so that the bot can handle a single fault in loading the cache from the original source.
Stacked PR Chain: rei:wedf/a
m.room.create.