diff --git a/README.md b/README.md
index 24d6d14..cfee5f3 100644
--- a/README.md
+++ b/README.md
@@ -14,3 +14,11 @@ The core systems may be updated to Debian 11 and/or Postgresql 13 during the cou
 [![](https://xmpp.net/badge.php?domain=chinwag.org)](https://xmpp.net/result.php?domain=chinwag.org&type=server)
 
 [![](https://compliance.conversations.im/badge/chinwag.org)](https://compliance.conversations.im/server/chinwag.org)
+
+## Future plans
+In the medium to long term, I'd like the service a little better integrated on the Mastodon side, but I have no real clue about working with Ruby right now. Here are some items on the wishlist.
+
+1. The Mastodon user preferences should allow the user to activate/deactivate messaging services, so it's completely off if someone does not want it. Right now the user is "created" on first use, but there's no way to kind of destroy the ejabberd user again afterwards if it's no longer required.
+2. Rather than use the Mastodon password, allow (require?) setting of a secondary application password via user preferences in a separate table and use that. Could also be used for multiple passwords, per device and permit granular revokation of a single device's access.
+3. Can the JSXC project's authentication hub project or similar be applied here for a web chat client authenticated from the current logged-in Mastodon user?
+4. Pre-configured mobile and/or desktop app. Fork/embed a project like JSXC or ConverseJS? It'd be nice to provide a reference client to be able to simply document "how to chat" for new users.