There's an upstream task https://secure.phabricator.com/T13018 and some related discussion at https://meta.discourse.org/t/onebox-doesnt-render-boxes-for-phabricator-urls/74421

Interestingly, the Open Graph protocol project itself is now in a really abandoned state.

https://github.com/facebookarchive/open-graph-protocol/pull/50

Syncing from an answer I have made on our internal Slack in early September following this question by @gmodena asking how to integrate tools in Slack

Are you aware of any effort to integrate phab, gerrit and gitlab with Slack? E.g. bots like https://github.com/etcinit/phabulous

For Gerrit I looked at how Slack could potentially render a preview of the link. Slack relies on embedded data at the target page (a process they name URL unfurling apparently based on OpenGraph / Twitter card / <meta> or something.

Slack has a debugger at https://api.slack.com/tools/unfurl-debugger (under Team pick "████████████" then under URL insert some url such as a Gerrit change, Phabricator page or Gitlab page and see what happens.

For Gerrit that gives:
Result
No usable content found.
Log

• Request to fetch https://gerrit.wikimedia.org/r/c/integration/quibble/+/903255 returned HTTP 206
• Type of resource is text or HTML
• No OpenGraph or Twitter data found in meta tags
• Found data in meta tags

Gerrit doesn't seem to provide any relevant meta tag beside the description Gerrit Code Review

That is similar for Phabricator (which is the purpose of this task). If I ask parse https://phabricator.wikimedia.org/T2001

Result
No usable content found.
Log

• Request to fetch https://phabricator.wikimedia.org/T2001 returned HTTP 200
• Type of resource is text or HTML
• No OpenGraph or Twitter data found in meta tags
• Found data in meta tags

For Gitlab there are few issues filed such as:

• 21980 - Snippets should support OEmbed
• 18311 - Feature request: Embedding rich media in GFM

That is for the problem statement, continuing in next message

Interesting. Thanks!

As a side note, I'm sorry if Slack does not integrate better with stuff, but please understand me if I'm not inclined to contribute as volunteer to any integration with any specific proprietary software like Slack in general. Being involved in Slack details makes me feel very uncomfortable. I also don't know why Slack is required to work in WMF for most positions. This seems like something to think about, even if OT here. (But were we can talk about Slack?)

To add support to OpenGraph, I think we need to explore what we have at the moment, that is, probably:

https://secure.phabricator.com/rP49b57eae7df52c189aef1d973823c697fc97fd4b
https://secure.phabricator.com/T13018
https://secure.phabricator.com/T13018#233394

In particular, from Evan:

To move forward, we'd probably need to add methods like setOpenGraphTextDescription(), setOpenGraphRemarkupDescription(), and setOpenGraphEmptyDescription() to StandardPageView

Probably, we need to just see the last link and take inspiration. Probably not. But that is an interesting starting point.

Adding metadata should be achievable since Phabricator is written in PHP and we have good relation with upstream. One would have to pick a format to support given:

• Facebook OpenGraph is apparently abandoned (edit: as noted above by Valerio T288117#8931772
• Twitter Card might be in a poor shape
• I don't know whether Slack supports OEmbed which was a tentative to establish a standard but is not one afaik :)

There is a 2010 task by Brion Vibber about adding OEmbed for MediaWiki which is T27854 and which has useful links.

For MediaWiki, I think that got implemented in 2020 via T157145 which went to use og meta tags. They are Facebook OpenGraph tags which are documented at https://developers.facebook.com/docs/sharing/webmasters/

In T288117#9356144, @valerio.bozzolan wrote:

...
As a side note, I'm sorry if Slack does not integrate better with stuff, but please understand me if I'm not inclined to contribute as volunteer to any integration with any specific proprietary software like Slack in general. Being involved in Slack details makes me feel very uncomfortable. I also don't know why Slack is required to work in WMF for most positions. This seems like something to think about, even if OT here. (But were we can talk about Slack?)

I hear you, I have mentioned Slack in my previous comment ( T288117#9356136 ) since the question was asked there and I did the analysis with Slack in mind and I merely copy pasted my answer. The reason is Telegram, Slack, Wordpress etc all more or less rely on Open Graph tags to be added to the task with `Slack being a detail :-)

To add support to OpenGraph, I think we need to explore what we have at the moment, that is, probably:

https://secure.phabricator.com/rP49b57eae7df52c189aef1d973823c697fc97fd4b
https://secure.phabricator.com/T13018
https://secure.phabricator.com/T13018#233394

In particular, from Evan:

To move forward, we'd probably need to add methods like setOpenGraphTextDescription(), setOpenGraphRemarkupDescription(), and setOpenGraphEmptyDescription() to StandardPageView

Probably, we need to just see the last link and take inspiration. Probably not. But that is an interesting starting point.

My guess is Facebook abandoned their repo/page in favor of the documentation https://developers.facebook.com/docs/sharing/webmasters/

Twitter has its own tags, then their documentation ( https://developer.twitter.com/en/docs/twitter-for-websites/cards/overview/markup ) mentions Facebook OpenGraph tags.

My conclusion is Facebook OpenGraph tags, short of being a standard, are the de facto most supported ones and I guess one can look at adding support for them in Phorge.