Any idea if this always happens or only w/ a specific type of attachment?

Ignore what I previously wrote, I imagined it.

Do you know if this worked with a different bridge control + bridge combo? Or when we weren't running bridges and it was all in the cloud? I'm looking for any clues that a happy path might already exist and if not then it needs a parser. I collected raw data to get a sense of what a proper preview should look like so there's progress.

Looks like there might be a flag in either the client or server code called ddScan. It is possible that crafting rich links was never implemented (talking to someone on their discord) so I'll start by looking at the bb config.

Is there any benefit to supporting rich links? Doesn't the Beeper/Element client make them look pretty anyway by loading them up on the clients themselves?

Looks like there might be a flag in either the client or server code called ddScan. It is possible that crafting rich links was never implemented (talking to someone on their discord) so I'll start by looking at the bb config.

dltacube, how far have you looked into this? It also seems that the BB connector never implemented it, there's a "TODO Richlinks" in api.go

Looks like there might be a flag in either the client or server code called ddScan. It is possible that crafting rich links was never implemented (talking to someone on their discord) so I'll start by looking at the bb config.

dltacube, how far have you looked into this? It also seems that the BB connector never implemented it, there's a "TODO Richlinks" in api.go

Whatever I'm thinking about in terms of these features will need to be fleshed out on our end. I've dug deep into bbb's output using web sockets and honestly if you point to the problematic ones I'll tell you how they behave.

Whatever I'm thinking about in terms of these features will need to be fleshed out on our end. I've dug deep into bbb's output using web sockets and honestly if you point to the problematic ones I'll tell you how they behave.

Do you know what the UID values mean in the JSON for the payloadData object? Here's an example message:
data.json

Parsing this is a mess and the BB app implementation looks nothing like this is way simpiler but I have no idea how to get this JSON instead of what the server sent above:

"payloadData": {
          "type": 0,
          "urlData": [
               {
                    "imageMetadata": {
                         "size": "Size(0.0, 0.0)",
                         "URL": {
                              "NS.relative": "https://jsonformatter.curiousconcept.com/icons/jf/mstile-144x144.b0ef4bd01d6cb25ab71ae707ed7ac226.png"
                         }
                    },
                    "videoMetadata": null,
                    "iconMetadata": {
                         "size": "Size(0.0, 0.0)",
                         "URL": {
                              "NS.relative": "https://jsonformatter.curiousconcept.com/icons/jf/apple-touch-icon.g79xknzqx7c.png"
                         }
                    },
                    "itemType": "website",
                    "originalURL": {
                         "NS.relative": "https://jsonformatter.curiousconcept.com/#"
                    },
                    "URL": {
                         "NS.relative": "https://jsonformatter.curiousconcept.com/"
                    },
                    "title": "JSON Formatter & Validator",
                    "summary": "Format and validate JSON data so that it can easily be read by human beings.",
                    "siteName": null
               }
          ],
          "appData": null
     }
`