a1batross
/
pleroma
1
0
Fork 0
Code Issues 1 Pull Requests Releases Wiki Activity

Formatting of the comment

This commit is contained in:
Mark Felder 2021-06-09 11:58:51 -05:00
parent d12e62c0b6
commit 6aa7fc15df
2 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
lib/pleroma/web/metadata/providers/open_graph.ex
View File

@ -82,9 +82,9 @@ defmodule Pleroma.Web.Metadata.Providers.OpenGraph do
# Not using preview_url for this. It saves bandwidth, but the image dimensions will # Not using preview_url for this. It saves bandwidth, but the image dimensions will
# be wrong. We generate it on the fly and have no way to capture or analyze the # be wrong. We generate it on the fly and have no way to capture or analyze the
# analyze the image to get the dimensions. This can be an issue for apps/FEs # image to get the dimensions. This can be an issue for apps/FEs rendering images
# rendering images in timelines too, but you can get clever with the aspect ratio # in timelines too, but you can get clever with the aspect ratio metadata as a
# metadata as a workaround. # workaround.
"image" -> "image" ->
[ [
{:meta, [property: "og:image", content: MediaProxy.url(url["href"])], []}, {:meta, [property: "og:image", content: MediaProxy.url(url["href"])], []},

6
lib/pleroma/web/metadata/providers/twitter_card.ex
View File

@ -69,9 +69,9 @@ defmodule Pleroma.Web.Metadata.Providers.TwitterCard do
# Not using preview_url for this. It saves bandwidth, but the image dimensions will # Not using preview_url for this. It saves bandwidth, but the image dimensions will
# be wrong. We generate it on the fly and have no way to capture or analyze the # be wrong. We generate it on the fly and have no way to capture or analyze the
# analyze the image to get the dimensions. This can be an issue for apps/FEs # image to get the dimensions. This can be an issue for apps/FEs rendering images
# rendering images in timelines too, but you can get clever with the aspect ratio # in timelines too, but you can get clever with the aspect ratio metadata as a
# metadata as a workaround. # workaround.
"image" -> "image" ->
[ [
{:meta, [property: "twitter:card", content: "summary_large_image"], []}, {:meta, [property: "twitter:card", content: "summary_large_image"], []},