-
-
Notifications
You must be signed in to change notification settings - Fork 7.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fetch link metadata on sender instance rather than receiver instances #12738
Comments
This would require federating preview information. Also it doesn't account for cases where the preview information changes -- and since Updates on statuses are discarded, this means that previews are effectively frozen at time of receipt. |
To elaborate, it's not even a question of trust, but a question of needs as well. Do Mastodon, Pleroma, and Misskey agree on a specific interpretation of how to preview a link? Does that cover all possible use-cases? There's OpenGraph, OEmbed, Twitter-specific properties, who knows what else. |
i dunno, we could at least federate the properties mastodon wants as a Link attachment and then ask if anyone wants any additional properties. I see the og/oembed/twitter stuff as an implementation detail—I'm imagining high level properties like "image", "title" and "summary", not sending over all the low-level stuff we use to construct that. i'm not too worried about trust—sites can make their previews whatever they want anyway. |
We could attach a Link with
|
Pitch
Rather than fetching every link that comes in with a post, possibly causing a DDoS on a small target webserver, fetch the metadata on the sender side and attach it to the status object in some way.
Motivation
Even with the random delay, there's still a significant amount of load that can come from requests for page metadata for posts from users with lots of followers from different instances. Misleading metadata is a non-issue as it's already possible to create a redirect page with misleading information on it for Mastodon to consume.
The text was updated successfully, but these errors were encountered: