Roadmap

[kegsay]

Currently this project is a glorified HTTP wrapper with some /sync state handling and "Observer" pattern callbacks by default. This is fine for basic bots but there is much more scope for improving this. This issue maintains a list of ideas/features/improvements along with coarse timeframes for when I want to land them.

Short-term

• Intent-driven APIs: (inspired by the bridge component of the same name)
  • Will auto-join rooms if "not in room" errors are encountered.
  • Will try to assert that the client has enough power level to perform the intended action.
  • Should we do this by default or add a layer on top? If by default, can we turn it off? Per-request or globally?
• Scheduler API (inspired by the JS SDK class of the same name)
  • For both message sending and membership operations. JS SDK only does message sending.
• Olm encryption.

Medium-term

• Megolm encryption.
• Implement all known APIs (Endpoint checklist #9).
• Room timeline management (what JS SDK does)