Rocket.chat: Posting twitter links doesn't display the tweet.

[jherman]

Description:

When posting a twitter link, it's expected to see the tweet directly below it (similar to how you post a website url, you will see a brief view of it below)

Steps to reproduce:

1. Enter a channel
2. Directly link a tweet (ex. https://twitter.com/testing/status/1135187357513199616)
3. Observe no embedded link shown

Expected behavior:

We should see the tweet directly

Actual behavior:

Server Setup Information:

• Version of Rocket.Chat Server: 1.2.3
• Operating System: Centos 7
• Deployment Method: Docker
• Number of Running Instances: 1
• DB Replicaset Oplog: Enabled
• Node Version: 8.11.4
• MongoDB: 4.0.10

[geekgonecrazy]

I’m not sure if this is a front end issue or if backend isn’t fetching the oembed.

[tassoevan]

Preview is built on back end. Does the server have Internet access?

[jherman]

Well when I tested this, I tested on my personal server which didn't work, then I tested it on rocket.chat's public server and it didn't work. However I just tested this now, and it's apparently working today. I'm assuming it's what you said and the issue was on rocket.chats end. I'm concerned that this relies on rocket chats servers. Are they listening in on chats by filtering our links through them?

[geekgonecrazy]

By backend we mean your servers backend. So relies on your servers ability to access the internet. Not it’s ability to reach us.

We for sure don’t have everyone contacting our servers for previews. That would be insane :)

[geekgonecrazy]

I can confirm this was happening on open and nothing has changed infrastructure wise that would have prevented it from talking to twitter to get the preview.

[jherman]

Got it Aaron. Glad to hear there's no snooping 👍 In any case I still don't understand why it's now working when it wasn't before on my server. I have not touched the container or host it's been running in. Not to mention this was happening on the public server as well. I'm baffled.

[tassoevan]

I bet some change in the message attachment rendering was causing it, looking into some changelogs from latest versions. @jherman I'll close this issue by now, but feel free to reopen it if this bug comes back.

[jherman]

It's happening again @tassoevan. Any idea?

[PeGaSuS-Coder]

I can reproduce the issue at least in the mobile app and mobile browser, at least regarding Twitter URLs. GitHub URLs and others seem to work fine.

Screenshots below:

Mobile App

Mobile Browser

Desktop Browser

[awunder]

the issue still (or again) exists on 3.2.1... neither twitter nor bloomberg links work, see:

vs. same url in slack:

BBG:

vs. same link in slack:

[rzaSF]

Been wondering about this one for some time. Is this something we just need to live with? Is this a deployment / configuration issue or? Never saw Rocket.Chat behave like the other collaboration products. Is there something we can do about it?

[rzaSF]

Ok, so I stumbled on this (https://github.com/RocketChat/Rocket.Chat/issues/12924#issuecomment-646759538) and added Twitter's script as discussed in the #12924 comment above. That seemed to do the right thing. It should just be rolled into Rocket.Chat as a configurable default IMHO. This is too much work for expected behavior (as we see in virtually any collaboration package today).

[awunder]

@rzaSF be sure to read his latest comment https://github.com/RocketChat/Rocket.Chat/issues/12924#issuecomment-703028598

the bloomberg links are still asking me if i am a robot btw.