Skip to content
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

Twitter: Use OG resolver by default #499

Closed
leon-richardt opened this issue Jun 27, 2023 · 2 comments · Fixed by #522
Closed

Twitter: Use OG resolver by default #499

leon-richardt opened this issue Jun 27, 2023 · 2 comments · Fixed by #522

Comments

@leon-richardt
Copy link
Contributor

Since the Twitter API is now absurdly expensive, it is reasonable to assume that most hosters do not want to pay for an API key. Therefore, Twitter links should be handled by the Open Graph link resolver by default.

@M4tthewDE
Copy link
Contributor

This seems to be quiet hard to implement, since twitter does not like automated access to their website. Without passing a valid value in the Cookies, the meta tags cannot be resolved.

@KararTY
Copy link
Contributor

KararTY commented Jul 11, 2023

This seems to be quiet hard to implement, since twitter does not like automated access to their website. Without passing a valid value in the Cookies, the meta tags cannot be resolved.

Valid point, the solution is to make sure the user-agent includes the word "bot":
See matrix-org/synapse#11985 (review)

We will subsequently get all relevant OG tags.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants