v0.3.0-rc1

Added

• Logging in with a bot (see wiki for usage).
  • You can log in with a personal Telegram bot to appear almost like a real user without logging in with a real Telegram account.
• Replacing your Telegram account's Matrix puppet with your Matrix account (see wiki for usage).
• Formatting options for relaybot messages.
  • Real displaynames are now supported and enabled by default.
  • State events (join/leave/name change) can be independently disabled by setting the format to a blank string.
• New config sections
  • Proper log config, including logging to file (by default)
  • Proxy support (requires installing PySocks)
  • Separate field for appservice address for homeserver (useful if using a reverse proxy).
• New permission levels to allow initiating bridges without allowing puppeting and to allow Telegram puppeting without allowing Matrix puppeting.
• Telematrix import script (see wiki for usage).
• Provisioning API (see wiki for more info).
• DBMS migration script (see wiki for usage).

Improved

• Tabs are now replaced with 4 spaces so that Telegram servers wouldn't change the message.
• Help page now detects your permissions and only shows commands you can use.
• Moved Matrix state cache to the main database. This means that the mx-state.json file is no longer needed and all non-config data is stored in the main database.
• Better lxml-based HTML parser for Matrix->Telegram formatting bridging. lxml is still optional, so the old parser is used as fallback if lxml is not installed.
• Disabled Telegram->Matrix bridging of messages sent by the relaybot. Can be re-enabled in config if necessary.

Fixed

• A ValueError in some cases when syncing power levels.
• Telegram connections being created for unauthenticated users possibly triggering spam protection connection delays in the Telegram servers.
• Logging out if a portal had been deleted/unbridged.