src/m2d/event-dispatcher.js

@@ -213,9 +213,9 @@ async event => {
 	if (!messageResponses.length) return
 	if (event.content["m.relates_to"]?.rel_type === "m.thread"){
 		api.sendEvent(event.room_id, "m.room.message", {
-			"body": "It seems like you sent this message inside a thread.",
+			"body": "⚠️ **This message may not have bridged to Discord in the way you thought it would!**\n\nIt seems like you sent this message inside a Matrix thread. Matrix threads don't work like Discord threads - they are effectively just „fancy replies”, not independent rooms/channels (any „thread-like appearance” is handled purely client-side - and even then, most Matrix clients don't handle it particularly well), and as such, they are bridged as replies to Discord. _Discord users will not be aware that you sent this message inside a thread - it will go directly onto the main channel. If the thread you sent this message in is old, such a random reply may be distracting to Discord users!_\n\nFor the sake of Discord parity (as well as better support in numerous Matrix clients - as stated above, most Matrix clients don't handle threads particularly well, and they just render in-thread messages as fancy replies), it is recommended to send threaded messages inside a separate Matrix room that gets bridged to Discord. If you sent this message in a pre-existing Matrix thread, please look around to see if anyone has created such a room for it. If this is the first message (ie. the thread was just created) or noone's made a thread-room for this thread, it is recommended you create one with `/thread <Thread Name>` (on Matrix) and continue the conversation there.\n\n*You can read more about the rationale behind this design choice [here](https://gitdab.com/cadence/out-of-your-element/src/branch/main/docs/threads-as-rooms.md).*",
 			"format": "org.matrix.custom.html",
-			"formatted_body": "It seems like you sent this message inside a thread.",
+			"formatted_body": "⚠️ <strong data-md=\"**\">This message may not have bridged to Discord in the way you thought it would!</strong><br/><br/>It seems like you sent this message inside a Matrix thread. Matrix threads don&#39;t work like Discord threads - they are effectively just „fancy replies”, not independent rooms/channels (any „thread-like appearance” is handled purely client-side - and even then, most Matrix clients don&#39;t handle it particularly well), and as such, they are bridged as replies to Discord. <i data-md=\"_\">Discord users will not be aware that you sent this message inside a thread - it will go directly onto the main channel. If the thread you sent this message in is old, such a random reply may be distracting to Discord users!</i><br/><br/>For the sake of Discord parity (as well as better support in numerous Matrix clients - as stated above, most Matrix clients don&#39;t handle threads particularly well, and they just render in-thread messages as fancy replies), it is recommended to send threaded messages inside a separate Matrix room that gets bridged to Discord. If you sent this message in a pre-existing Matrix thread, please look around to see if anyone has created such a room for it. If this is the first message (ie. the thread was just created) or noone&#39;s made a thread-room for this thread, it is recommended you create one with <code data-md=\"`\">/thread &lt;Thread Name&gt;</code> (on Matrix) and continue the conversation there.<br/><br/><i data-md=\"*\">You can read more about the rationale behind this design choice <a data-md href=\"https://gitdab.com/cadence/out-of-your-element/src/branch/main/docs/threads-as-rooms.md\">here</a>.</i>",
 			"m.mentions": { "user_ids": [event.sender]},
 			"m.relates_to": {
 				"event_id": event.content["m.relates_to"].event_id,