Tulir Asokan
Tulir Asokan
This should probably be split into two issues: 1. Ignore unknown keys in appservice registration files 2. Implement sending ephemeral events to appservices ([MSC2409](https://github.com/matrix-org/matrix-doc/pull/2409))
Is `bridge`->`encryption`->`default` set to `true`?
There's no hard limit, I've been logged in with the same session for over a year. WhatsApp probably just randomly kicks people out if they feel like it.
Are you using an up to date version of the bridge?
Releases happen occasionally, there's no schedule @moj02090 the `:latest` docker tag will use the master branch. You can also use commit hash + architecture (e.g. `:181f87ab2516fdfae64337eec476f9e285c500bb-amd64`). Also keep in mind...
Signal profile names also work better now (but sometimes don't work). Those are enabled by default and work on multi-user instances. Contact names are more reliable since they don't involve...
Doesn't seem possible, but you can already just try to send a message
It probably requires adding a new request type to signald that checks if a phone number is on Signal. `get_profile` doesn't do that.
You don't get an uuid (unless you already have the user in contacts or something) nor an error
You can do trust-on-first-use by just manually marking the device on the bridge bot as verified, other than that it can't currently be verified. (in element web: click on "1...