Editorial Policy
CarryFeed pages are maintained for people who need clear public-link workflows, not exaggerated access claims. This policy explains how examples, limitations, and guide copy are checked against the tool.
How CarryFeed Keeps Claims Grounded
CarryFeed guide copy is checked against product behavior before major page rewrites are published: what public links can be pasted, what result appears, and which private or login-only sources fail.
The page should not claim private access, hidden media, or platform-only features that the public workflow cannot support.
How Public Links Are Tested
- Start with a public x.com or twitter.com URL, profile handle, or public post URL.
- Confirm whether the public page exposes video, image, GIF-style media, profile, post, or article-style data.
- Record the expected outcome, such as MP4 options, original-size image links, looping MP4-backed GIF media, or public viewer context.
- Retest examples when page copy changes or public platform behavior appears to change.
What Counts as Supported
Supported examples are public links that can be inspected without asking the user for an X login. A supported video page may show MP4 files and available quality options. A supported image page may show original-size image URLs when the public post exposes them. A supported viewer result may show public profile, post, media, or article context.
A result can still vary by post. CarryFeed describes what is available from the public link rather than promising that every post has the same file types or quality options.
Known Limitations
- Private, protected, deleted, suspended, restricted, or login-only content is not supported.
- CarryFeed does not bypass account privacy settings, paywalls, technical restrictions, or platform access controls.
- Some posts use embedded players, third-party cards, or platform behavior that does not expose a direct media file.
- Browser save behavior varies across iPhone, Android, desktop Chrome, Safari, Edge, and Firefox.
Agent and AI Access Boundaries
CarryFeed can expose public-link results in agent-readable forms for compatible browsers and AI workflows. The purpose is to pass along the same public context the page resolved: source URL, author or profile details, post text, article text when available, media metadata, and file options.
Agent access is read-only. CarryFeed does not expose tools for posting, liking, following, monitoring private accounts, starting downloads on behalf of an agent, or using an X account.
Update Cadence
Tool pages and support guides are checked when public platform behavior changes. CarryFeed updates affected page copy before expanding claims.
Primary references for public-link claims.
These sources help CarryFeed check public-post, profile, image, GIF, video, and browser-agent claims before publishing copy changes.
Explains that public posts are visible to anyone, protected posts are visible and searchable only for allowed followers, and media links shared on X are not protected.
X Help Center About profile visibility settingsExplains which profile fields are public by default and how X handles profile visibility settings.
X Help Center How to post photos or GIFs on XDocuments how X handles photo posts, multi-image posts, GIF posting, and image display behavior.
X Help Center How to share and watch videos on XDocuments native video upload, playback, autoplay behavior, and web upload limits on X.
Chrome for Developers WebMCP is available for early previewDescribes WebMCP as a way for websites to expose structured tools for browser agents.
WebMCP proposal WebMCPExplains the JavaScript tool interface that lets web pages provide structured actions to agents.
