Repository navigation
docs: replace legacy twitter.com links on policy/terms pages - #422
Merged
Merged
Conversation
Update stale twittercommunity.com, blog.twitter.com, and developer.x.com/docs/twitter-for-websites links to their current X equivalents (devcommunity.x.com, blog.x.com, help.x.com, x.com/en/privacy, and in-repo x-for-websites pages). Pages: developer policy (5 links), restricted use cases (3), developer agreement (2), changelog (1).
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Replaces stale
twittercommunity.com,blog.twitter.com, anddeveloper.x.com/docs/twitter-for-websites/...hyperlinks with their current X equivalents. These were surfaced during a strategic deal review of the Developer Policy page; the same link families were then fixed everywhere else in the repo. No remaining occurrences of these link families.Changes
developer-terms/policy.mdx(5 links, per the approved side-by-side table)twittercommunity.com/t/policy-clarification-automated-replies-and-mentions/94444devcommunity.x.com/t/policy-clarification-automated-replies-and-mentions/94444twittercommunity.com/t/policy-clarification-aggressive-following-and-inorganic-following-behavior/92769devcommunity.x.com/t/...-inorganic-following-behavior/92769blog.twitter.com/developer/en_us/topics/tips/2018/automation-and-the-use-of-multiple-accounts.htmlblog.x.com/developer/en_us/topics/tips/2018/automation-and-the-use-of-multiple-accountsdeveloper.x.com/docs/twitter-for-websites/overview(dead)help.x.com/en/x-for-websites-ads-info-and-privacydeveloper.x.com/docs/twitter-for-websites/privacy(dead)x.com/en/privacydeveloper-terms/restricted-use-cases.mdx(3 links)devcommunity.x.com/.../94444devcommunity.x.com/.../92769devcommunity.x.com/t/policy-clarification-multiple-applications-for-the-same-use-case/92080developer-terms/agreement.mdx(2 links)/x-for-websites/embedded-posts/overview(internal; old URL redirected to docs.x.com home)/x-for-websites/timelines/overview(internal; old URL redirected to docs.x.com home)changelog.mdx(1 link)blog.x.com/developer/en_us/topics/tools/2017/new-apis-to-power-the-future-of-customer-engagement-in-direct-meVerification
mintlify devlocally and read the renderedhrefof every changed link on all four pages; internal/x-for-websites/...targets render ("Embedded Posts", "Embedded Timelines").grepconfirms no remainingtwittercommunity.com,blog.twitter.com, ordeveloper.x.com/docs/twitter-for-websiteslinks in the repo.