Thanks for the clarification. By “persist across restarts,” I’m referring to the fact that if I just install the agent in my container, it won’t persist if I restart the container, unless I install it on a volume which seems clunky. Running the agent alongside in a separate container with network access is the solution I was looking for.

On the Redis and Valkey restores, that makes sense. Disaster recovery is my use case anyway. Do you document the manual restore process for those? I didn’t notice it in a brief review of the docs, but I may have overlooked it.

This looks exciting! A couple of questions:

1. How would I deploy an agent into an existing docker container in a way that makes it persist across restarts? Most of my databases are running in containers.
2. Regarding redis and valkey: what good does backup do without restore? Not trying to denigrate; I just really want to understand how that is useful.

Thanks for building this!

This has been my experience with Matrix, and the message decryption problems are a dealbreaker. I hope the person who replied to you saying those have very recently been fixed is correct, but the fact that such a fundamental feature was broken for so long leaves me with little confidence in Matrix. I had this problem years ago on a Matrix community, then again maybe a year ago on a different community, and even more recently on my self-hosted instance. Don’t understand how you can push a chat platform that effectively doesn’t deliver ~1/12 messages to random users and let that issue hang around for years.

XMPP looks really interesting as an alternative. Hope that development continued at a brisk pace.