| 29 Aug 2023 |
 starnell | I'm trying to think of a way for me to host mautrix-whatsapp at home (on a computer that doesn't have a port forwarded to it), and somehow still have the element.io iOS app get push notifications over cellular. Any suggestions? | 22:09:17 |
 tulir | well bridges aren't really related to push notifications in any way, but ignoring that part, having a homeserver in the cloud and bridge locally works perfectly fine | 22:12:43 |
| tulir | (although the primary benefit of such a setup is security, it wouldn't help with hosting costs as the homeserver is the heavy part) | 22:13:36 |
| tulir | another option is to simply forward a port to the computer, e.g. by getting a cheap vps for proxying | 22:14:13 |
| 30 Aug 2023 |
 jjj333_p (any pronouns) | ^ the main thing is you need to have a homeserver (or maybe beeper??) | 01:49:51 |
| jjj333_p (any pronouns) | * ^ the main thing is you need to have a selfhosted homeserver (or maybe beeper??) | 01:50:10 |
 Surak | I have a few rooms where both my matrix account and my whatsapp ghost are in there 🤔 can I remove the ghost safely? | 10:33:50 |
|  andk01 joined the room. | 11:18:04 |
| andk01 | Hi all! Short question regarding the end-to-bridge encryption: the room with the whatsapp bot is supposed to be encrypted (in the room settings), but I get a red warning icon beside the message saying "unencrypted". The same happens for WA chats, but in this case the icon says something like "encrypted from deleted device". How can I check whether the encryption is enabled? | 11:30:06 |
 Malte E | In reply to @andk01:tchncs.de
Hi all! Short question regarding the end-to-bridge encryption: the room with the whatsapp bot is supposed to be encrypted (in the room settings), but I get a red warning icon beside the message saying "unencrypted". The same happens for WA chats, but in this case the icon says something like "encrypted from deleted device". How can I check whether the encryption is enabled? The bridge bot's messages are unencrypted. Your own messages sent from the official app are unencrypted. Messages from whatsapp ghosts should be encrypted by the bridge bot's session. Not sure why the bot messages are unencrypted, but your own messages are unencrypted because the bridge does not have a verified session to encrypt from. | 11:57:56 |
| andk01 | In reply to @malte:maltee.de
The bridge bot's messages are unencrypted. Your own messages sent from the official app are unencrypted. Messages from whatsapp ghosts should be encrypted by the bridge bot's session. Not sure why the bot messages are unencrypted, but your own messages are unencrypted because the bridge does not have a verified session to encrypt from. Is this normal, or just because the homeserver did not enable the encryption according https://docs.mau.fi/bridges/general/end-to-bridge-encryption.html ? What I can do to verify the bot session? | 12:09:36 |
| Malte E | you can't verify the bot's session | 12:10:58 |
| Malte E | it's all normal and expected | 12:11:05 |
| Malte E | the use of e2be is of limited use, because an attacker would still be able to read the messages on your homeserver. I suppose that keys are not stored by the bridge, so messages will be stored encrypted by synapse, so an attacker would only be able to intercept messages while they have control over your bridge. | 12:13:27 |
| Malte E | * e2be is of limited use, because an attacker would still be able to read the messages on your homeserver. I suppose that keys are not stored by the bridge, so messages will be stored encrypted by synapse, so an attacker would only be able to intercept messages while they have control over your bridge. | 12:15:35 |
| andk01 | OK, but the homeserver admin can read the messages when e2be is enabled? And how can ich verify if e2be is enables? | 12:18:13 |
| Malte E | Anyone with full access to the bridge can read the message. The homeserver admin cannot, but typically they are the same person.
Oh well, I suppose since you can host bridge and homeserver on different machines, e2be does make quite a bit of sense, depending on the scenario
e2be is indistinguishable from matrix e2ee. If the room says it's encrypted, e2be is enabled. Messages from remote platform ghosts should come in encrypted, your average client would indicate whether or not they are. | 13:53:18 |
| andk01 | So if I understand you correctly its as follows:
Matrix client (Element) <-> bridge is encrypted if the room says so.
Bridge (homeserver) <-> WhatsApp universe should be encrypted by WhatsApp protocol, and can be verified in WhatsApp messenger. Right? | 14:06:44 |
| Malte E | correct | 14:09:58 |
| Malte E | the bridge must temporarily decrypt messages, because whatsapp and matrix have incompatible message formats and encryption standards. | 14:10:23 |
| andk01 | Right. Nevertheless, I don't understand why the warning icon exists. From logical point it should not appear since it relates just to the matrix-client <-> bridge part (so just the matrix room), which should be fully encrypted by matrix protocol (if room says so). | 14:25:56 |
| tulir | https://docs.mau.fi/bridges/general/troubleshooting.html#why-are-messages-showing-up-as-encrypted-by-a-deleted-session | 14:26:17 |
| andk01 | Ah there is a FAQ, how could I missed that! Thanks tulir , and also Malte E for the extensive explanations! | 14:34:02 |
| Malte E | What was the reason that the bridge bot's messages aren't encrypted? I know they typically don't contain confidential information, but is there any real benefit to not encrypting them? | 14:51:56 |
| andk01 | Yes, good question. I would consider telefone numbers which are shared in the bridge bot room confidential information. | 15:45:37 |
 GitHub | [mautrix/whatsapp] trpl-dev starred the repo | 16:08:23 |
|  dyoxin joined the room. | 18:46:54 |
| GitHub | [mautrix/whatsapp] lukx33 starred the repo | 20:35:07 |
| 31 Aug 2023 |
 Clumsily6239 | How do I backsync history for just one contact? | 02:39:39 |
 Erik | In reply to @clumsily6239:matrix.org
How do I backsync history for just one contact? Afaik it is not possible as backfill does only happen on login | 06:16:07 |
