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

Credo

Browse Source
This commit is contained in:
Mark Felder 2021-06-09 11:09:14 -05:00
parent 2a47156b87
commit 5f7901cc48
2 changed files with 10 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

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

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

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