Skip to content

Updated providers.json to use X instead of Twitter following rebrand and schema change #18767

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.

Sign up for GitHub

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

Merged
reivilibre merged 2 commits into from
Sep 26, 2025
Merged

Updated providers.json to use X instead of Twitter following rebrand and schema change #18767

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
16482bf
Updated providers.json to use X instead of Twitter
HammyHavoc Aug 2, 2025
2aa1227
Newsfile
reivilibre Sep 24, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 6 additions & 5 deletions synapse/res/providers.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,14 +1,15 @@
[
{
"provider_name": "Twitter",
"provider_url": "http://www.twitter.com/",
"provider_name": "X",
"provider_url": "https://x.com/",
"endpoints": [
{
"schemes": [
"https://twitter.com/*/moments/*",
"https://*.twitter.com/*/moments/*"
Comment on lines -8 to -9
Copy link
Copy Markdown
Contributor

@clokep clokep Aug 2, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think you probably want to keep these URLs?

Copy link
Copy Markdown
Contributor Author

@HammyHavoc HammyHavoc Aug 3, 2025 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Moments isn't a feature anymore, and Twitter URLs won't work after the domain change to x.com, despite 301 redirects, as they otherwise won't be in the schema.

"https://x.com/*",
"https://x.com/*/status/*",
"https://*.x.com/*/status/*"
],
"url": "https://publish.twitter.com/oembed"
"url": "https://publish.x.com/oembed"
}
]
},
Expand Down
Loading
⚡